[IT-4720] Throttle Sceptre deployment #1498
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…orks-IT#1496)" This reverts commit 7aea11b.
AWS is throttling cloudformation deployments to service catalog accounts because there are too many requests to the service catalog APIs. This is causing deployments to fail and put service catalog in a bad state. This reverts the temporary disabling of service catalog deployments. It also installs a development version of Sceptre containing a max-concurrency option that will throttle sceptre requests to avoid the AWS throttling.
ConsoleCatzirl
approved these changes
Nov 11, 2025
zaro0508
changed the title
zaro0508
added a commit
to zaro0508/organizations-infra
that referenced
this pull request
Nov 17, 2025
We changed Sceptre to deploy service catalog cloudformation templates serially in PR Sage-Bionetworks-IT#1498 to get around an AWS throttling issue. AWS has confirmed that a change on their end caused this problem and they have reverted their change. From that we are reverting our change so that we can deploy cloudformation in parallel again.
zaro0508
added a commit
that referenced
this pull request
Nov 17, 2025
We changed Sceptre to deploy service catalog cloudformation templates serially in PR #1498 to get around an AWS throttling issue. AWS has confirmed that a change on their end caused this problem and they have reverted their change. From that we are reverting our change so that we can deploy cloudformation in parallel again.
zaro0508
added a commit
to zaro0508/organizations-infra
that referenced
this pull request
Dec 23, 2025
This reverts commit 5e0713e. Sceptre was released v4.60 with a concurrency option to throttle deployments. Update to use the latest upststream version instead of using the private version.
zaro0508
added a commit
that referenced
this pull request
Jan 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AWS is throttling cloudformation deployments to service catalog
accounts because there are too many requests to the service catalog
APIs. This is causing deployments to fail and put service catalog in
a bad state.
This reverts the temporary disabling of service catalog deployments
in PR #1496. It also installs a development version of Sceptre containing
a max-concurrency option that will throttle sceptre requests to avoid
the AWS throttling.