If/when the aws_cloudformation_stack_set
resource supports SERVICE_MANAGED
permissions (tracked by #12422), the aws_cloudformation_stack_set_instance
should support targeting organizational units so that it can be used to provision resources across an AWS Organization.
Currently, the resource identifies itself so that it is particular to the 3-tuple of a StackSet, account, and region. This means one instance of the resource can't be used to manage StackSet instances across multiple regions or organizations dynamically (and I'm not sure if it really should). But in any case, this design makes it incompatible when targeting organizational units (which is required when referring to a StackSet that is using a SERVICE_MANAGED
permission model).
resource "aws_cloudformation_stack_set_instance" "organization_accept-guardduty" {
provider = aws.us-east-1
organizational_unit_ids = [aws_organizations_organization.this.roots.0.id]
regions = ["us-east-1", "us-east-2"]
stack_set_name = aws_cloudformation_stack_set.accept_guardduty.name
}
This is much needed. We currently frankenstein'd CloudFormation and Terraform due to the lack of this feature. It will be very nice once we have this.
Hello there,
Are there any updates on this? It seems that there are several issues opened for the same need which goes to show that people are really wanting this feature.
Thank you in advance!
Awaiting support from terraform for this. Much needed
Most helpful comment
This is much needed. We currently frankenstein'd CloudFormation and Terraform due to the lack of this feature. It will be very nice once we have this.