Why it matters
Idle Elastic IPs are a pure cost. They are often left behind after an instance or NAT gateway is deleted.How nOps finds it
nOps reads the last 30 days of public IPv4 billing. An address is flagged when it was billed as idle on at least 28 of those days, including the last 2 days, and was never billed as in use. The saving is its idle charge over the last 30 days, and must be at least $1.Before you start
Permission to release addresses (ec2:ReleaseAddress). Confirm the address is not allow-listed by a partner, customer or firewall.
How to implement
- Check that the address has no association and note the IP:
aws ec2 describe-addresses --allocation-ids ID. - Search your DNS records and partner allow-lists for the IP.
- Release it: EC2 → Elastic IPs → Actions → Release Elastic IP addresses, or
aws ec2 release-address --allocation-id ID. - Remove it from Terraform or CloudFormation so it is not recreated.
Risks and considerations
- A released address usually cannot be recovered, so anything that allow-lists it needs to be updated.
- If the address is kept on purpose for a planned failover, keep it and accept the charge.