rebuy-de /aws-nuke

Nuke a whole AWS account and delete all its resources.

★ 5,783⑂ 712👁 15⑃ 771● 475▤ 51
GoMITCreated 2016-11-27github.com/ekristen/aws-nuke
Download: v2.25.0v2.25.0 ↓2.25.02023-09-04
+0
Daily
5,783
stars
712
forks
15
watchers
771
prs
475
issues
51
releases

README

[!CAUTION]
 This repository for aws-nuke is no longer being actively maintained. We recommend users to switch to the actively maintained fork of this project at ekristen/aws-nuke.
 We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke.
 Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository.
 Thank you for your understanding and support.


 aws-nuke

!Build Status




Remove all resources from an AWS account.

 Development Status aws-nuke is stable, but it is likely that not all AWS
resources are covered by it. Be encouraged to add missing resources and create
a Pull Request or to create an Issue.

 Caution!

Be aware that aws-nuke is a very destructive tool, hence you have to be very
careful while using it. Otherwise you might delete production data.

We strongly advise you to not run this application on any AWS account, where
you cannot afford to lose all resources.

To reduce the blast radius of accidents, there are some safety precautions:

1. By default aws-nuke only lists all nukeable resources. You need to add
   --no-dry-run to actually delete resources.
2. aws-nuke asks you twice to confirm the deletion by entering the account
   alias. The first time is directly after the start and the second time after
   listing all nukeable resources.
3. To avoid just displaying a account ID, which might gladly be ignored by
   humans, it is required to actually set an Account
   Alias
   for your account. Otherwise aws-nuke will abort.
4. The Account Alias must not contain the string prod. This string is
   hardcoded and it is recommended to add it to every actual production account
   (eg mycompany-production-ecr).
5. The config file contains a blocklist field. If the Account ID of the account
   you want to nuke is part of this blocklist, aws-nuke will abort. It is
   recommended, that you add every production account to this blocklist.
6. To ensure you don't just ignore the blocklisting feature, the blocklist must
   contain at least one Account ID.
7. The config file contains account specific settings (eg. filters). The
   account you want to nuke must be explicitly listed there.
8. To ensure to not accidentally delete a random account, it is required to
   specify a config file. It is recommended to have only a single config file
   and add it to a central repository. This way the account blocklist is way
   easier to manage and keep up to date.

Feel free to create an issue, if you have any ideas to improve the safety
procedures.


 Use Cases

 We are testing our Terraform code with Jenkins.
  Sometimes a Terraform run fails during development and messes up the account.
  With aws-nuke we can simply clean up the failed account so it can be reused
  for the next build.
 Our platform develo

Latest release

v2.25.0 v2.25.0 2023-09-04
What's Changed
 Add EC2InstanceConnectEndpoint resource by @der-eismann in https://github.com/rebuy-de/aws-nuke/pull/1087
 Add elasticache user and group support by @swhite-oreilly in https://github.com/rebuy-de/aws-nuke/pull/1044
 Add support for CloudFront public keys and CloudFront key groups (873) by @npellegrin in https://github.com/rebuy-de/aws-nuke/pull/1065
 feat: MemoryDB resource support by @JTaylor-myenergi in https://github.com/rebuy-de/aws-nuke/pull/1079
 Stopped Executions before deleting step functions state machines by @suleman-sohail in https://github.com/rebuy-de/aws-nuk

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON