Unused Elastic IPs and EBS snapshots are zombie spend you can clear in an afternoon. Since February 1, 2024, every public IPv4 address bills $0.005 per hour whether attached or idle, so each unreleased Elastic IP costs about $3.60 a month for nothing. EBS snapshots cost about $0.05 per GB-month in the standard tier, and orphaned snapshots from deleted volumes pile up silently. Find unattached IPs in the EC2 console, release them, list orphaned snapshots, delete or archive them, then automate the cleanup with Amazon Data Lifecycle Manager so the waste does not return.
Last updated: June 2026 · Written by Fredrik Filipsson and reviewed by Morten Andersen · See, Cut, Lock, Run method
Zombie resources are provisioned assets that no longer serve a workload but keep billing, and unattached Elastic IPs and orphaned EBS snapshots are two of the most common on AWS. Clearing them is the cleanest kind of saving because nothing in production depends on them. This guide is part of our complete guide to AWS cost optimization, the cluster pillar it links up to, and it sits in the Cut step of our method, where idle and zombie spend goes before any commitment.
Why do unused Elastic IPs and snapshots cost money?
They cost money because AWS bills both the address and the stored data regardless of whether anything uses them. Since February 1, 2024, AWS charges $0.005 per hour for every public IPv4 address, in use or idle, which works out to about $3.60 per address per month and is documented in the AWS public IPv4 address charge announcement. An Elastic IP you allocated and never attached, or one left behind after an instance was terminated, bills that rate continuously. EBS snapshots cost about $0.05 per GB-month in the standard tier per the Amazon EBS pricing page, and because snapshots are incremental but persist after their source volume is deleted, a backlog of orphaned snapshots accumulates storage charges no one is watching. Verify both rates for your Region before you model the saving, since pricing varies by Region.
How do I find and delete unused Elastic IPs and snapshots?
Find the idle addresses and orphaned snapshots, confirm nothing depends on them, then remove or archive them. Work through these five steps:
- Find unattached Elastic IPs. In the EC2 console, open Elastic IPs and filter for addresses with no associated instance or network interface. Public IP Insights in Amazon VPC IP Address Manager gives an account-wide view of every public IPv4 address and how it is used.
- Release idle Elastic IPs. Before releasing, confirm the address is not referenced by a DNS record, a firewall allowlist, or a partner integration. Once clear, release it to stop the hourly charge immediately.
- Find orphaned EBS snapshots. List snapshots whose source volume no longer exists, or that are older than your retention policy, or that are redundant copies of an AMI you no longer use. Tag-based filtering and AWS Backup reports help separate keepers from cruft.
- Delete or archive snapshots. Delete snapshots you do not need for recovery. For snapshots you must retain but rarely restore, move them to the EBS Snapshots Archive tier at about $0.0125 per GB-month, remembering its 90-day minimum and restore fee.
- Automate ongoing cleanup. Use Amazon Data Lifecycle Manager to create and expire snapshots on a schedule, and add a recurring check, by tag or by Public IP Insights, for newly unattached Elastic IPs so the waste does not creep back.
This is the Cut step of our AWS cost optimization service: clear idle and zombie spend before committing to anything. The same hunt for forgotten line items applies to storage requests in the sibling guide how to reduce Amazon S3 request and API costs.
Snapshots are incremental, so deleting an old snapshot does not corrupt newer ones that reference shared blocks; AWS preserves the data the later snapshots need. Still, confirm a snapshot is not the only copy of a volume you might restore before you delete it.
How much can deleting Elastic IPs and snapshots save?
The saving scales with how long the waste has been ignored, and in neglected accounts it is often material. A single idle Elastic IP is about $3.60 a month, so an organization with a few hundred orphaned addresses across accounts is losing four figures monthly for nothing. Snapshot backlogs are larger still: terabytes of orphaned snapshots at $0.05 per GB-month add up quickly, and we routinely find multi-year snapshot histories no recovery plan references. Because these resources carry no production dependency, the saving is close to pure margin. For a finance-ready view of where this waste hides across an account structure, see our broader treatment in the complete guide to AWS cost optimization.
Want every zombie resource found and cleared?
Our AWS cost audit inventories idle Elastic IPs, orphaned snapshots, unattached volumes, and the rest of the zombie estate across every account, then clears it and locks guardrails so it stays gone. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →How do I stop unused resources from coming back?
Stop the recurrence with automation and guardrails, because a one-time cleanup decays as new orphans appear. Schedule snapshot expiry with Amazon Data Lifecycle Manager so backups age out automatically instead of living forever, and run a recurring report, weekly or monthly, that flags unattached Elastic IPs and snapshots with no source volume. Add an account-level tagging standard so every resource has an owner and a purpose, which makes the next sweep faster and lets you act with confidence. This is the Lock step of our method: budgets, alerts, and guardrails that keep spend from drifting back. The organization-wide version of this control surfaces in how to use AWS Compute Optimizer across an organization.
The AWS Cost Optimization Field Guide includes the zombie-resource sweep checklist we run on every engagement, covering Elastic IPs, snapshots, unattached volumes, idle load balancers, and old AMIs.
Frequently asked questions
How much does an unused Elastic IP cost on AWS?
Since February 1, 2024, every public IPv4 address bills $0.005 per hour whether attached or idle, which is about $3.60 per address per month. An Elastic IP you allocated but never attached, or one left after an instance was terminated, accrues that charge continuously until you release it.
Does deleting an old EBS snapshot break newer snapshots?
No. EBS snapshots are incremental, and AWS preserves any data that later snapshots still reference when you delete an older one. Deleting an old snapshot only removes blocks that no remaining snapshot needs. Still confirm the snapshot is not the sole copy of a volume you might restore.
What is the difference between deleting and archiving a snapshot?
Deleting removes the snapshot and stops all charges for it. Archiving moves it to the EBS Snapshots Archive tier at about $0.0125 per GB-month, lower than the $0.05 standard rate, for snapshots you must keep but rarely restore. The archive tier has a 90-day minimum and a per-GB restore fee, so it suits long-term retention, not active recovery.
How do I find unused Elastic IPs across many accounts?
Use Public IP Insights in Amazon VPC IP Address Manager for an account-wide view, and aggregate across accounts with AWS Organizations. Filter for addresses with no associated instance or network interface, then confirm each is not referenced by DNS or an allowlist before releasing it.
The short version
Unused Elastic IPs and EBS snapshots are zombie spend with no production dependency. Each idle public IPv4 address costs about $3.60 a month, and orphaned snapshots accrue $0.05 per GB-month indefinitely. Find the unattached addresses and orphaned snapshots, release or delete them, archive the snapshots you must keep, then automate expiry with Amazon Data Lifecycle Manager so the waste stays gone. When you want the whole zombie estate found and cleared, that is the work our AWS cost optimization service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: AWS pricing ↗, AWS documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.