Error : Limit on the number of resources in a single stack operation exceeded, IsCustomResource: true

[yashBrahma]

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

12.0.3

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

Limit on the number of resources in a single stack operation exceeded, IsCustomResource: true

We have 8 custom resources each resource does not exceed more than 500. Whenever we add a new env and push we get the above error.

But if we are not getting this error in the current working environment. When we try creating a new env we get this error

Expected behavior

Push without an error

Reproduction steps

Add custom resources at least 10 each as 300 resources in it. and push

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• 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.

[ykethan]

Hey @yashBrahma, thank you for reaching. From the error it appears are you running into a CloudFormation resources limit of 500.
As a workaround, after a amplify add env temporarily remove categories/resources locally, then run push. After the push finishes, re-add the resources and re-push.

[yashBrahma]

Hi @ykethan, currently we are doing the same as you have suggested. But in the long run, this will not work for us.

Is there any way that we put resources into a nested stack? as suggested in this

This is costing our time.

I tried adding a nested stack in cdk-stack but resources added in a nested stack were not generated in cloudFormation template file.

"Resources": {
"nestedstackNestedStacknestedstackNestedStackResource": {
"Type": "AWS::CloudFormation::Stack",
"Properties": {
"TemplateURL": ""
},
"UpdateReplacePolicy": "Delete",
"DeletionPolicy": "Delete"
}
}

[ykethan]

@yashBrahma reached out to the team on this, unfortunately the limit on the update stack operation would apply on the entire stack tree and not just on a single stack.

[BBopanna]

Hey @yashBrahma, thank you for reaching. From the error it appears are you running into a CloudFormation resources limit of 500. As a workaround, after a amplify add env temporarily remove categories/resources locally, then run push. After the push finishes, re-add the resources and re-push.

Thankyou but this is definitely NOT scalable solution, any other recommendations ? @kaustavghosh06

[ykethan]

Closing the issue due to inactivity, please refer to #13536 providing additional information on this issue.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.