AWS EC2 cost: pricing levers and a cost review
Updated: 6 November 2026AWS EC2 cost starts with the instance configuration and its running time. A useful review also accounts for the resources around it, then tests whether a change preserves the service your users need.
Request a quote
Use the AWS cost optimization FAQ on free recommendations and paid features before choosing a reporting or review scope. Ask the quote to separate analysis from application testing and approved resource changes.
Include observability in the workload boundary. The CloudWatch logs and metrics cost review connects the monitoring bill with application owners and the evidence they need during incidents.
When the application also uses a managed database, build a separate estimate with the Amazon RDS pricing checklist rather than applying an EC2 instance rate to RDS.
AWS EC2 cost: read the complete workload bill
The official EC2 On-Demand pricing page distinguishes instance configurations, operating systems and Regions. Record those fields beside the hours actually billed. A price for one Linux instance is not a quote for an application with Windows licences, persistent storage and outbound traffic. Keep the contractual rate you pay alongside the public price, and identify credits separately.
| Cost line | Evidence to collect | Review question |
|---|---|---|
| Compute | Instance type, operating system, Region, running time | Does the application need this size throughout the period? |
| Persistent disks | Volume type, size and performance settings | Are capacity and performance both required? |
| Network | Traffic path and billed transfer | Which application creates the flow? |
| Commitments | Coverage and effective cost | Would this usage remain after rightsizing? |
Use the AWS cost optimization review to reconcile the workload to the payer account. Read the EBS volume cost guide before treating storage as part of the instance hourly price. This prevents a compute-only comparison from overstating the saving available on the whole service.
Identify idle time before changing instance size
The EC2 lifecycle documentation explains that a stopped EBS-backed instance stops incurring instance usage charges, while associated EBS storage can still be billed. Stopping and terminating are different actions. Neither automatically cancels a Reserved Instance or Savings Plan obligation; distinguish removed On-Demand usage from a continuing commitment. Have the owner confirm the required state, restart procedure and retained data before scheduling a shutdown.
- List the owner and production role of every candidate instance.
- Compare running schedules with the hours the workload must be available.
- Check memory, latency and batch peaks as well as CPU usage.
- Record dependencies that prevent a shutdown or require a coordinated restart.
A low average is evidence to investigate, not approval to resize. Select a period that includes known demand peaks and record what the metrics do not cover. An instance supporting a quiet disaster recovery environment can have low utilization for an intentional reason. Ask engineering to explain that requirement before classifying the capacity as waste.
Compare rates against the remaining demand
For AWS EC2 cost optimization, compare configurations that can run the same workload. Include licence conditions and application compatibility in the decision sheet. The Reserved Instances and Savings Plans comparison belongs after the usage review: evaluate the steady demand that survives the proposed changes rather than the current invoice total.
A controlled EC2 change plan
- Capture the current configuration and its measured service behavior.
- Test the proposed size or operating schedule against the application acceptance criteria.
- Agree the change owner, maintenance procedure and rollback trigger.
- Measure the bill after the change, including disks and traffic, against the approved baseline.
The instance cost AWS charges is only one input to the business decision. A proposal should identify the accounts reviewed, the evidence window and the work included in implementation. It should say who approves production changes and how the team will distinguish expected savings from savings already observed. Review AWS data transfer costs if a move between locations changes the traffic path. Keep that effect in the same register as the compute change.

Questions before a cost review
Does stopping EC2 remove every cost?
No. Instance usage charging stops for a stopped EBS-backed instance, but EBS storage and other retained resources can still incur charges. Review the complete workload rather than the compute line alone.
Related workload decisions
Continue the review with aws s3 cost, aws cost rds. Each guide addresses a separate decision within the same cloud cost boundary.
Keep attached storage in the EBS pricing reconciliation when assessing a compute change. Review an application's managed database through the RDS cost optimization checklist so its recovery requirements and residual charges stay in the same workload boundary.