-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit for stack has been exceeded #2467
Comments
@wbroek How many stacks are in your account as a whole? |
@SwaySway where can look that up? See a lot of stacks in the CloudFormation but no number/counts? |
@SwaySway the CloudFormation interface says Stacks(100+); but the Service Quota did say I had 200 |
Did anyone attempt to raise their limit? I di, it's been about three days still waiting. |
Is there a best practice in this regard for many apps with many environments using many stacks and sub-stacks? This account limit of 200 seems fairly low. |
@SourceCode, I've just had a look at this issue now. Is there any chance that you have found a way around this? It seems pretty clear that a relatively small application with multiple environments will hit the 200 limit pretty easily. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
When pushing a new environment from an existing environment we cannot push, it errors out with creation errors with main message "Limit for stack has been exceeded". This was not an issue before?
We got the following resources/services (graphql, rest api, lambda, s3)
Also creating from scratch I hit this limit after adding the graphql api?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Create a new environment
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: