aws-nuke doesn't remove IPAM resources.

[timbaileyjones]

After running aws-nuke on an account containing an IPAM resources, I re-ran my Terraform IaC which recreates it (aws_vpc_ipam). I got:

│ Error: Error creating ipam: ResourceLimitExceeded: You've reached the limit for ipams. You have created 1 ipams and you are limited to 1.

Expected behavior:

• I expected aws-nuke to destroy the IPAM resource.

[ad-m-ss]

I expected aws-nuke to destroy the IPAM resource.

IPAM is not a supported resource by aws-nuke to manage at that moment. Could you try to use CloudControl for that? The implementation should be pretty straightforward:

aws-nuke/resources/cloudcontrol.go

Lines 24 to 37 in e36ec1a

	registerCloudControl("AWS::AppFlow::ConnectorProfile")
	registerCloudControl("AWS::AppFlow::Flow")
	registerCloudControl("AWS::AppRunner::Service")
	registerCloudControl("AWS::ApplicationInsights::Application")
	registerCloudControl("AWS::Backup::Framework")
	registerCloudControl("AWS::MWAA::Environment")
	registerCloudControl("AWS::Synthetics::Canary")
	registerCloudControl("AWS::Timestream::Database")
	registerCloudControl("AWS::Timestream::ScheduledQuery")
	registerCloudControl("AWS::Timestream::Table")
	registerCloudControl("AWS::Transfer::Workflow")
	registerCloudControl("AWS::NetworkFirewall::Firewall")
	registerCloudControl("AWS::NetworkFirewall::FirewallPolicy")
	registerCloudControl("AWS::NetworkFirewall::RuleGroup")

[Alphasite]

I don't believe this works as there are IPAM allocations which need to be released as well before it lets you.

[timbaileyjones]

I have a wrapper script around aws-nuke that deletes a number of such things after aws-nuke runs. You can easily delete an entire ipam with this command:

aws ec2 delete-ipam --ipam-id "${ipam_id}" --cascade

The --cascade option will delete all the attached scopes and pools. Very helpful!

Hope this helps, in the meantime.

[ekristen]

Closing due to age, if this is still an issue, please open an issue at https://github.com/ekristen/aws-nuke

---

Please see the copy of the notice from the README about the deprecation of this project. Sven was kind enough to grant me access to help triage and close issues and pull requests that have already been addressed in the actively maintained fork. Some additional information is located in the welcome issue for more information.

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.