6.1.7 released 2019-05-17

• Issue #406 - Fix for unhandled exception when a Trusted Advisor check has a null timestamp.

6.1.6 released 2019-04-19

• PR #402 - Add --skip-check command line option for ignoring specific checks based on service and check name. Thanks to @ddelnano.

6.1.5 released 2019-03-06

• Issue #397 - Fix unhandled exception checking SES in some regions. Issue #375 in 6.0.1 handled an uncaught ClientError when checking SES in some regions, but some regions such as ap-southeast-2 are now returning a 503 Service Unavailable for SES instead. Handle this case as well. Thanks to @TimGebert for reporting the issue and bergkampsliew for verifying.

6.1.4 released 2019-03-01

• PR #394 - Fix bug in calculation of VPC "Network interfaces per Region" limit, added in 6.1.0 (PR #379), that resulted in reporting the limit 5x lower than it actually is in some cases. Thanks to @TimGebert.

6.1.3 released 2019-02-26

• PR #391 / Issue #390 - Update for some recently-increased DynamoDB and EFS default limits. Thanks to bergkampsliew.

6.1.2 released 2019-02-19

• PR #387 - Fix bug in calculation of VPC "Network interfaces per Region" limit, added in 6.1.0 (PR #379). Thanks to @nadlerjessie.

6.1.1 released 2019-02-15

• PR #381 / Issue #382 - Revised fix for Issue #375, uncaught ClientError exception when checking SES Send Quota in certain regions. Thanks to bergkampsliew.

6.1.0 released 2019-01-30

• PR #379 - Add support for EC2/VPC Network interfaces per Region limit. Thanks to @nadlerjessie.

6.0.1 released 2019-01-27

• Issue #375 - Fix uncaught ClientError exception when checking SES Send Quota in certain regions. Thanks to bergkampsliew for PR #376.

6.0.0 released 2019-01-01

This release requires new IAM permissions:

• lambda:GetAccountSettings

Important: This release removes the ApiGateway APIs per account limit in favor of more-specific limits; see below.

• Issue #363 - Add support for the Lambda limits and usages.
• Clarify support for "unlimited" limits (limits where :pyawslimitchecker.limit.AwsLimit.get_limit returns None).
• Add support for 26 new EC2 instance types.
• Update default limits for ECS service.
• ApiGateway service now has three ReST API limits (Regional API keys per account, Private API keys per account, and Edge API keys per account) in place of the previous single APIs per account to reflect the current documented service limits.
• API Gateway service - add support for VPC Links per account limit.
• Add support for Network Load Balancer limits Network load balancers and Listeners per network load balancer.
• Add support for Application Load Balancer limits Certificates per application load balancer.
• Add support for Classic ELB (ELBv1) Registered instances per load balancer limit.
• Rename dev/terraform.py to dev/update_integration_iam_policy.py and move from using terraform to manage integration test IAM policy to pure Python.
• Note that I've left out the Targets per application load balancer and Targets per network load balancer limits. Checking usage for these requires iterating over DescribeTargetHealth for each target group, so I've opted to leave it out at this time for performance reasons and because I'd guess that the number of people with 500 or 1000 targets per LB is rather small. Please open an issue if you'd like to see usage calculation for these limits.

Important Note on Limit Values

awslimitchecker has had documented support for Limits that are unlimited/"infinite" since 0.5.0 by returning None from :pyawslimitchecker.limit.AwsLimit.get_limit. Until now, that edge case was only triggered when Trusted Advisor returned "Unlimited" for a limit. It will now also be returned for the Lambda service's Function Count Limit. Please be aware of this if you're using the Python API and assuming Limit values are all numeric.

If you are relying on the output format of the command line awslimitchecker script, please use the Python API instead.