Step 1 — List Elastic IP Addresses
- Open EC2 → Network & Security → Elastic IPs.
- Look for rows with no associated instance / empty association.
- Also check addresses tied to terminated labs you no longer need.
Release Unused Elastic IPs
Start here
Why Release Elastic IPs?
An Elastic IP stays in your account until you release it. If it sits unused (not associated with a running instance), you can still pay for that public IPv4—and it counts against your Region quota.
Lab habit.
When a tutorial ends, disassociate if needed, then release. Treat EIP cleanup like turning off unused EC2.
Why it matters
In Simple Words
Disassociate vs release
Disassociate = unplug the address from the network interface / instance but keep owning it. Release = give the address back to AWS permanently.
When should you release?
After deleting a demo instance, finishing a course lab, or when the Elastic IPs list shows Association ID empty and you do not plan to reuse that address.
Do not release production addresses.
Update DNS and allow lists first. Releasing breaks anything that still points at that IPv4.
Dictionary
Words You Will See
| Word | Plain meaning |
|---|---|
Allocate | Get a new Elastic IP into your account |
Associate | Attach the EIP to an instance / ENI |
Disassociate | Detach but keep the EIP allocated |
Release | Return the EIP to AWS; you no longer own it |
Idle / unassociated | Allocated EIP with no running association—cleanup candidate |
Checklist
What You Need First
- Permission to manage Elastic IPs in the Region.
- Certainty that no DNS, partner allow list, or live site still needs that address.
Follow along
Step-by-Step
Step 2 — Disassociate (If Still Attached)
- Select the Elastic IP.
- Actions → Disassociate Elastic IP address.
- Confirm. The address stays in your account until release.
How It Works
- Disassociate unhooks the ENI mapping described in network interfaces.
- You cannot release some attached addresses until they are free—disassociate first.
Step 3 — Release the Address
- Select the unassociated Elastic IP.
- Actions → Release Elastic IP addresses.
- Confirm. The IPv4 leaves your account.
How It Works
- Release frees quota and stops idle public IPv4 charges for that address.
- Need another EIP later? Allocate a new one from the Elastic IP guide.
Avoid these
Common Beginner Mistakes
Releasing a live site IP
Update Route 53 / DNS before release, or traffic fails.
Only terminating EC2
Terminating the instance does not always release the EIP automatically.
Wrong Region
Elastic IPs are Regional—check the console Region switcher.
Disassociate without release
Idle allocated EIPs can still cost money. Release when done.
Remember
Key Takeaways
One line: find idle Elastic IPs, disassociate if needed, then release so they stop billing.
Frequently Asked Questions
AWS bills for public IPv4 addresses that stay allocated to your account when they are not associated with a running instance. Releasing unused EIPs stops that idle charge.
Disassociate unbinds the EIP from an ENI/instance but keeps the address in your account. Release returns the address to AWS so you no longer own it.
Usually no. After release, the address goes back to Amazon’s pool. Allocate a new one if you need another EIP.
No. Only release addresses you no longer need. Releasing a live EIP breaks SSH, DNS, and allow lists that pointed at it.
Pricing focuses on idle (unassociated) public IPv4s. Always check the current AWS public IPv4 pricing page for your Region and use case.
An EIP associates to a private IP on a network interface (ENI). Disassociate from that ENI before you release if the address is still attached.
Need a new Elastic IP?
Allocate and associate a fresh address for your next lab.
About the author
8 people found this page helpful