Amplify-cli: Template may not exceed 460800 bytes in size.

[JustFly1984]

Describe the bug
Template may not exceed 460800 bytes in size.

Template is autogenerated and the size is 523Kb.

Expected behavior
if generated code exceeding the limit, it should be divided to sub-stack.

If you have some solution, please share.

[mikeparisstuff]

We are tackling the Cloudformation limit issues very soon and will be migrating the transform to use nested stacks. Resources just freed up so expect to see movement on this issue soon.

[JustFly1984]

Thank you! This is amazing news!!! We are screwed with our current project implementation development, and can't deploy to production new features since last week, cos our project www.agrariansupply.com is developing at fast pace. Please post any news as soon as it possible to use amplify-cli again.

Thank you for your work, it really improves our development workflow.

[JustFly1984]

Is there any update?

[JustFly1984]

Any news?

[christianto88]

we have the same problem as well. do you have any ETA when will this issue be resolved?

[JustFly1984]

Hey guys, why is it taking so long?

[kunwarVivek]

Hi,
any updates on this issue. Is there any workaround for this problem.

[JustFly1984]

@kunwarVivek
We are using lambdas with graphql resolvers to DynamoDB instead of Amplify as workaround.

[JustFly1984]

I feel like AWS spending not enough for open-source support (((

[kaustavghosh06]

@JustFly1984 We’re actively working to support this currently. We have a design for this and have started work on it but it’s not production ready yet.

[kunwarVivek]

Team,

Atleast suggest a workaround.

We have not more than 12-15 tables with couple of 1 to many relationships
and we are stuck.

Regards
Kunwar
[phone]

On Fri, Nov 16, 2018 at 11:43 PM Kaustav Ghosh [e-mail]
wrote:

@JustFly1984 https://github.com/JustFly1984 We’re actively working to
support this currently. We have a design for this and have started work on
it but it’s notboeiduction ready yet.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/185#issuecomment-439479503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFAChUlDxVg37gG_goDNXWgYqW-luzStks5uvwA_gaJpZM4WzLLL
.

[darrylmack]

Any news on this? Stuck in an app with 20 tables and 8 have one-to-many relationships.

[darrylmack]

@kaustavghosh06 In the interim, is there a workaround. Splitting the CloudFormation templates doesn't seem possible as the cli generates the template. Is it possible to generate the template with fewer tables. and then edit the schema directly in the AWS console?

Or will that overwrite the local schema.graphql on next amplify push?

[kaustavghosh06]

@darrylmack We're still working on this as the solution for this isn't trivial.
For the interim, you could create the API on the Appsync console, using the contents present in amplify/api//build/ directory and then could probably do a codegen on that API using the
amplify add codegen --apiId XXXXXX. This also adds the appsync API to your aws_exports.js file which would be accessible by your frontend code via the AWS Amplify JS lib.

[kunwarVivek]

Hi,

Will " amplify add codegen " create the corresponding dynamodb tables and
roles that are required to access the tables .

Regards
Kunwar
[phone]

On Wed, Nov 21, 2018 at 5:12 AM Kaustav Ghosh [e-mail]
wrote:

@darrylmack https://github.com/darrylmack We're still working on this
as the solution for this isn't trivial.
For the interim, you could create the API on the Appsync console, using
the contents present in amplify/api//build/ directory and then could
probably do a codegen on that API using the
amplify add codegen --apiId XXXXXX. This also adds the appsync API to
your aws_exports.js file which would be accessible by your frontend code
via the AWS Amplify JS lib.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/185#issuecomment-440468927,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFAChaiT-X0Q-UMGsUmOVYkl-wHECy0Zks5uxJNKgaJpZM4WzLLL
.

[afuyo]

Hi
amplify add codegen --apiId XXXXX generates invalid subcommand. Is this a valid command?

[rajababu3]

Hi,
Is there any update for this issue?
How long will this take ?

[kldeb]

@kaustavghosh06 I updated the schema in AppSync console.

When I run: amplify add codegen --apiId [myAPIId] I get the following error: Codegen support only one GraphQL API per project

How do I get around this?

Edit: trying amplify codegen statements

[chasen]

I am having this issue as well, i saw in another post that the auto-generated template uses pretty print for the json output making my template file. 959KB however just minifying(removing the whitespace) reduces that size to 207KB under the max size.

Maybe while you work on fixing the issue you could release a stop gap version that used a minified json file?

[JustFly1984]

Is there any update? It is been 3 months since I opened an issue.

[stanleycyang]

Yeah would love to see at least a workaround on this issue. Just completely blocked

[randallprince]

Started using AppSync a week or so ago. Finalized my tables yesterday and then this pops up. It would be nice to have an ETA or some help on the creation of the DynamoDB tables as though I have the schema setup now, I can't actually do anything since the tables still need to be built. I'm going to try @chasen 's solution as that seems pretty reasonable at the moment. Thanks guys!

[randallprince]

Actually just tried the manual compression to no avail. Opened up CloudFormation and the CloudFormation Designer on the failed process, replaced the template with the minified JSON file, but after trying to run it, during validation I get the following error:

Template is not valid: Template format error: Number of resources, 203, is greater than maximum allowed, 200

So, the file size seems to be somewhat related to how resources are limited. Now to look around and see if it's possible to maximum resource ceiling manually.

Hopefully, someone who might be slightly closer to the limit might be able to move past this error. Good luck!

[stanleycyang]

@JustFly1984 we ended up just having to write our own resolvers in AppSync with VTL and connect our databases, which sucks but it is what it is. Hope that helps you move forward

[JustFly1984]

@stanleycyang We are ended up pretty the same destination. That is sucks that tool like this promises gold, but provides copper in best case scenario.

[undefobj]

@JustFly1984 @stanleycyang @randallprince @chasen @rajababu3 @darrylmack @kunwarVivek @christianto88

We are very close to implementing a solution for this. Unfortunately it was a very complex problem to resolve and implement stack and template partitioning in the core deployment processes of the transformer. We also have a custom resolvers solution as well which will let you override both GraphQL fields and templates as well as implement your own CloudFormation overrides. If you could keep an eye on this PR: https://github.com/aws-amplify/amplify-cli/pull/581 and help test it out to validate the solution that will help us release faster. We're trying our best to get this out in the coming weeks.

[nagey]

would be really great to get a solution to this published.

[ffabinhoo]

I am having the same problem. Any update on this matter?

[kaustavghosh06]

Hey guys,
The fix for this has been merged to the main cli verison. Please use npm install -g @aws-amplify/cli to install the latest version of the CLI.

[meetrij]

@kaustavghosh06 not working with cli version update my amplify version 1.7.4

[kaustavghosh06]

@meetrij What does your schema look like? Interested in knowing the number of models and number of connections in your annotated schema.

[lr001dev]

So, I updated my cli and I'm getting this error:

AWS::CloudFormation::Stack Wed Oct 14 2020 00:02:12 GMT-0700 (Pacific Daylight Time) Template may not exceed 468992 bytes in size.

My api-cloudformation.json is breaking the limit, so not sure how to fix this....