AWS Amplify app build failing since this morning

Question

Hi, my Amplify app that was building fine until yesterday has suddenly stopped building since this morning. I haven’t made any major changes to my code or build settings.

Platform: AWS Amplify Hosting

Issue: Builds are failing consistently today (after being successful earlier).

What I checked:

Code compiles locally without issues.

Build settings (amplify.yml, environment variables) haven’t been changed.

Tried redeploying and clearing cache.

Questions:

Is there any known issue with Amplify builds today?

How can I debug what changed suddenly - are there updated Node.js versions, dependency mismatches, or service outages that could cause this?

Is there a way to pin Amplify to a stable Node or build image to avoid unexpected breakages?

Any guidance or troubleshooting steps would be appreciated.

Thanks in advance!

re:Post Agent · Answer

There could be several reasons why your Amplify app build is suddenly failing. Here are some troubleshooting steps and potential solutions:

1. **Memory issues**: One common cause of build failures is the build container running out of memory. This can happen with Next.js applications or other memory-intensive builds. You can try:
- Removing `.next/cache/**/*` from the cache.paths section in your amplify.yml
- Increasing memory allocation by setting the NODE_OPTIONS environment variable (e.g., `--max-old-space-size=12288`)

2. **IAM permissions**: Check if there are any IAM role permission issues. Ensure the IAM role associated with your Amplify app has the necessary permissions, including AdministratorAccess and AdministratorAccess-Amplify policies. Also verify the trust relationship of the IAM role allows the Amplify service to assume the role.

3. **Environment variable limits**: If you're using many environment variables, you might be hitting a limit. AWS Amplify has a limit of up to 28 environment variables, with each variable name and value limited to 512 characters.

4. **Check build logs**: Review the detailed build logs in the Amplify console to identify specific error messages that might point to the root cause.

5. **Known issues**: Check the AWS Amplify GitHub repository or AWS Service Health Dashboard for any reported issues or outages.

To prevent unexpected breakages in the future, you could:
- Consider using an initialization script which has fewer limitations
- Consolidate related environment variables if you're approaching limits
- Use AWS Systems Manager Parameter Store for more complex configurations
- Implement a more robust CI/CD pipeline with specific version pinning

If these steps don't resolve the issue, you may need to reach out to AWS Support for more specific assistance based on your build logs and configuration.  
**Sources**  
[Build container ran out of memory | AWS re:Post](https://repost.aws/questions/QUOKgUYiwsSzaqE8pbnyPxRw/build-container-ran-out-of-memory)  
[on amplify react app deploy issue | AWS re:Post](https://repost.aws/questions/QUly0RHs5hSWadDeqOuvWJPA/on-amplify-react-app-deploy-issue)  
[Issue with Amplify Environment Variables Limit | AWS re:Post](https://repost.aws/questions/QU62mblnxyQKG-yFbDAN2_Yg/issue-with-amplify-environment-variables-limit)

AWS Amplify app build failing since this morning

Add your answer

Relevant content