PAGES
← all tools
◆ Cloud Security Posture

cloud-nuke

v0.52.0 open-source

cloud-nuke is a CLI tool to delete all resources in your cloud account, designed for cleaning up test accounts and removing leftover resources.

Summary

cloud-nuke is an open-source command-line tool, free to use, that deletes resources across a cloud account, covering 125+ AWS resource types plus a growing set of GCP resources like Cloud Functions and Artifact Registry. It runs as a single binary you install from the releases page or a package manager, and is aimed at platform and DevOps teams cleaning up test accounts, removing leftover infrastructure, or stripping default VPCsVPCsVirtual Private Clouds — isolated, software-defined network environments inside a public cloud provider such as AWS, Azure, or GCP — give cyber tools a controlled network boundary with configurable routing, subnets, and access rules. and permissive security group rules before an environment goes live. Filtering by region, resource type, or tag lets a run be scoped rather than total, and a dry-run mode previews what would be deleted first, which matters given the README's own warning that a full run is highly destructive and unsuited to production. Maintained by Gruntwork, it has drawn 102 contributors and 337 commits in the past year, with a release 69 days ago, indicating active upkeep.

cloud-nuke is a CLI tool to delete all resources in your cloud account, designed for cleaning up test accounts and removing leftover resources.

How cloud-nuke helps

What resources are sitting in this account before anything gets deleted?

lists every matching resource across the account by scanning each supported type and region, so the inventory is visible before a run touches anything

Which leftover resources are actually costing money in a test account right now?

scans across regions and 125+ resource types in one pass, surfacing everything left running so unused infrastructure can be identified before it accrues further cost

Can I clean up just the S3 buckets and EC2 instances in one region without touching the rest of the account?

filters a run by region and by resource type, so deletion is scoped to exactly the types and places named

Will this run wipe out resources I actually still need?

offers a preview mode that reports what would be deleted without deleting it, so the list can be checked against expectations first

Which resources belong to a specific team or project so only theirs get removed?

matches resources by tag, so a run can be limited to (or exclude) whatever carries a given tag

Are the default VPCs and permissive security group rules still open in an account about to go live?

a dedicated mode finds and removes default VPCs and the default ingress/egress rules on default security groups, separately from the full destructive run

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities

Built from cloud-nuke's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What cloud-nuke offers you

  • Command-line interface5
All capabilities 13 capabilities
Multi-cloud resource support shipped Adds deletion capabilities for specific AWS resource types including DynamoDB, ElastiCache, OpenSearch, IAM OIDC providers, KMS keys, CloudWatch Log Groups, GuardDuty detectors, SageMaker notebooks, Kinesis streams, IAM groups and policies, EC2 key pairs, CloudWatch Alarms, Redshift clusters, API Gateway client certificates, DB parameter groups, S3 access points, SES resources, Route53 resources, MSK clusters, and Elastic Beanstalk applications. 72 releases · 3 other sources · first seen Oct 2018

Shared capability: OIDC SSO

release 72 total

  • New backup-plan resource type enables nuking of AWS Backup plans. v0.51.0 · Jun 2026 · source · release history
  • Adds support for nuking RDS cluster snapshots (rds-cluster-snapshot resource type). v0.49.0 · Apr 2026 · source · release history
  • Adds support for nuking AWS RAM ResourceShares (resource-shares resource type). v0.49.0 · Apr 2026 · source · release history
  • Adds support for nuking Amazon MQ broker resources. v0.49.0 · Apr 2026 · source · release history
  • Adds SSM Parameter Store as a supported resource type for discovery and deletion. v0.48.0 · Mar 2026 · source · release history
  • Adds GCP Artifact Registry as a nuke-able resource type. v0.47.0 · Mar 2026 · source · release history

example

  • Nuke only IAM instance profiles in a sandbox account to clean up leftover EC2 role associations. cloud-nuke aws --resource-type iam_instance_profile --region us-east-1 v0.40.0 · Mar 2025 · source
  • Nuke all resources except OpenSearch domains by using the exclusion flag. cloud-nuke --exclude-resource-type opensearch v0.7.0 · Nov 2021 · source
  • Delete all supported resources except NAT gateways in the current AWS account cloud-nuke --exclude-resource-type nat-gateway v0.3.0 · Jun 2021 · source
Selective resource exclusion shipped Allows users to exclude specific resource types or names from nuking operations via CLI flags or configuration files. 41 releases · 8 other sources · first seen Apr 2020

release 41 total

  • Adds tag filtering support for Security Hub. v0.49.0 · Apr 2026 · source · release history
  • Adds tag filtering support for Backup Vault resources. v0.49.0 · Apr 2026 · source · release history
  • Adds tag filtering support for Lambda, Kinesis, SNS, SQS, and ECR resources. v0.49.0 · Apr 2026 · source · release history
  • Adds tag filtering support for ACM, CloudFront, SageMaker, and miscellaneous resources. v0.49.0 · Apr 2026 · source · release history
  • Adds tag filtering support for CodeDeploy applications. v0.49.0 · Apr 2026 · source · release history
  • Adds tag filtering support for EC2, ELB, and VPC Lattice resources. v0.49.0 · Apr 2026 · source · release history

example 8 total

  • Configure cloud-nuke to permanently skip OpenSearch domains via a config file. # Add to your config file: resource_types: exclude: - opensearch v0.7.0 · Nov 2021 · source
  • Nuke all supported cloud resources except ACM Private Certificate Authorities cloud-nuke --all --exclude-resource-type acmpca v0.5.0 · Aug 2021 · source
  • Nuke all AWS resources while preserving Access Analyzers. cloud-nuke aws --exclude-resource-type accessanalyzer v0.4.0 · Jul 2021 · source
  • Configure cloud-nuke to permanently exclude NAT gateways from all future runs via config file # Add the following to your cloud-nuke config file (default ~/.config/cloud-nuke/config.yaml): resources: excluded_types: - "nat-gateway" v0.3.0 · Jun 2021 · source
  • Example config snippet to exclude secretsmanager # In .config/cloud-nuke/config.yaml exclude_resource_types: - secretsmanager v0.2.0 · Jun 2021 · source
  • Exclude Secrets Manager from nuking to prevent accidental deletion of active secrets cloud-nuke aws --exclude-resource-type secretsmanager v0.2.0 · Jun 2021 · source
Default resource deletion support shipped Provides capabilities to detect and delete default VPCs, security group rules, and other standard cloud account configurations. 4 releases · 5 other sources · first seen Aug 2019

Also counts toward: Command-line interface

release

  • defaults-aws now accepts --region and --exclude-region flags to reduce scope when nuking default VPCs and security group rules. v0.1.13 · Dec 2019 · source · release history
  • Adds --sg-only option to skip nuking default VPCs and only nuke default security group rules. v0.1.13 · Dec 2019 · source · release history
  • Adds the cloud-nuke defaults-aws subcommand that identifies and removes default VPCs and their associated resources across all enabled AWS regions. v0.1.8 · Aug 2019 · source · release history
  • Adds support for the --force flag in cloud-nuke defaults-aws to enable non-interactive execution. v0.1.8 · Aug 2019 · source · release history

example

  • Preview what default VPCs and security group rules would be removed in a region before actually deleting them. cloud-nuke defaults-aws --dry-run v0.51.0 · Jun 2026 · source
  • Limit default VPC and SG cleanup to a single AWS region instead of running globally. cloud-nuke defaults-aws --region us-east-1 v0.1.13 · Dec 2019 · source
  • Nuke only default security group rules, ignoring default VPCs. cloud-nuke defaults-aws --sg-only v0.1.13 · Dec 2019 · source
  • Non-interactively remove all default VPCs and security groups from your AWS account for compliance or cleanup. ./cloud-nuke defaults-aws --force v0.1.8 · Aug 2019 · source
  • Delete default VPCs and security group rules cloud-nuke defaults-aws
Parallel multi-region resource deletion shipped Scans and deletes resources across regions and resource types concurrently under a single global concurrency cap, with a configurable parallelism level and dependency-aware ordering that handles global resources last. 5 releases · 3 other sources · first seen Apr 2020

release

  • Enables concurrent nuking of regional resources while preserving within-region dependency order; global resources (IAM, Route53, CloudFront) are deleted last. v0.52.0 · Jun 2026 · source · release history
  • Library consumers: aws.NukeAllResources and gcp.NukeAllResources now take an additional parallelism int parameter. v0.52.0 · Jun 2026 · source · release history
  • Breaking change for library consumers: aws.NukeAllResources and gcp.NukeAllResources now require an additional parallelism int parameter. v0.52.0 · Jun 2026 · source · release history
  • Adds --parallelism flag (default 10) to control concurrent scanning and deletion of regions and resource types under a single global concurrency cap. v0.52.0 · Jun 2026 · source · release history
  • Speeds up S3 bucket enumeration by fetching bucket info concurrently (5-10x faster). v0.1.18 · Apr 2020 · source · release history

example

  • Speed up a full AWS account cleanup across many regions by raising the concurrency well above the default of 10. cloud-nuke aws --region us-east-1 --region us-west-2 --region eu-west-1 --parallelism 25 v0.52.0 · Jun 2026 · source
  • Throttle parallelism to 3 when nuking a large account where API rate limits are a concern, while still scanning concurrently. cloud-nuke aws --parallelism 3 --resource-type ec2 --resource-type s3 --dry-run v0.52.0 · Jun 2026 · source
  • Delete all AWS ECS clusters older than 10 minutes using the new resource type support. cloud-nuke aws --resource-type ecscluster --older-than 10m v0.1.22 · Oct 2020 · source
Resource inspection shipped Provides the ability to list or search for resources without deleting them. 2 releases · 2 other sources · first seen Jun 2020

Also counts toward: Command-line interface

release

  • Config YAML keys are now case-sensitive and must match Go struct names exactly (e.g., s3 → S3, NatGateway → NATGateway, EcsCluster → ECSCluster, EksCluster → EKSCluster, RdsParameterGroup → RDSParameterGroup); old keys are rejected with errors. v0.47.0 · Mar 2026 · source · release history
  • Adds the inspect-aws subcommand to list or search for AWS resources without deleting anything. v0.11.8 · Jun 2022 · source · release history

example

  • Use the updated tags map syntax in your nuke config to filter resources by tag instead of the removed tag/tag_value fields. # nuke_config.yml S3: include: tags: Environment: staging v0.47.0 · Mar 2026 · source
  • Filter nuked resources using an external YAML configuration file. cloud-nuke --config my-filters.yaml v0.1.20 · Jun 2020 · source
Resource type support for ECS clusters shipped Enables detection and deletion of AWS ECS cluster resources. 3 releases · 1 other source · first seen Jun 2020

Also counts toward: Command-line interface

release

  • Supports filtering ecscluster resources by age using the --older-than CLI argument. v0.1.22 · Oct 2020 · source · release history
  • New ecscluster value for the --resource-type flag. v0.1.22 · Oct 2020 · source · release history
  • Adds --config CLI flag to specify a configuration file for complex resource filtering v0.1.20 · Jun 2020 · source · release history

example

  • Nuke all Lambda functions in the current AWS profile cloud-nuke --resource-type lambda v0.1.24 · Nov 2020 · source
Dry-run and preview capabilities shipped Allows users to inspect potential deletions for general resources or specific default configurations without committing changes. 1 release · 1 other source · first seen Jun 2026

Also counts toward: Command-line interface

release

  • Adds --dry-run flag to the defaults-aws command to preview which default VPCs and security group rules would be deleted before committing. v0.51.0 · Jun 2026 · source · release history

example

  • Preview what would be deleted cloud-nuke aws --dry-run
Resource discovery and deletion reporting shipped Enhances the resource nuking process by providing detailed results for each operation rather than just generic success/failure. 2 releases · first seen Oct 2018

release

  • Nuke() now returns []NukeResult instead of error. v0.47.0 · Mar 2026 · source · release history
  • Continues nuking on individual resource errors instead of failing the entire run v0.1.3 · Oct 2018 · source · release history
Deletion protection handling shipped Automatically disables deletion protection on supported resources before nuking them. 2 releases · first seen Mar 2025

release

  • Adds deletion-protection handling for RDS clusters, automatically disabling it before deletion. v0.43.0 · Sep 2025 · source · release history
  • Automatically disables deletion protection on supported resources before nuking, unblocking previously protected resources. v0.40.0 · Mar 2025 · source · release history
Configurable log verbosity shipped Allows users to control the detail level of operational logs via CLI flags. 1 release · 1 other source · first seen Apr 2020

release

  • Adds --log-level flag to control the log verbosity of cloud-nuke. v0.1.18 · Apr 2020 · source · release history

example

  • Set verbose logging to debug specific cloud resource operations. cloud-nuke --log-level debug v0.1.18 · Apr 2020 · source
Multi-region resource support shipped Adds support for targeting AWS China regions. 1 release · first seen Dec 2024

release

  • Adds support for AWS China region, enabling cloud-nuke to target China-region resources. v0.38.0 · Dec 2024 · source · release history
RDS subnet group deletion support shipped Enables detection and deletion of AWS RDS DB subnet groups. 1 release · first seen Jul 2023

release

  • Implements nukeAllRdsDbSubnetGroups to delete all RDS subnet groups v0.32.0 · Jul 2023 · source · release history
Resource type support for Lambda functions shipped Enables detection and deletion of AWS Lambda function resources. 1 release · first seen Nov 2020

Also counts toward: Command-line interface

release

  • Adds --resource-type lambda flag to enable nuking AWS Lambda functions v0.1.24 · Nov 2020 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for cloud-nuke, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail cloud-nuke puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

56 entries

  1. June 20263
  2. April 20261
  3. March 20262
  4. December 20251
  5. October 20251
  6. September 20251
  7. August 20251
  8. June 20251
  9. March 20252
  10. December 20241
  11. August 20241
  12. July 20241
  13. May 20241
  14. April 20241
  15. March 20241
  16. November 20231
  17. July 20231
  18. May 20232
  19. April 20232
  20. February 20232
  21. January 20231
  22. December 20221
  23. October 20221
  24. July 20224
  25. June 20221
  26. March 20222
  27. February 20221
  28. January 20223
  29. November 20213
  30. August 20211
  31. July 20211
  32. June 20212
  33. November 20201
  34. October 20201
  35. June 20201
  36. April 20202
  37. December 20191
  38. August 20191
  39. October 20181
    Show

    56 entries

    Project health

    Issue, contributor and maintainer activity in gruntwork-io/cloud-nuke, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 8 −4 vs prior 12 months
    2. Maintainers 1 +0 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 97% of issues opened, last 12 months
    5. Median time to close 7.3 days first maintainer reply 5.7 days
    6. Open backlog 0 of 367 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 3,187
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →