Have you solve this error??? If yes ,How did you solve this error??

[Nischit007]

@cjihrig Yes. I will absolutely send that your way with the issue id referenced in the subject line.

I just want to make sure I know everything about the env when it is falling because this occurred with another member of my team on his sandboxed environment.

This week, I will reproduce this error in our dev environment with the latest CLI version.

Thank you very much.

Originally posted by @alexboulay in #7680

[ykethan]

Hey @Nischit007, thank you for reaching out. As suggested in the comment could you try using amplify push --yes --minify

[pahud]

Hi @Nischit007,

Thank you for reaching out. I can see you're referencing the CloudFormation template size limit issue from #7680.

The solution mentioned in that issue was:

amplify push --yes --minify

However, to provide you with the most appropriate guidance, could you please share:

1. Your specific error message and logs
2. Environment information:
   • Amplify CLI version (amplify --version)
   • Node.js version
   • Operating system
3. Your GraphQL schema complexity (number of types, fields, etc.)
4. What you've already tried to resolve the issue

Common solutions for this issue include:

1. Use minification: amplify push --yes --minify
2. Optimize your schema:
   • Remove unused types and fields
   • Disable subscriptions if not needed: amplify update api → disable subscriptions
3. Consider Amplify Gen 2: For better scalability with large schemas

Related Issues: #7680, #10479

If the --minify flag doesn't work, please share your specific error details so we can provide more targeted assistance.

Issue Quality Note: For future reference, please provide specific details about your environment and error when creating issues, as this helps us provide better support.

I am closing this issue for staleness, if there's any concern, feel free to create a new issue for us.

[github-actions[bot]]

This issue is now closed. 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.