Compute and database costs are fairly obvious, but networking charges seem easier to overlook, especially after workloads are stopped. What should I check when trying to understand or reduce an AWS bill?
What networking costs are easy to miss in AWS?
Answers
Start with the billing breakdown rather than assuming stopped instances mean the account is idle. Check for resources that remain provisioned, such as NAT gateways, interface VPC endpoints, load balancers, transit gateways and public IPv4 addresses.
Some have hourly charges, some also charge for traffic, and pricing varies by service and region. Look at the usage types and quantities on the bill before deleting anything. A resource can still be serving something even if the main application is paused.
Reply to this answer
Private networking has a price, and the fixed charges can feel pretty steep on a small setup. Interface endpoints, for example, can add up before much traffic ever flows through them.
Compare the cost and security tradeoffs for your actual workload. NAT gateways cost money too, so swapping endpoints for NAT is not automatically cheaper. The right choice depends on traffic, availability needs and which services you need to reach.
Reply to this answer
This sounds partly like a lifecycle problem. If environments are created for occasional work, plan how to remove the supporting network resources when the environment is no longer needed, not just how to stop the servers.
Infrastructure as code can make rebuilding an environment less painful and help keep track of what belongs to it. Still review shared resources and dependencies before tearing anything down.
Reply to this answer
Cost is only one side of the design. Private instances accessed through Systems Manager can avoid opening inbound management ports, with identity controls and logging available. That may be worth paying for, but the supporting services and connectivity should be part of the estimate.
Reply to this answer
Don't stop at networking while you're checking the bill. Old snapshots and other retained storage can quietly keep charging too. Lots of individually modest items can make the total surprisingly large.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_g58!windowspool.9:
Also check for unused Elastic IP addresses. Stopping an instance does not necessarily release an address allocated to the account.