aws_cloudformation_stack_set has no field to set max_concurrent operations

[nandac]

Hi,

I have been experimenting with the aws_cloudformation_stack_set resource but find that there is no way to set the number of concurrent executions allowed. As a result I ran into an issue when creating stack set instances as terraform by default tries to create 10 resources in parallel.

Because the max concurrent executions number is set to 1 on the stack set I get:

Error: error creating CloudFormation Stack Set Instance: OperationInProgressException: Another Operation on StackSet arn:aws:cloudformation:<region>:<account>:stackset/<stack-name> is in progress
        status code: 409, request id: 2e0bf029-9923-11e9-9d56-6dd65b781a5f

I can get around the issue by running apply like this:

terraform apply -parallelism=1

I can set the max concurrent executions for the stack set in CloudFormation or with an API call so I believe the aws provider should have this feature as well.

Can you suggest a workaround?

Many thanks,
Nanda

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add a field to the aws_cloudformation_stack_set resource to set the maximum number of concurrent executions.

New or Affected Resource(s)

• aws_cloudformation_stack_set

References

Have not found any related issues.

[nijave]

It seems like a sensible solution to this would be for Terraform to treat 409 responses as "throttling" and retry later

Adding that exception as a throttling exception to the go-sdk would allow Terraform to auto retry aws/aws-sdk-go#2961

Terraform also only submits account-number,region pair at once instead of listing them all out and using a single AWS API call so Terraform operates differently than using the console to make changes

Here's an example but needs cleanup before a PR master...nijave:nv-retry-cloudformation-stackset-operations

[nijave]

Please thumbs up so it gets reviewed faster :) #10969

[breathingdust]

Looks like this was resolved in #10969

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.