Container Overrides length must be at most 8192

[amitvchaudhary]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

React

Amplify APIs

Authentication, GraphQL API, DataStore

Amplify Version

v6

Amplify Categories

auth, api

Backend

Amplify CLI

Environment information

# Put output below this line

Describe the bug

For past 3 days, I am facing this issue where if I try to deploy using AWS Amplify Studio, with change and without any change, it always fails with below error. It had been working fine and suddenly without any change it stopped working.

Now when I try to push from CLI then the deployment works without any issue. But there, just for testing, I modify my React file and nothing related to backend. Additional info: I am using Gen 1, v6.

Expected behavior

It should deploy without any issue.

Reproduction steps

1. Go to AWS Amplify Studio
2. Simply click Deploy

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line
Container Overrides length must be at most 8192 (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: b6dbb90d-8f3e-40fd-9eec-d7994720a4ac; Proxy: null)

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[HuiSF]

Thanks for opening this issue! I've reached out to the Hosting maintainers for investigation.

[cwoolum]

Hi @amitvchaudhary , could you please share your app id and region?

[amitchaudhary140]

@cwoolum Thanks for looking into it. It would be great if you can expedite this as I am kinda blocked due to it.

Id: d38y4bo2lz3661
Region: ap-south-1

[ali-murtaza92]

the same problem I am facing too

[ali-murtaza92]

[tsnguyenducphuong]

I got same issue. First, I think it was due to adding new field in the Data table, but then I got same error message when trying to delete an existing field.
AppID: drolaplniylbb
Region: us-east-1

[ajessu]

Thanks for the reports.

This is currently an issue the Service team is tracking and actively working on.

Unfortunately, the only current workaround if you encounter this issue is to use the Amplify CLI for deployments.

[amitchaudhary140]

Thanks @ajessu for the response. We hope this gets resolved soon as our production features are blocked due to it. Request you to take it on high priority.

[cwoolum]

Hey @amitchaudhary140 and @ali-murtaza92, I apologize for the delay in response. Can you please create AWS support tickets? It helps us get these issues prioritized internally.

https://console.aws.amazon.com/support

[ali-murtaza92]

I already did. They are asking to wait as well, and they are looking for someone to resolve this issue.

[ykethan]

Hey folks, Amplify team is currently diving into this and should provide an update on the issue.
but as a workaround you should be able to pull your backend resources to your local setup and continue pushing new data models or resources using Amplify CLI.
Refer to the extend using Amplify CLI documentation providing this information. Additionally, refer to our GraphQL documentation providing information on creating and deploying data models using Amplify CLI.

[ajessu]

Apologies for the delays in the resolution of this issue.

The fix has been released to all regions

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