v0.12.0

#320: cloud-nuke will now delete GuardDuty Detectors. If you wish to avoid nuking GuardDuty Detectors, you can pass in --exclude-resource-type guardduty.

v0.11.8

#305 Extend cloud-nuke with non-destructive inspect command and library methods

This release adds a non-destructive command, inspect-aws, which accepts most of the same flags as nuke but will never delete resources. As aws / nuke is to DELETE, aws-inspect is to LIST or READ.

You can use inspect-aws to list and search for resources across your AWS accounts.

In addition, this release adds library functionality that allows you to script against cloud-nuke. See Using cloud-nuke as a library for more information.

This release fixes the regression bug with --exclude-resource-type that was introduced in v0.11.7

v0.11.7

IMPORTANT

A major regression bug has been identified in this release, where --exclude-resource-type no longer works as intended. We advise users not to use this version to avoid nuking resources unintentionally.

Please use v0.11.8

v0.11.6

#294: Removal of S3 BucketPolicy before nuke bucket

Special thanks

Special thanks to @maxhaensel for their contribution!

v0.11.5

#293 : VPCEs deletion before subnets removal

Special thanks

Special thanks to @sHesl for their contribution!

v0.11.4

#295: Added support for config file to control EKS cluster nuking.

v0.11.3

#291 updates VPC config to filter by name instead of VPC Id.

Special thanks

Special thanks to @brandonstrohmeyer for their contribution!

v0.11.2

#287 ElasticIPs, AutoScalingGroups, LaunchConfigurations and EC2 instances can now be filtered by the config file using their names.

Special thanks

Special thanks to @brandonstrohmeyer for their contribution!

v0.11.1

#284: KMS Customer Managed Key deletion now supports the config file format to filter by alias.

v0.11.0

cloud-nuke will now delete CloudWatch Log Groups. If you wish to avoid nuking Log Groups, you can either pass in --exclude-resource-type cloudwatch-loggroup, or specify a config file.

Special thanks

Special thanks to @ekristen for their contribution!