Upgraded from cli v3.9 to v3.17 - get error on push: "Invalid request template given, must be less than 64kb in size"
See original GitHub issueDescribe the bug I upgraded the cli from v3.9 to v3.17 then did an amplify push. The push is failing with:
UPDATE_FAILED Update<redact>RequestResolver AWS::AppSync::Resolver Wed Nov 06 2019 14:36:46 GMT-0700 (Mountain Standard Time) Invalid request template given, must be less than 64kb in size. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: d2eec6ea-649e-4dea-b188-d4464fd52e1c)
Amplify CLI Version v3.17
Desktop (please complete the following information):
- OS: Mac
- Node Version. 10.9
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:39 (8 by maintainers)
Top Results From Across the Web
Resolve template validation or template format errors in ...
Validate your JSON or YAML templates with the AWS CloudFormation linter on the GitHub website.
Read more >draft-mbelshe-httpbis-spdy-00.txt - IETF
51 Belshe & Peon Expires August 4, 2012 [Page 3] Internet-Draft SPDY Feb 2012 1. ... (Section 2.4.2) with the error code INVALID_STREAM...
Read more >Developer's guide to installing Pendo
This article summarizes the components and instructions for installing Pendo. Installation involves inserting Pendo's JavaScript code...
Read more >DOSBox v0.74-3 Manual
You have to make your directories available as drives in DOSBox by using the "mount" command. For example, in Windows "mount C D:\GAMES"...
Read more >Versal Platform Loader and Manager - Xilinx Wiki - Confluence
Any system configuration in Versal will come in the form of a CDO to PLM. ... Status) { 3 //Update proper error code...
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
This issue should be reopened. This is a major flaw. We are building a healthcare platform that has many fields which require different authorization levels. We can’t compromise security because there is a 64kb file size limit. AWS has to offer a larger size even if it requires to be on a paid plan.
fyi I did contact AWS Support and they are not able to change these limits at this time. So the solution is to reduce the number of field-level auths until amplify cli comes up with reduced code to enforce field auths.