Does AWS charge for stopped instances? 3 hidden charges
In short: Unattached EBS volumes bill every month until you delete them. Snapshot anything you are unsure about, then delete. AWS charges for every public IPv4 address, about $3.60 a month each. Release the ones nothing uses. A stopped EC2 instance still pays for its disks. Schedule dev servers to stop, and terminate what you no longer need. Does AWS charge for stopped instances? Not for the…
When an EC2 instance is stopped, AWS does not charge for the instance's compute resources, but it does charge for certain hidden costs. These include unattached EBS volumes, public IPv4 addresses, and any leftover resources from stopped instances.
Unattached EBS volumes continue to be billed monthly until they are deleted. Test servers, for example, may have a 30 GiB gp3 root volume costing $2.40 a month. Similarly, data volumes and Elastic IP addresses attached to stopped instances also incur ongoing charges.
Public IPv4 addresses have a new fee as of 2024, at $3.60 per month per IP, even if not currently in use. Users can identify and release unused or unused Elastic IPs via AWS CLI commands.
Stopped instances still incur storage costs for any attached EBS volumes. Unused snapshots and AMIs can also lead to unnecessary charges. Regularly monitoring and cleaning up these idle resources, using AWS tools like Cost Explorer, Amazon Data Lifecycle Manager, and tagging resources, can help reduce these hidden costs significantly.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.