Limit on the number of resources in a single stack operation exceeded (V2 Transformer Migration)
See original GitHub issueBefore opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- I have removed any sensitive information from my code snippets and submission.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v17.1.0
Amplify CLI Version
7.6.19
What operating system are you using?
Linux
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
Not applicable
Amplify Commands
push
Describe the bug
I am trying to migrate a large system from V1 to V2 Transformer. I have upgraded ElasticSearch 6.2 to OpenSearch 1.1. I have performed the “amplify migrate api” and stripped away all the custom resolvers we have.
The amplify push gets a long way through the deployment, but ultimately fails with the message “Limit on the number of resources in a single stack operation exceeded”.
None of my individual stacks are above 500 resources, so I figure this is something to do with concurrent resources. So I checked the current limits on my account, but don’t see any way to change that (have opened up a ticket with the CloudFormation Team):
$aws cloudformation describe-account-limits
ACCOUNTLIMITS StackLimit 2000
ACCOUNTLIMITS StackOutputsLimit 200
ACCOUNTLIMITS ConcurrentResourcesLimit 8500
Not sure how to proceed here.
Expected behavior
Push does not fail
Reproduction steps
See above
GraphQL schema(s)
# Put schemas below this line
Log output
# Put your logs below this line
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:31 (12 by maintainers)
Top Results From Across the Web
AWS CloudFormation quotas
Maximum number of resources you can have involved in stack operations (create, update, or delete operations) in your Region at a given time....
Read more >Project-level configurations - Troubleshooting guide
Push failures from resources exceeding AWS service quotas. Errors: "Limit on the number of resources in a single stack operation exceeded” "Cannot exceed...
Read more >Avoiding the 200-resource limit in CloudFormation stacks with ...
Unfortunately, AWS enforce a limit of 200 resources per CloudFormation stack. Unlike many AWS limits, this is not one that can be increased...
Read more >Migration Guide Red Hat JBoss Enterprise Application ...
Instructions for migrating applications from one major Red Hat JBoss ... Server Configuration Migration Options for limitations of the migrate operation.
Read more >Mule Errors | MuleSoft Documentation
Mule execution failures result in an error. When a Mule app is running, both the Mule runtime engine and the module and connector...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @undefobj / @josefaidt - appreciate your updates to status
Hi @edwardfoyle - just wondering if you have any feedback on this one. Its going to prevent anyone with a significant database migrating to the V2 platform (of course in my opinion). I know we are stopped in our tracks. So any viable workaround also appreciated.