aws-amplify / aws-amplify/amplify-hosting

SSR Build failed due to RequestEntityTooLargeException

Open
#2,707 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

dpoimtt9hpxe2

### Region

eu-west-2

### Amplify Hosting feature

Backend builds

### Describe the bug

My build is succeed in the local environment but failed on Amplify with the error:
Starting SSR Build...
RequestEntityTooLargeException: Request must be smaller than 69905067 bytes for the CreateFunction operation

I checked my application and it's only 30Mb in size. The previous build was succeeded.

### Expected behavior

I'd expect the build is success as our previous builds. Or if there's any workaround that can help us deploying the change.

### Reproduction steps

1. Commit the change to Github
2. The Amplify build was trigger automatically
3. Build failed with the error "Starting SSR Build...
4
![Uploading image.png…]()

### Build Settings

```yaml
version: 1
applications:
- frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- yarn run build
artifacts:
baseDirectory: .next
files:
- '**/*'
cache:
paths:
- node_modules/**/*

appRoot: Source/web
```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the Amplify Hosting backend-build SSR stage and the .next artifact produced by the build settings in the issue. Reproduce the GitHub-triggered build using the listed yarn commands, then determine why CreateFunction receives more than 69905067 bytes. Done means identifying the cause and documenting a verified workaround or fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, next.js
Domain
cloud, devops, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.