[Lambda] Increase Layers and Lambda size to 500mb

Open
#76 0 comments 28 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, numpy, pandas, python
Domain
cloud

Research direction

This is an AWS Lambda service-limit request; the issue names no repository files, tests, or entry points. Start by reviewing the current Lambda layer and deployment-package limits and comparing the stated 500 MB request with provider constraints. Done means AWS evaluates and implements the increased limits, rather than a change in this repository.

Written by the indexing model from the issue text.

Description

Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
    If you are interested in providing additional feedback, please leave a comment

Description

Increase Layers and Lambda size limit to 500mb.

Additional context

The size of python libraries increases more and more over time. For example, if we use pandas, numpy and polars, we very easily exceed the current limit of 250mb. Other cloud providers already offer 500mb.

Dominant language
No language data
Stars
196
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-roadmap

All issues in aws/aws-lambda-roadmap

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.