Skip to content

Documentation: the package size limit includes the layers #2194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mnapoli merged 1 commit into from
Sep 27, 2026
Merged

Documentation: the package size limit includes the layers #2194

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/deploy/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,9 @@ Once your project is ready, you can deploy via the following command:

### Reducing package size

AWS Lambda has a **250MB size limit** for deployed applications (unzipped). Large Composer dependencies can push your project over this limit and also lead to slower cold starts.
AWS Lambda has a **250MB size limit** for deployed applications (unzipped). The limit counts the application code **and** the Lambda layers: Bref's PHP runtime layer takes about 80MB of it, so your code has roughly 170MB. Large Composer dependencies can push your project over this limit and also lead to slower cold starts.

A deployment over the limit fails with the AWS error `Unzipped size must be smaller than 262144000 bytes`.

The most common offender is `aws/aws-sdk-php`: it ships clients for **every** AWS service, adding over 100MB to your vendor directory. If you only use a few services (e.g. S3, SQS, DynamoDB), you can remove the rest.

Expand Down
Loading