Elastic IP not associated with any resource
- Severity
- Low
- Service
- EC2
- Check ID
- EIP_UNASSOCIATED
What this check finds
An unassociated Elastic IP address incurs a charge of $0.005/hour (~$3.65/month) per AWS pricing. Unassociated EIPs provide no value and are commonly left behind after instance or NAT gateway deletion.
Passing looks like: All Elastic IPs associated.
How to fix it
Release the Elastic IP if it is no longer needed.
AWS CLI
aws ec2 release-address --allocation-id ALLOCATION_ID
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
EC2 → Elastic IPs → select address → Actions → Release Elastic IP addresses.
Compliance
This is a cost check. It flags spend that buys nothing, which no compliance framework asks about, so it is not mapped to a control.
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More EC2 checks
- HighAccount does not block public sharing of EBS snapshots
- HighAMI is publicly shared
- HighEBS snapshot is public
- HighEC2 instance CPU spiked abnormally — possible compromise or runaway process
- HighEC2 instance has an IAM role with admin privileges
- MediumAccount default for instance metadata does not require IMDSv2
- MediumEBS default encryption is not enabled for this region
- MediumEBS volume is not encrypted at rest