Check provider logo

Elastic IP is associated with an instance or network interface

ec2_elastic_ip_unassigned

Severitylow
Serviceec2
by Prowler

EC2 Elastic IPs that are allocated but not associated with any instance or network interface. The evaluation identifies EIPs present in the account without an active association.

Risk

Unused Elastic IPs consume public IPv4 capacity and incur ongoing charges. Hoarded addresses can exhaust quotas, blocking new allocations and delaying deployments (availability). Lack of ownership tracking increases operational drift and misconfigurations, risking unintended exposure when later reassigned.

Run this check with Prowler CLI

prowler aws --checks ec2_elastic_ip_unassigned

Recommendation

Release unused Elastic IPs or promptly associate them only where required. Enforce least privilege for address allocation, apply tagging to track ownership, and schedule periodic audits. Prefer private networking or managed front ends to reduce public IPv4 use. Automate reclaiming of unassociated addresses in lifecycle policies.

Remediation

CLI

aws ec2 release-address --allocation-id <ALLOCATION_ID>

Native IaC
Terraform
Other
  1. In the AWS console, go to EC2 > Network & Security > Elastic IPs
  2. Select the Elastic IP with Status = Not associated
  3. Choose Actions > Associate Elastic IP address
  4. Select Instance (or Network interface), pick the target, and click Associate
  5. Alternatively, to remove the finding by deleting the unused EIP: Actions > Release Elastic IP address > Release

Source Code

Resource Type

AwsEc2Eip

References