base on Nuke a whole AWS account and delete all its resources. > [!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](https://github.com/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  [](https://github.com/rebuy-de/aws-nuke/blob/main/LICENSE) [](https://github.com/rebuy-de/aws-nuke/releases) [](https://hub.docker.com/r/rebuy/aws-nuke) 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](https://github.com/rebuy-de/aws-nuke/issues/new). ## 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html) 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](https://www.terraform.io/) 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 developers have their own AWS Accounts where they can create their own Kubernetes clusters for testing purposes. With *aws-nuke* it is very easy to clean up these account at the end of the day and keep the costs low. ## Releases We usually release a new version once enough changes came together and have been tested for a while. You can find Linux, macOS and Windows binaries on the [releases page](https://github.com/rebuy-de/aws-nuke/releases), but we also provide containerized versions on [quay.io/rebuy/aws-nuke](https://quay.io/rebuy/aws-nuke) and [docker.io/rebuy/aws-nuke](https://hub.docker.com/r/rebuy/aws-nuke). Both are available for multiple architectures (amd64, arm64 & armv7). ## Usage At first you need to create a config file for *aws-nuke*. This is a minimal one: ```yaml regions: - eu-west-1 - global account-blocklist: - "999999999999" # production accounts: "000000000000": {} # aws-nuke-example ``` With this config we can run *aws-nuke*: ``` $ aws-nuke -c config/nuke-config.yml --profile aws-nuke-example aws-nuke version v1.0.39.gc2f318f - Fri Jul 28 16:26:41 CEST 2017 - c2f318f37b7d2dec0e646da3d4d05ab5296d5bce Do you really want to nuke the account with the ID 000000000000 and the alias 'aws-nuke-example'? Do you want to continue? Enter account alias to continue. > aws-nuke-example eu-west-1 - EC2DHCPOption - 'dopt-bf2ec3d8' - would remove eu-west-1 - EC2Instance - 'i-01b489457a60298dd' - would remove eu-west-1 - EC2KeyPair - 'test' - would remove eu-west-1 - EC2NetworkACL - 'acl-6482a303' - cannot delete default VPC eu-west-1 - EC2RouteTable - 'rtb-ffe91e99' - would remove eu-west-1 - EC2SecurityGroup - 'sg-220e945a' - cannot delete group 'default' eu-west-1 - EC2SecurityGroup - 'sg-f20f958a' - would remove eu-west-1 - EC2Subnet - 'subnet-154d844e' - would remove eu-west-1 - EC2Volume - 'vol-0ddfb15461a00c3e2' - would remove eu-west-1 - EC2VPC - 'vpc-c6159fa1' - would remove eu-west-1 - IAMUserAccessKey - 'my-user -> ABCDEFGHIJKLMNOPQRST' - would remove eu-west-1 - IAMUserPolicyAttachment - 'my-user -> AdministratorAccess' - [UserName: "my-user", PolicyArn: "arn:aws:iam::aws:policy/AdministratorAccess", PolicyName: "AdministratorAccess"] - would remove eu-west-1 - IAMUser - 'my-user' - would remove Scan complete: 13 total, 11 nukeable, 2 filtered. Would delete these resources. Provide --no-dry-run to actually destroy resources. ``` As we see, *aws-nuke* only lists all found resources and exits. This is because the `--no-dry-run` flag is missing. Also it wants to delete the administrator. We don't want to do this, because we use this user to access our account. Therefore we have to extend the config so it ignores this user: ```yaml regions: - eu-west-1 account-blocklist: - "999999999999" # production accounts: "000000000000": # aws-nuke-example filters: IAMUser: - "my-user" IAMUserPolicyAttachment: - "my-user -> AdministratorAccess" IAMUserAccessKey: - "my-user -> ABCDEFGHIJKLMNOPQRST" ``` ``` $ aws-nuke -c config/nuke-config.yml --profile aws-nuke-example --no-dry-run aws-nuke version v1.0.39.gc2f318f - Fri Jul 28 16:26:41 CEST 2017 - c2f318f37b7d2dec0e646da3d4d05ab5296d5bce Do you really want to nuke the account with the ID 000000000000 and the alias 'aws-nuke-example'? Do you want to continue? Enter account alias to continue. > aws-nuke-example eu-west-1 - EC2DHCPOption - 'dopt-bf2ec3d8' - would remove eu-west-1 - EC2Instance - 'i-01b489457a60298dd' - would remove eu-west-1 - EC2KeyPair - 'test' - would remove eu-west-1 - EC2NetworkACL - 'acl-6482a303' - cannot delete default VPC eu-west-1 - EC2RouteTable - 'rtb-ffe91e99' - would remove eu-west-1 - EC2SecurityGroup - 'sg-220e945a' - cannot delete group 'default' eu-west-1 - EC2SecurityGroup - 'sg-f20f958a' - would remove eu-west-1 - EC2Subnet - 'subnet-154d844e' - would remove eu-west-1 - EC2Volume - 'vol-0ddfb15461a00c3e2' - would remove eu-west-1 - EC2VPC - 'vpc-c6159fa1' - would remove eu-west-1 - IAMUserAccessKey - 'my-user -> ABCDEFGHIJKLMNOPQRST' - filtered by config eu-west-1 - IAMUserPolicyAttachment - 'my-user -> AdministratorAccess' - [UserName: "my-user", PolicyArn: "arn:aws:iam::aws:policy/AdministratorAccess", PolicyName: "AdministratorAccess"] - would remove eu-west-1 - IAMUser - 'my-user' - filtered by config Scan complete: 13 total, 8 nukeable, 5 filtered. Do you really want to nuke these resources on the account with the ID 000000000000 and the alias 'aws-nuke-example'? Do you want to continue? Enter account alias to continue. > aws-nuke-example eu-west-1 - EC2DHCPOption - 'dopt-bf2ec3d8' - failed eu-west-1 - EC2Instance - 'i-01b489457a60298dd' - triggered remove eu-west-1 - EC2KeyPair - 'test' - triggered remove eu-west-1 - EC2RouteTable - 'rtb-ffe91e99' - failed eu-west-1 - EC2SecurityGroup - 'sg-f20f958a' - failed eu-west-1 - EC2Subnet - 'subnet-154d844e' - failed eu-west-1 - EC2Volume - 'vol-0ddfb15461a00c3e2' - failed eu-west-1 - EC2VPC - 'vpc-c6159fa1' - failed eu-west-1 - S3Object - 's3://rebuy-terraform-state-138758637120/run-terraform.lock' - triggered remove Removal requested: 2 waiting, 6 failed, 5 skipped, 0 finished eu-west-1 - EC2DHCPOption - 'dopt-bf2ec3d8' - failed eu-west-1 - EC2Instance - 'i-01b489457a60298dd' - waiting eu-west-1 - EC2KeyPair - 'test' - removed eu-west-1 - EC2RouteTable - 'rtb-ffe91e99' - failed eu-west-1 - EC2SecurityGroup - 'sg-f20f958a' - failed eu-west-1 - EC2Subnet - 'subnet-154d844e' - failed eu-west-1 - EC2Volume - 'vol-0ddfb15461a00c3e2' - failed eu-west-1 - EC2VPC - 'vpc-c6159fa1' - failed Removal requested: 1 waiting, 6 failed, 5 skipped, 1 finished --- truncating long output --- ``` As you see *aws-nuke* now tries to delete all resources which aren't filtered, without caring about the dependencies between them. This results in API errors which can be ignored. These errors are shown at the end of the *aws-nuke* run, if they keep to appear. *aws-nuke* retries deleting all resources until all specified ones are deleted or until there are only resources with errors left. ### AWS Credentials There are two ways to authenticate *aws-nuke*. There are static credentials and profiles. The later one can be configured in the shared credentials file (ie `~/.aws/credentials`) or the shared config file (ie `~/.aws/config`). To use *static credentials* the command line flags `--access-key-id` and `--secret-access-key` are required. The flag `--session-token` is only required for temporary sessions. To use *shared profiles* the command line flag `--profile` is required. The profile must be either defined with static credentials in the [shared credential file](https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html) or in [shared config file](https://docs.aws.amazon.com/cli/latest/userguide/cli-roles.html) with an assuming role. ### Using custom AWS endpoint It is possible to configure aws-nuke to run against non-default AWS endpoints. It could be used for integration testing pointing to a local endpoint such as an S3 appliance or a Stratoscale cluster for example. To configure aws-nuke to use custom endpoints, add the configuration directives as shown in the following example: ```yaml regions: - demo10 # inspired by https://www.terraform.io/docs/providers/aws/guides/custom-service-endpoints.html endpoints: - region: demo10 tls_insecure_skip_verify: true services: - service: ec2 url: https://10.16.145.115/api/v2/aws/ec2 - service: s3 url: https://10.16.145.115:1060 - service: rds url: https://10.16.145.115/api/v2/aws/rds - service: elbv2 url: https://10.16.145.115/api/v2/aws/elbv2 - service: efs url: https://10.16.145.115/api/v2/aws/efs - service: emr url: https://10.16.145.115/api/v2/aws/emr - service: autoscaling url: https://10.16.145.115/api/v2/aws/autoscaling - service: cloudwatch url: https://10.16.145.115/api/v2/aws/cloudwatch - service: sns url: https://10.16.145.115/api/v2/aws/sns - service: iam url: https://10.16.145.115/api/v2/aws/iam - service: acm url: https://10.16.145.115/api/v2/aws/acm account-blocklist: - "account-id-of-custom-region-prod" # production accounts: "account-id-of-custom-region-demo10": ``` This can then be used as follows: ```buildoutcfg $ aws-nuke -c config/my.yaml --access-key-id <access-key> --secret-access-key <secret-key> --default-region demo10 aws-nuke version v2.11.0.2.gf0ad3ac.dirty - Tue Nov 26 19:15:12 IST 2019 - f0ad3aca55eb66b93b88ce2375f8ad06a7ca856f Do you really want to nuke the account with the ID account-id-of-custom-region-demo10 and the alias 'account-id-of-custom-region-demo10'? Do you want to continue? Enter account alias to continue. > account-id-of-custom-region-demo10 demo10 - EC2Volume - vol-099aa1bb08454fd5bc3499897f175fd8 - [tag:Name: "volume_of_5559b38e-0a56-4078-9a6f-eb446c21cadf"] - would remove demo10 - EC2Volume - vol-11e9b09c71924354bcb4ee77e547e7db - [tag:Name: "volume_of_e4f8c806-0235-4578-8c08-dce45d4c2952"] - would remove demo10 - EC2Volume - vol-1a10cb3f3119451997422c435abf4275 - [tag:Name: "volume-dd2e4c4a"] - would remove demo10 - EC2Volume - vol-1a2e649df1ef449686ef8771a078bb4e - [tag:Name: "web-server-5"] - would remove demo10 - EC2Volume - vol-481d09bbeb334ec481c12beee6f3012e - [tag:Name: "volume_of_15b606ce-9dcd-4573-b7b1-4329bc236726"] - would remove demo10 - EC2Volume - vol-48f6bd2bebb945848b029c80b0f2de02 - [tag:Name: "Data volume for 555e9f8a"] - would remove demo10 - EC2Volume - vol-49f0762d84f0439da805d11b6abc1fee - [tag:Name: "Data volume for acb7f3a5"] - would remove demo10 - EC2Volume - vol-4c34656f823542b2837ac4eaff64762b - [tag:Name: "wpdb"] - would remove demo10 - EC2Volume - vol-875f091078134fee8d1fe3b1156a4fce - [tag:Name: "volume-f1a7c95f"] - would remove demo10 - EC2Volume - vol-8776a0d5bd4e4aefadfa8038425edb20 - [tag:Name: "web-server-6"] - would remove demo10 - EC2Volume - vol-8ed468bfab0b42c3bc617479b8f33600 - [tag:Name: "web-server-3"] - would remove demo10 - EC2Volume - vol-94e0370b6ab54f03822095d74b7934b2 - [tag:Name: "web-server-2"] - would remove demo10 - EC2Volume - vol-9ece34dfa7f64dd583ab903a1273340c - [tag:Name: "volume-4ccafc2e"] - would remove demo10 - EC2Volume - vol-a3fb3e8800c94452aff2fcec7f06c26b - [tag:Name: "web-server-0"] - would remove demo10 - EC2Volume - vol-a53954e17cb749a283d030f26bbaf200 - [tag:Name: "volume-5484e330"] - would remove demo10 - EC2Volume - vol-a7afe64f4d0f4965a6703cc0cfab2ba4 - [tag:Name: "Data volume for f1a7c95f"] - would remove demo10 - EC2Volume - vol-d0bc3f2c887f4072a9fda0b8915d94c1 - [tag:Name: "physical_volume_of_39c29f53-eac4-4f02-9781-90512cc7c563"] - would remove demo10 - EC2Volume - vol-d1f066d8dac54ae59d087d7e9947e8a9 - [tag:Name: "Data volume for 4ccafc2e"] - would remove demo10 - EC2Volume - vol-d9adb3f084cd4d588baa08690349b1f9 - [tag:Name: "volume_of_84854c9b-98aa-4f5b-926a-38b3398c3ad2"] - would remove demo10 - EC2Volume - vol-db42e471b19f42b7835442545214bc1a - [tag:Name: "lb-tf-lb-20191126090616258000000002"] - would remove demo10 - EC2Volume - vol-db80932fb47243efa67c9dd34223c647 - [tag:Name: "web-server-5"] - would remove demo10 - EC2Volume - vol-dbea1d1083654d30a43366807a125aed - [tag:Name: "volume-555e9f8a"] - would remove --- truncating long output --- ``` ### Specifying Resource Types to Delete *aws-nuke* deletes a lot of resources and there might be added more at any release. Eventually, every resources should get deleted. You might want to restrict which resources to delete. There are multiple ways to configure this. One way are filters, which already got mentioned. This requires to know the identifier of each resource. It is also possible to prevent whole resource types (eg `S3Bucket`) from getting deleted with two methods. * The `--target` flag limits nuking to the specified resource types. * The `--exclude` flag prevent nuking of the specified resource types. It is also possible to configure the resource types in the config file like in these examples: ``` --- regions: - "eu-west-1" account-blocklist: - 1234567890 resource-types: # only nuke these three resources targets: - S3Object - S3Bucket - IAMRole accounts: 555133742: {} ``` ``` --- regions: - "eu-west-1" account-blocklist: - 1234567890 resource-types: # don't nuke IAM users excludes: - IAMUser accounts: 555133742: {} ``` If targets are specified in multiple places (eg CLI and account specific), then a resource type must be specified in all places. In other words each configuration limits the previous ones. If an exclude is used, then all its resource types will not be deleted. **Hint:** You can see all available resource types with this command: ``` aws-nuke resource-types ``` ### AWS Cloud Control API Support > This feature is not yet released and is probably part of `v2.18`. _aws-nuke_ supports removing resources via the AWS Cloud Control API. When executing _aws-nuke_ it will automatically remove a manually managed set of resources via Cloud Control. Only a subset of Cloud Control supported resources will be removed automatically, because there might be resources that were already implemented and adding them too would bypass existing filters in user configs as Cloud Control has another naming scheme and a different set of properties. Moreover, there are some Cloud Control resources that need special handling which is not yet supported by _aws-nuke_. Even though the subset of automatically supported Cloud Control resources is limited, you can can configure _aws-nuke_ to make it try any additional resource. Either via command line flags of via the config file. For the config file you have to add the resource to the`resource-types.cloud-control` list: ```yaml resource-types: cloud-control: - AWS::EC2::TransitGateway - AWS::EC2::VPC ``` If you want to use the command line, you have to add a `--cloud-control` flag for each resource you want to add: ```sh aws-nuke \ -c nuke-config.yaml \ --cloud-control AWS::EC2::TransitGateway \ --cloud-control AWS::EC2::VPC ``` **Note:** There are some resources that are supported by Cloud Control and are already natively implemented by _aws-nuke_. If you configure to use Cloud Control for those resources, it will not execute the natively implemented code for this resource. For example with the `--cloud-control AWS::EC2::VPC` it will not use the `EC2VPC` resource. ### Feature Flags There are some features, which are quite opinionated. To make those work for everyone, *aws-nuke* has flags to manually enable those features. These can be configured on the root-level of the config, like this: ```yaml --- feature-flags: disable-deletion-protection: RDSInstance: true EC2Instance: true CloudformationStack: true force-delete-lightsail-addons: true ``` ### Filtering Resources It is possible to filter this is important for not deleting the current user for example or for resources like S3 Buckets which have a globally shared namespace and might be hard to recreate. Currently the filtering is based on the resource identifier. The identifier will be printed as the first step of *aws-nuke* (eg `i-01b489457a60298dd` for an EC2 instance). **Note: Even with filters you should not run aws-nuke on any AWS account, where you cannot afford to lose all resources. It is easy to make mistakes in the filter configuration. Also, since aws-nuke is in continous development, there is always a possibility to introduce new bugs, no matter how careful we review new code.** The filters are part of the account-specific configuration and are grouped by resource types. This is an example of a config that deletes all resources but the `admin` user with its access permissions and two access keys: ```yaml --- regions: - global - eu-west-1 account-blocklist: - 1234567890 accounts: 0987654321: filters: IAMUser: - "admin" IAMUserPolicyAttachment: - "admin -> AdministratorAccess" IAMUserAccessKey: - "admin -> AKSDAFRETERSDF" - "admin -> AFGDSGRTEWSFEY" ``` Any resource whose resource identifier exactly matches any of the filters in the list will be skipped. These will be marked as "filtered by config" on the *aws-nuke* run. #### Filter Properties Some resources support filtering via properties. When a resource support these properties, they will be listed in the output like in this example: ``` global - IAMUserPolicyAttachment - 'admin -> AdministratorAccess' - [RoleName: "admin", PolicyArn: "arn:aws:iam::aws:policy/AdministratorAccess", PolicyName: "AdministratorAccess"] - would remove ``` To use properties, it is required to specify a object with `properties` and `value` instead of the plain string. These types can be used to simplify the configuration. For example, it is possible to protect all access keys of a single user: ```yaml IAMUserAccessKey: - property: UserName value: "admin" ``` #### Filter Types There are also additional comparision types than an exact match: * `exact` – The identifier must exactly match the given string. This is the default. * `contains` – The identifier must contain the given string. * `glob` – The identifier must match against the given [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)). This means the string might contains wildcards like `*` and `?`. Note that globbing is designed for file paths, so the wildcards do not match the directory separator (`/`). Details about the glob pattern can be found in the [library documentation](https://godoc.org/github.com/mb0/glob). * `regex` – The identifier must match against the given regular expression. Details about the syntax can be found in the [library documentation](https://golang.org/pkg/regexp/syntax/). * `dateOlderThan` - The identifier is parsed as a timestamp. After the offset is added to it (specified in the `value` field), the resulting timestamp must be AFTER the current time. Details on offset syntax can be found in the [library documentation](https://golang.org/pkg/time/#ParseDuration). Supported date formats are epoch time, `2006-01-02`, `2006/01/02`, `2006-01-02T15:04:05Z`, `2006-01-02T15:04:05.999999999Z07:00`, and `2006-01-02T15:04:05Z07:00`. To use a non-default comparision type, it is required to specify an object with `type` and `value` instead of the plain string. These types can be used to simplify the configuration. For example, it is possible to protect all access keys of a single user by using `glob`: ```yaml IAMUserAccessKey: - type: glob value: "admin -> *" ``` #### Using Them Together It is also possible to use Filter Properties and Filter Types together. For example to protect all Hosted Zone of a specific TLD: ```yaml Route53HostedZone: - property: Name type: glob value: "*.rebuy.cloud." ``` #### Inverting Filter Results Any filter result can be inverted by using `invert: true`, for example: ```yaml CloudFormationStack: - property: Name value: "foo" invert: true ``` In this case *any* CloudFormationStack ***but*** the ones called "foo" will be filtered. Be aware that *aws-nuke* internally takes every resource and applies every filter on it. If a filter matches, it marks the node as filtered. #### Filter Presets It might be the case that some filters are the same across multiple accounts. This especially could happen, if provisioning tools like Terraform are used or if IAM resources follow the same pattern. For this case *aws-nuke* supports presets of filters, that can applied on multiple accounts. A configuration could look like this: ```yaml --- regions: - "global" - "eu-west-1" account-blocklist: - 1234567890 accounts: 555421337: presets: - "common" 555133742: presets: - "common" - "terraform" 555134237: presets: - "common" - "terraform" filters: EC2KeyPair: - "notebook" presets: terraform: filters: S3Bucket: - type: glob value: "my-statebucket-*" DynamoDBTable: - "terraform-lock" common: filters: IAMRole: - "OrganizationAccountAccessRole" ``` ## Install ### For macOS `brew install aws-nuke` ### Use Released Binaries The easiest way of installing it, is to download the latest [release](https://github.com/rebuy-de/aws-nuke/releases) from GitHub. #### Example for Linux Intel/AMD Download and extract `$ wget -c https://github.com/rebuy-de/aws-nuke/releases/download/v2.25.0/aws-nuke-v2.25.0-linux-amd64.tar.gz -O - | tar -xz -C $HOME/bin` Run `$ aws-nuke-v2.25.0-linux-amd64` ### Compile from Source To compile *aws-nuke* from source you need a working [Golang](https://golang.org/doc/install) development environment. The sources must be cloned to `$GOPATH/src/github.com/rebuy-de/aws-nuke`. Also you need to install [golint](https://github.com/golang/lint/) and [GNU Make](https://www.gnu.org/software/make/). Then you just need to run `make build` to compile a binary into the project directory or `make install` go install *aws-nuke* into `$GOPATH/bin`. With `make xc` you can cross compile *aws-nuke* for other platforms. ### Docker You can run *aws-nuke* with Docker by using a command like this: ```bash $ docker run \ --rm -it \ -v /full-path/to/nuke-config.yml:/home/aws-nuke/config.yml \ -v /home/user/.aws:/home/aws-nuke/.aws \ quay.io/rebuy/aws-nuke:v2.25.0 \ --profile default \ --config /home/aws-nuke/config.yml ``` To make it work, you need to adjust the paths for the AWS config and the *aws-nuke* config. Also you need to specify the correct AWS profile. Instead of mounting the AWS directory, you can use the `--access-key-id` and `--secret-access-key` flags. Make sure you use the latest version in the image tag. Alternatiely you can use `main` for the latest development version, but be aware that this is more likely to break at any time. ## Testing ### Unit Tests To unit test *aws-nuke*, some tests require [gomock](https://github.com/golang/mock) to run. This will run via `go generate ./...`, but is automatically run via `make test`. To run the unit tests: ```bash make test ``` ## Contact Channels Feel free to create a GitHub Issue for any bug reports or feature requests. Please use our mailing list for questions: [email protected]. You can also search in the mailing list archive, whether someone already had the same problem: https://groups.google.com/d/forum/aws-nuke ## Contribute You can contribute to *aws-nuke* by forking this repository, making your changes and creating a Pull Request against our repository. If you are unsure how to solve a problem or have other questions about a contributions, please create a GitHub issue. ", Assign "at most 3 tags" to the expected json: {"id":"4172","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"