Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

jantman / awslimitchecker Public

Notifications You must be signed in to change notification settings
Fork 188
Star 515

Code
Issues 16
Pull requests 14
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Introducing AWS Lambda Limits and Usage#366

Merged

jantman merged 12 commits intojantman:developjantman/awslimitchecker:developfrom kilsbo:developCopy head branch name to clipboard

Dec 11, 2018

+458-13

Conversation Commits12 (12)Checks Files changed

Commits

Commits on Nov 2, 2018

Ignoring IntelliJ iml files
kilsbo
committed
Lambda service added.
kilsbo
committed

Commits on Nov 4, 2018

issue #363 - Implementation of Lambda limits and usage.
kilsbo
committed
issue #363 - Added generated documentation.
kilsbo
committed

Commits on Dec 10, 2018

PR #366 - make order match between _construct_limits and _update_limits_from_api because I'm horribly pedantic
jantman
committed
PR #366 - remove calculations of constants
jantman
committed
PR #366 - add 'per Function' clarifier to Lambda Code Size zipped/unzipped limits
jantman
committed
clarify support for 'unlimited' limits by having AwsLimit.get_limit return None, and allow AwsLimit() to take None as a default limit value
jantman
committed
PR #366 - define all limits in _construct_limits and unify Total Code Size to MiB
jantman
committed
PR #366 - update tests for previous commits on this PR
jantman
committed

Commits on Dec 11, 2018

PR #366 - ensure that some 'None' limits appear in the CLI examples
jantman
committed
PR #366 - rebuild docs
jantman
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.