-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
AWS Lambda Has Increased Memory Limits #1844
AWS Lambda Has Increased Memory Limits #1844
Conversation
Co-authored-by: Pat Myron <PatMyron@users.noreply.github.com>
I do not seem to have the ability to link this to issue |
Can we please have 20480 while you're in there ;) (j/k thanks for the contribution!) |
I mean we can...but AWS isn't ready for that level of awesome |
Linting failed on files unrelated to this pull request.
|
Sorry, that was me since Travis wasn't showing in PRs until this week. Fixing here: #1845 |
@PatMyron was not trying to be lazy. I wanted to keep the scope of the changes clear since I am a random human to this project. :) |
Thanks! Further update likely we should move from a list of values to just checking the upper/lower bounds and alignment. |
AWS has announced a new memory limit for AWS Lambda. The Limit is now 10240 MB.