v0.7.1

#243: Adds support for deleting non-default VPCs. Thanks to @ekristen for this contribution!

v0.7.0

#238: cloud-nuke will now delete OpenSearch Service domains (formerly called AWS Elasticsearch Service). If you wish to avoid nuking OpenSearch domains, you can either pass in --exclude-resource-type opensearch, or specify a config file.

#234: Fixed bug where cloud-nuke did not nuke EKS clusters that had compute resources. With this release, cloud-nuke will now handle nuking Managed Node groups and Fargate profiles attached to EKS clusters eligible for nuking.

v0.6.0

#233: Cloud nuke will now delete CloudWatch Dashboards. If you wish to avoid nuking Dashboards, you can either pass in --exclude-resource-type cloudwatch-dashboard, or specify a config file.

v0.5.2

#169: Add support for nuking DynamoDB
#223 Limit parallelism of gox to stabilize build stage
#221 Update circleci config fix 32 bit builds & use GW utils
#214, #216 Fix nuke-config for internal Gruntwork usage

Special thanks to @DMEvanCT for their contribution!

v0.5.1

#205: Fix Config file not including when there is a 'exclude' rule
#209: Adds new default enabled region (ap-northeast-3)

Special thanks to @ashwiniag for their contribution!

v0.5.0

#201: Cloud nuke will now delete AWS ACM Private Certificate Authorities. If you wish to avoid nuking PCAs, you can pass in --exclude-resource-type acmpca.

Special thanks to @weitzj for their contribution!

v0.4.0

#202: Cloud nuke will now delete AWS IAM Access Analyzers. If you wish to avoid nuking IAM Access Analyzers, you can either pass in --exclude-resource-type accessanalyzer, or specify a config file.

v0.3.0

#197: Cloud nuke will now delete NAT gateways. If you wish to avoid nuking NAT gateways, you can either pass in --exclude-resource-type nat-gateway, or specify a config file.

v0.2.0

#194: Cloud nuke will now delete secrets manager secrets. If you wish to avoid nuking secrets manager entries, you can either pass in --exclude-resource-type secretsmanager, or specify a config file.

Release practice change

⚠️ Starting this release, new resources nuked by cloud-nuke will be marked as a minor version bump (X in v0.X.Y) to indicate backward incompatibilities. Previously, all new resources were considered backward compatible, but since new resources are included automatically (opt-out vs opt-in), users with CI practices around cloud-nuke would be surprised by new resources that are suddenly being picked up for deletion. This surprise is stronger for resources that are actively in use for any account, such as IAM Users.

As such, we have decided to mark the addition of new nuked resources as backward incompatible releases to provide better signals for users when we introduce a new resource.

v0.1.30

#184: cloud-nuke now supports nuking SQS queues.

Special thanks to @rafaelleonardocruz for the contribution!