A tool that helps keeping track of your AWS quota utilization

Overview

aws-quota-checker

A tool that helps keeping track of your AWS quota utilization. It'll determine the limits of your AWS account and compare them to the number of current resources.

Example output of aws-quota-checker

This is especially useful cause today, cloud resources are being created from all kinds of sources, e.g. IaC and Kubernetes operators. This tool will give you a head start for requesting quota increases before you hit a quota limit to prevent being stuck with a production system not being able to scale anymore.

A usual use case is to add it to your CI pipeline right after applying your IaC or run it on a regular basis. Feel free to leave a vote on this issue if you'd like to see a Prometheus exporter.

Installation

From pypi

pip install aws-quota-checker

From source

git clone [email protected]:brennerm/aws-quota-checker.git
cd aws-quota-checker
pip install .

Usage

Make sure you are logged into your AWS account (aws configure or through environment variables) or switch to the one you want to check. This account needs to have read permissions for all supported services. AWS provides a default policy called ReadOnlyAccess that contains the required permissions.

Check the help page with aws-quota-checker --help to see all available command and their documentation.

Run a single check

$ aws-quota-checker check vpc_count
AWS profile: default | AWS region: eu-central-1 | Active checks: vpc_count
VPCs per region [default/eu-central-1]: 1/5 ✓

Run all checks

$ aws-quota-checker check all
AWS profile: default | AWS region: eu-central-1 | Active checks: route53_traffic_policy_count,vpc_count,ec2_tgw_count,ec2_on_demand_standard_count,route53_health_check_count,cw_alarm_count,iam_attached_policy_per_role,asg_count,elasticbeanstalk_environment_count,s3_bucket_count,iam_attached_policy_per_user,elb_listeners_per_alb,ec2_eip_count,route53resolver_rule_count,iam_policy_version_count,elb_listeners_per_nlb,vpc_subnets_per_vpc,route53_vpcs_per_hosted_zone,cf_stack_count,iam_user_count,elb_listeners_per_clb,ni_count,dyndb_table_count,elasticbeanstalk_application_count,route53_traffic_policy_instance_count,ig_count,elb_clb_count,ec2_vpn_connection_count,route53_reusable_delegation_set_count,ebs_snapshot_count,route53_hosted_zone_count,iam_attached_policy_per_group,eks_count,am_mesh_count,elb_target_group_count,route53resolver_rule_association_count,iam_server_certificate_count,elb_alb_count,vpc_acls_per_vpc,iam_group_count,ec2_spot_standard_count,route53resolver_endpoint_count,iam_policy_count,elb_nlb_count,sg_count,route53_records_per_hosted_zone,lc_count,ecs_count,secretsmanager_secrets_count
Collecting checks  [####################################]  100%
Route53 Traffic Policies per Account [default]: 0/50 ✓
VPCs per region [default/eu-central-1]: 1/5 ✓
Transit Gateways per account [default]: 4/5 !
Running On-Demand Standard (A, C, D, H, I, M, R, T, Z) EC2 instances [default]: 0/1280 ✓
Route53 Health Checks per Account [default]: 0/200 ✓
Number of CloudWatch alarms per region [default/eu-central-1]: 0/5000 ✓
Auto Scaling groups per region [default/eu-central-1]: 0/200 ✓
Elastic Beanstalk Environments per account [default]: 0/200 ✓
Application Load Balancers per region [default/eu-central-1]: 46/50 X
...

Run a single instance check

$ aws-quota-checker check-instance vpc_acls_per_vpc vpc-0123456789
Network ACLs per VPC [default/eu-central-1/vpc-0123456789]: 0/200

Missing a quota check?

Feel free to create a new issue with the New Check label including a description which quota check you are missing.

Comments
  • Add RDS snapshot quota checks

    Add RDS snapshot quota checks

    Adds quota checks for Manual DB cluster snapshots and Manual DB instance snapshots https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html#RDS_Limits.Limits image

    $ aws-quota-checker check rds_db_snapshots,rds_db_cluster_snapshots
    AWS profile: default | AWS region: ap-southeast-2 | Active checks: rds_db_cluster_snapshots,rds_db_snapshots
    Collecting checks  [####################################]  100%
    Manual DB cluster snapshots per Region [xxx/ap-southeast-2]: 0/200 ✓
    Manual DB instance snapshots per Region [xxx/ap-southeast-2]: 152/200 ✓
    
    opened by kedoodle 4
  • Version 1.10.0

    Version 1.10.0

    Added

    • fix MaxResults=1000 for EC2 instances check (from baec59a)
    • new checks: ecsstrg_count,fargatespot_count,fargatedemand_count,iam_role_count (from #23)
    • added service/quota_code: iam_user_count
    • fixed description: s3_bucket_count
    • feature: display NOTDEF for check if limit in AWS is not default (was increased)
    • catch EndpointConnectionError
    opened by alt-dima 4
  • Paginate ebs_snapshot_count check

    Paginate ebs_snapshot_count check

    This PR fixes a memory usage issue whereby quota checks make a single boto3 call, even when supposedly paginating. Symptoms described in this comment on #31.

    • Uses the existing paginator to count the ebs_snapshot_count quota
    • Sets a default pagination page size (otherwise the paginator just gets all resources in my testing of describe_snapshots)
    • Fixes up an error log message

    See memory usage spikes to ~800 MiB on 1.10.0 and is fairly stable at ~50 MiB on this branch. image

    Before:

    • Locally
      $ time aws-quota-checker check ebs_snapshot_count
      
      AWS profile: default | AWS region: ap-southeast-2 | Active checks: ebs_snapshot_count
      EBS Snapshots per Region [xxx/ap-southeast-2]: 34896/100000 ✓
      aws-quota-checker check ebs_snapshot_count  12.72s user 2.32s system 3% cpu 7:27.41 total
      
    • In cluster (~3 minutes):
      AWS profile: default | AWS region: ap-southeast-2 | Active checks: 
      cf_stack_count,ebs_snapshot_count,rds_instances,s3_bucket_count
      ...
      07-Jan-22 06:10:21 [INFO] aws_quota.prometheus - refreshing current values
      07-Jan-22 06:13:39 [INFO] aws_quota.prometheus - current values refreshed
      

    After:

    • Locally:
      $ time aws-quota-checker check ebs_snapshot_count
      
      AWS profile: default | AWS region: ap-southeast-2 | Active checks: ebs_snapshot_count
      EBS Snapshots per Region [xxx/ap-southeast-2]: 34899/100000 ✓
      aws-quota-checker check ebs_snapshot_count  12.33s user 1.36s system 16% cpu 1:25.01 total
      
    • In cluster (~1 minute):
      AWS profile: default | AWS region: ap-southeast-2 | Active checks: 
      cf_stack_count,ebs_snapshot_count,rds_instances,s3_bucket_count
      ...
      07-Jan-22 08:47:46 [INFO] aws_quota.prometheus - refreshing current values
      07-Jan-22 08:48:55 [INFO] aws_quota.prometheus - current values refreshed
      
    opened by kedoodle 2
  • Compatibility with python3

    Compatibility with python3

    Getting the following error while running it inside a kubernetes pod or even as a container

    Traceback (most recent call last): File "/usr/local/bin/aws-quota-checker", line 7, in from aws_quota.cli import cli File "/usr/local/lib/python3.7/site-packages/aws_quota/cli.py", line 2, in from aws_quota.utils import get_account_id File "/usr/local/lib/python3.7/site-packages/aws_quota/utils.py", line 6, in def get_account_id(session: boto3.Session) -> str: File "/usr/lib64/python3.7/functools.py", line 490, in lru_cache raise TypeError('Expected maxsize to be an integer or None') TypeError: Expected maxsize to be an integer or None

    opened by rishavsharma9802 2
  • ebs_snapshot_count seems high

    ebs_snapshot_count seems high

    I'm seeing EBS Snapshots per region [default/eu-west-1]: 25780/100000 ✓ for an account with only a handful of actual snapshots. Perhaps change

    return len(self.boto_session.client('ec2').describe_snapshots()['Snapshots'])
    

    To

    return len(self.boto_session.client('ec2').describe_snapshots(OwnerIds=["self"])['Snapshots'])
    
    opened by cariaso 2
  • Bump urllib3 from 1.26.4 to 1.26.5

    Bump urllib3 from 1.26.4 to 1.26.5

    Bumps urllib3 from 1.26.4 to 1.26.5.

    Release notes

    Sourced from urllib3's releases.

    1.26.5

    :warning: IMPORTANT: urllib3 v2.0 will drop support for Python 2: Read more in the v2.0 Roadmap

    • Fixed deprecation warnings emitted in Python 3.10.
    • Updated vendored six library to 1.16.0.
    • Improved performance of URL parser when splitting the authority component.

    If you or your organization rely on urllib3 consider supporting us via GitHub Sponsors

    Changelog

    Sourced from urllib3's changelog.

    1.26.5 (2021-05-26)

    • Fixed deprecation warnings emitted in Python 3.10.
    • Updated vendored six library to 1.16.0.
    • Improved performance of URL parser when splitting the authority component.
    Commits
    • d161647 Release 1.26.5
    • 2d4a3fe Improve performance of sub-authority splitting in URL
    • 2698537 Update vendored six to 1.16.0
    • 07bed79 Fix deprecation warnings for Python 3.10 ssl module
    • d725a9b Add Python 3.10 to GitHub Actions
    • 339ad34 Use pytest==6.2.4 on Python 3.10+
    • f271c9c Apply latest Black formatting
    • 1884878 [1.26] Properly proxy EOF on the SSLTransport test suite
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • [New Check] Roles in an AWS account

    [New Check] Roles in an AWS account

    The AWS console is warning us about getting close to the limit for number of IAM roles (1000). Would like to have a check for this limit.

    https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-quotas.html#reference_iam-quotas-entities

    opened by charleshepner 1
  • Regression for blacklist check in 1.3.0

    Regression for blacklist check in 1.3.0

    Running check with a blacklist entry in 1.3.0 returns a usage error.

    (aws-quota-checker) [(HEAD detached at 1.3.0)] aws-quota-checker $ aws-quota-checker check 'all,!vpc_count'
    Usage: aws-quota-checker check [OPTIONS] [all|am_mesh_count|asg_count|cf_stack
                                   _count|cw_alarm_count|dyndb_table_count|ebs_sna
                                   pshot_count|ec2_eip_count|ec2_on_demand_f_count
                                   |ec2_on_demand_g_count|ec2_on_demand_inf_count|
                                   ec2_on_demand_p_count|ec2_on_demand_standard_co
                                   unt|ec2_on_demand_x_count|ec2_spot_f_count|ec2_
                                   spot_g_count|ec2_spot_inf_count|ec2_spot_p_coun
                                   t|ec2_spot_standard_count|ec2_spot_x_count|ec2_
                                   tgw_count|ec2_vpn_connection_count|ecs_count|ek
                                   s_count|elasticbeanstalk_application_count|elas
                                   ticbeanstalk_environment_count|elb_alb_count|el
                                   b_clb_count|elb_listeners_per_alb|elb_listeners
                                   _per_clb|elb_listeners_per_nlb|elb_nlb_count|el
                                   b_target_group_count|iam_attached_policy_per_gr
                                   oup|iam_attached_policy_per_role|iam_attached_p
                                   olicy_per_user|iam_group_count|iam_policy_count
                                   |iam_policy_version_count|iam_server_certificat
                                   e_count|iam_user_count|ig_count|lc_count|ni_cou
                                   nt|route53_health_check_count|route53_hosted_zo
                                   ne_count|route53_records_per_hosted_zone|route5
                                   3_reusable_delegation_set_count|route53_traffic
                                   _policy_count|route53_traffic_policy_instance_c
                                   ount|route53_vpcs_per_hosted_zone|route53resolv
                                   er_endpoint_count|route53resolver_rule_associat
                                   ion_count|route53resolver_rule_count|s3_bucket_
                                   count|secretsmanager_secrets_count|sg_count|sns
                                   _pending_subscriptions_count|sns_subscriptions_
                                   per_topic|sns_topics_count|vpc_acls_per_vpc|vpc
                                   _count|vpc_subnets_per_vpc]
    Try 'aws-quota-checker check --help' for help.
    
    Error: Invalid value for '[all|am_mesh_count|asg_count|cf_stack_count|cw_alarm_count|dyndb_table_count|ebs_snapshot_count|ec2_eip_count|ec2_on_demand_f_count|ec2_on_demand_g_count|ec2_on_demand_inf_count|ec2_on_demand_p_count|ec2_on_demand_standard_count|ec2_on_demand_x_count|ec2_spot_f_count|ec2_spot_g_count|ec2_spot_inf_count|ec2_spot_p_count|ec2_spot_standard_count|ec2_spot_x_count|ec2_tgw_count|ec2_vpn_connection_count|ecs_count|eks_count|elasticbeanstalk_application_count|elasticbeanstalk_environment_count|elb_alb_count|elb_clb_count|elb_listeners_per_alb|elb_listeners_per_clb|elb_listeners_per_nlb|elb_nlb_count|elb_target_group_count|iam_attached_policy_per_group|iam_attached_policy_per_role|iam_attached_policy_per_user|iam_group_count|iam_policy_count|iam_policy_version_count|iam_server_certificate_count|iam_user_count|ig_count|lc_count|ni_count|route53_health_check_count|route53_hosted_zone_count|route53_records_per_hosted_zone|route53_reusable_delegation_set_count|route53_traffic_policy_count|route53_traffic_policy_instance_count|route53_vpcs_per_hosted_zone|route53resolver_endpoint_count|route53resolver_rule_association_count|route53resolver_rule_count|s3_bucket_count|secretsmanager_secrets_count|sg_count|sns_pending_subscriptions_count|sns_subscriptions_per_topic|sns_topics_count|vpc_acls_per_vpc|vpc_count|vpc_subnets_per_vpc]': invalid choice: all,!vpc_count. (choose from all, am_mesh_count, asg_count, cf_stack_count, cw_alarm_count, dyndb_table_count, ebs_snapshot_count, ec2_eip_count, ec2_on_demand_f_count, ec2_on_demand_g_count, ec2_on_demand_inf_count, ec2_on_demand_p_count, ec2_on_demand_standard_count, ec2_on_demand_x_count, ec2_spot_f_count, ec2_spot_g_count, ec2_spot_inf_count, ec2_spot_p_count, ec2_spot_standard_count, ec2_spot_x_count, ec2_tgw_count, ec2_vpn_connection_count, ecs_count, eks_count, elasticbeanstalk_application_count, elasticbeanstalk_environment_count, elb_alb_count, elb_clb_count, elb_listeners_per_alb, elb_listeners_per_clb, elb_listeners_per_nlb, elb_nlb_count, elb_target_group_count, iam_attached_policy_per_group, iam_attached_policy_per_role, iam_attached_policy_per_user, iam_group_count, iam_policy_count, iam_policy_version_count, iam_server_certificate_count, iam_user_count, ig_count, lc_count, ni_count, route53_health_check_count, route53_hosted_zone_count, route53_records_per_hosted_zone, route53_reusable_delegation_set_count, route53_traffic_policy_count, route53_traffic_policy_instance_count, route53_vpcs_per_hosted_zone, route53resolver_endpoint_count, route53resolver_rule_association_count, route53resolver_rule_count, s3_bucket_count, secretsmanager_secrets_count, sg_count, sns_pending_subscriptions_count, sns_subscriptions_per_topic, sns_topics_count, vpc_acls_per_vpc, vpc_count, vpc_subnets_per_vpc)
    
    

    Expected output (1.2.0):

    (aws-quota-checker) [(HEAD detached at 1.2.0)] aws-quota-checker $ aws-quota-checker check 'all,!vpc_count'
    AWS profile: default | AWS region: None | Active checks: am_mesh_count,asg_count,cf_stack_count,cw_alarm_count,dyndb_table_count,ebs_snapshot_count,ec2_eip_count,ec2_on_demand_f_count,ec2_on_demand_g_count,ec2_on_demand_inf_count,ec2_on_demand_p_count,ec2_on_demand_standard_count,ec2_on_demand_x_count,ec2_spot_f_count,ec2_spot_g_count,ec2_spot_inf_count,ec2_spot_p_count,ec2_spot_standard_count,ec2_spot_x_count,ec2_tgw_count,ec2_vpn_connection_count,ecs_count,eks_count,elasticbeanstalk_application_count,elasticbeanstalk_environment_count,elb_alb_count,elb_clb_count,elb_listeners_per_alb,elb_listeners_per_clb,elb_listeners_per_nlb,elb_nlb_count,elb_target_group_count,iam_attached_policy_per_group,iam_attached_policy_per_role,iam_attached_policy_per_user,iam_group_count,iam_policy_count,iam_policy_version_count,iam_server_certificate_count,iam_user_count,ig_count,lc_count,ni_count,route53_health_check_count,route53_hosted_zone_count,route53_records_per_hosted_zone,route53_reusable_delegation_set_count,route53_traffic_policy_count,route53_traffic_policy_instance_count,route53_vpcs_per_hosted_zone,route53resolver_endpoint_count,route53resolver_rule_association_count,route53resolver_rule_count,s3_bucket_count,secretsmanager_secrets_count,sg_count,sns_pending_subscriptions_count,sns_subscriptions_per_topic,sns_topics_count,vpc_acls_per_vpc,vpc_subnets_per_vpc
    
    opened by philof 1
  • Add vpc endpoint and nat gateways checks.

    Add vpc endpoint and nat gateways checks.

    Add two more checks at vpc check.

    AWS profile: default | AWS region: us-west-2 | Active checks: nat_count
    Collecting checks  [####################################]  100%
    NAT gateways per Region [XXXXXXX/us-west-2]: 60/90 ✓
    
    AWS profile: default | AWS region: eu-west-2 | Active checks: vpc_endpoint
    Collecting checks  [####################################]  100%
    Gateway VPC endpoints per Region [XXXXXXX/eu-west-2]: 1/20 ✓
    ``
    opened by ppanagiotis 0
  • Build for MacM1

    Build for MacM1

    Would love to use this locally, however the Docker image is not build for linux/arm64/v8

    WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
    

    Probably https://github.com/marketplace/actions/build-and-push-docker-images will help as the following ran fine

    docker buildx build --platform=linux/arm/v8 -t aws-quota-checker:macm1 .
    
    opened by mavogel 0
  • How to check more than one region at the same time?

    How to check more than one region at the same time?

    I configured the quota check with my prometheus, but it only brings me the default region of aws configure, but I need it to bring sa-east-1 and us-east-1, could you help me?

    opened by ericosuporte 0
  • Avoid TooManyRequestsException using backoff

    Avoid TooManyRequestsException using backoff

    Adds backoff package to avoid TooManyRequestsException happened with high-rated requests. https://docs.aws.amazon.com/servicequotas/2019-06-24/apireference/API_GetServiceQuota.html Now there are retries:

    12-Apr-22 16:57:04 [INFO] aws_quota.prometheus - starting /metrics endpoint on port 8080
    12-Apr-22 16:57:04 [INFO] aws_quota.prometheus - collecting checks
    12-Apr-22 16:57:22 [INFO] aws_quota.prometheus - collected 746 checks
    12-Apr-22 16:57:22 [INFO] aws_quota.prometheus - refreshing limits
    12-Apr-22 16:57:39 [INFO] backoff - Backing off _maximum(...) for 0.3s (botocore.errorfactory.TooManyRequestsException: An error occurred (TooManyRequestsException) when calling the GetServiceQuota operation: Rate exceeded)
    12-Apr-22 16:57:41 [INFO] backoff - Backing off _maximum(...) for 0.6s (botocore.errorfactory.TooManyRequestsException: An error occurred (TooManyRequestsException) when calling the GetServiceQuota operation: Rate exceeded)
    

    In addition I add traceback to logs when error still happens.

    opened by velom 1
  • CloudFormation stack count doesn't return full count

    CloudFormation stack count doesn't return full count

    Version: aws-quota-checker==1.12.0

    when running

    aws-quota-checker check cf_stack_count --profile tools --region $region
    

    I'm seeing a maximum of 100 returned for regions that have more than 100 stacks. I suspect this is some kind of paging issue.

    opened by Graham42 1
Releases(1.12.0)
  • 1.12.0(Jan 14, 2022)

  • 1.11.0(Jan 10, 2022)

  • 1.10.0(Jan 6, 2022)

    Changelog

    Added

    • add error handling for CLI result reporter
    • new check: iam_role_count
    • Prometheus metrics now have a new label that contains the quota key, see #31 for further details
    Source code(tar.gz)
    Source code(zip)
  • 1.9.0(Sep 21, 2021)

  • 1.8.0(Sep 10, 2021)

    Changelog

    Added

    • new check: rds_instances
    • new check: rds_parameter_groups
    • new check: rds_cluster_parameter_groups

    Fixed

    • iterator bug that prevented check-instance command to function

    Security

    • update several dependencies
    Source code(tar.gz)
    Source code(zip)
  • 1.7.0(May 5, 2021)

  • 1.6.0(Apr 30, 2021)

  • 1.5.0(Apr 19, 2021)

  • 1.4.1(Mar 25, 2021)

  • 1.4.0(Mar 21, 2021)

    Changelog

    Added

    • new check: vpc_rules_per_acl
    • new check: vpc_ipv4_cidr_blocks_per_vpc
    • new check: vpc_ipv6_cidr_blocks_per_vpc
    • new check: vpc_rules_per_sg
    • new check: vpc_route_tables_per_vpc
    • new check: vpc_routes_per_route_table
    • add Grafana dashboard: on-demand-ec2
    • new Prometheus metric that will expose the time it took to get the current/max value of each check
    Source code(tar.gz)
    Source code(zip)
  • 1.3.1(Mar 17, 2021)

  • 1.3.0(Mar 12, 2021)

    Changelog

    Added

    • now available as a Docker image, give it a try with docker run ghcr.io/brennerm/aws-quota-checker:latest
    • improve autocompletion support
    Source code(tar.gz)
    Source code(zip)
  • 1.2.0(Mar 9, 2021)

    Changelog

    Added

    • implement Prometheus exporter that provides access to all quota results

    Changed

    • display AWS account ID instead of profile name in check scope
    Source code(tar.gz)
    Source code(zip)
  • 1.1.0(Feb 27, 2021)

    Changelog

    Added

    • new check: ec2_on_demand_f_count
    • new check: ec2_on_demand_g_count
    • new check: ec2_on_demand_p_count
    • new check: ec2_on_demand_x_count
    • new check: ec2_on_demand_inf_count
    • new check: ec2_spot_f_count
    • new check: ec2_spot_g_count
    • new check: ec2_spot_p_count
    • new check: ec2_spot_x_count
    • new check: ec2_spot_inf_count
    • new check: sns_topics_count
    • new check: sns_pending_subscriptions_count
    • new check: sns_subscriptions_per_topic

    Changed

    • sort checks alphabetically by key
    Source code(tar.gz)
    Source code(zip)
  • 1.0.0(Feb 24, 2021)

Owner
Max
Automate all the things!
Max
Implement backup and recovery with AWS Backup across your AWS Organizations using a CI/CD pipeline (AWS CodePipeline).

Backup and Recovery with AWS Backup This repository provides you with a management and deployment solution for implementing Backup and Recovery with A

AWS Samples 8 Nov 22, 2022
Cloudkeeper is “housekeeping for clouds” - find leaky resources, manage quota limits, detect drift and clean up.

Cloudkeeper Housekeeping for Clouds! Table of contents Overview Docker based quick start Cloning this repository Component list Contact License Overvi

Some Engineering 1.2k Jan 3, 2023
Automated AWS account hardening with AWS Control Tower and AWS Step Functions

Automate activities in Control Tower provisioned AWS accounts Table of contents Introduction Architecture Prerequisites Tools and services Usage Clean

AWS Samples 20 Dec 7, 2022
pyhakuna is a client to access the API of the time keeping service hakuna.ch.

pyhakuna pyhakuna is a client to access the API of the time keeping service hakuna.ch. The Hakuna API is – unfortunately – personal and currently does

Christian Mäder 1 Feb 15, 2022
Automatically compile an AWS Service Control Policy that ONLY allows AWS services that are compliant with your preferred compliance frameworks.

aws-allowlister Automatically compile an AWS Service Control Policy that ONLY allows AWS services that are compliant with your preferred compliance fr

Salesforce 189 Dec 8, 2022
AWS Auto Inventory allows you to quickly and easily generate inventory reports of your AWS resources.

Photo by Denny Müller on Unsplash AWS Automated Inventory ( aws-auto-inventory ) Automates creation of detailed inventories from AWS resources. Table

AWS Samples 123 Dec 26, 2022
Aws-cidr-finder - A Python CLI tool for finding unused CIDR blocks in AWS VPCs

aws-cidr-finder Overview An Example Installation Configuration Contributing Over

Cooper Walbrun 18 Jul 31, 2022
This solution helps you deploy Data Lake Infrastructure on AWS using CDK Pipelines.

CDK Pipelines for Data Lake Infrastructure Deployment This solution helps you deploy data lake infrastructure on AWS using CDK Pipelines. This is base

AWS Samples 66 Nov 23, 2022
SSH-Restricted deploys an SSH compliance rule (AWS Config) with auto-remediation via AWS Lambda if SSH access is public.

SSH-Restricted SSH-Restricted deploys an SSH compliance rule with auto-remediation via AWS Lambda if SSH access is public. SSH-Auto-Restricted checks

Adrian Hornsby 30 Nov 8, 2022
A suite of utilities for AWS Lambda Functions that makes tracing with AWS X-Ray, structured logging and creating custom metrics asynchronously easier

A suite of utilities for AWS Lambda Functions that makes tracing with AWS X-Ray, structured logging and creating custom metrics asynchronously easier

Amazon Web Services - Labs 1.9k Jan 7, 2023
aws-lambda-scheduler lets you call any existing AWS Lambda Function you have in a future time.

aws-lambda-scheduler aws-lambda-scheduler lets you call any existing AWS Lambda Function you have in the future. This functionality is achieved by dyn

Oğuzhan Yılmaz 57 Dec 17, 2022
Project template for using aws-cdk, Chalice and React in concert, including RDS Postgresql and AWS Cognito

What is This? This repository is an opinonated project template for using aws-cdk, Chalice and React in concert. Where aws-cdk and Chalice are in Pyth

Rasmus Jones 4 Nov 7, 2022
POC de uma AWS lambda que executa a consulta de preços de criptomoedas, e é implantada na AWS usando Github actions.

Cryptocurrency Prices Overview Instalação Repositório Configuração CI/CD Roadmap Testes Overview A ideia deste projeto é aplicar o conteúdo estudado s

Gustavo Santos 3 Aug 31, 2022
Python + AWS Lambda Hands OnPython + AWS Lambda Hands On

Python + AWS Lambda Hands On Python Criada em 1990, por Guido Van Rossum. "Bala de prata" (quase). Muito utilizado em: Automatizações - Selenium, Beau

Marcelo Ortiz de Santana 8 Sep 9, 2022
Unauthenticated enumeration of services, roles, and users in an AWS account or in every AWS account in existence.

Quiet Riot ?? C'mon, Feel The Noise ?? An enumeration tool for scalable, unauthenticated validation of AWS principals; including AWS Acccount IDs, roo

Wes Ladd 89 Jan 5, 2023
AWS Blog post code for running feature-extraction on images using AWS Batch and Cloud Development Kit (CDK).

Batch processing with AWS Batch and CDK Welcome This repository demostrates provisioning the necessary infrastructure for running a job on AWS Batch u

AWS Samples 7 Oct 18, 2022
Aws-lambda-requests-wrapper - Request/Response wrapper for AWS Lambda with API Gateway

AWS Lambda Requests Wrapper Request/Response wrapper for AWS Lambda with API Gat

null 1 May 20, 2022
AWS-serverless-starter - AWS Lambda serverless stack via Serverless framework

Serverless app via AWS Lambda, ApiGateway and Serverless framework Configuration

 Bəxtiyar 3 Feb 2, 2022