How much does an idle c5.xlarge cost on AWS?
A c5.xlarge billed on-demand and left running around the clock costs about $124/mo at its cheapest listed region (us-east-1). Scheduling it off outside business hours cuts that to roughly $37/mo — a $87/mo saving.
Cheapest on-demand
$0.1700/hr
us-east-1
Running 24/7
$124/mo
730-hour month
Business-hours savings
$87/mo
70% off the 24/7 bill
Price by region
| Region | Hourly (on-demand) | Spot (typical) | ≈ Monthly (24/7) |
|---|---|---|---|
| us-east-1 Cheapest | $0.1700/hr | $0.0714/hr | ≈ $124/mo |
| us-east-2 | $0.1700/hr | $0.0544/hr | ≈ $124/mo |
| us-west-2 | $0.1700/hr | $0.0714/hr | ≈ $124/mo |
| ap-south-1 | $0.1700/hr | $0.0612/hr | ≈ $124/mo |
| eu-west-1 | $0.1920/hr | $0.1171/hr | ≈ $140/mo |
| eu-central-1 | $0.1940/hr | $0.0718/hr | ≈ $142/mo |
| ap-southeast-1 | $0.1960/hr | $0.0941/hr | ≈ $143/mo |
| ap-northeast-1 | $0.2140/hr | $0.0685/hr | ≈ $156/mo |
| ap-southeast-2 | $0.2220/hr | $0.0955/hr | ≈ $162/mo |
| sa-east-1 | $0.2620/hr | $0.0550/hr | ≈ $191/mo |
What a schedule saves
| Schedule | Monthly cost | Savings vs 24/7 |
|---|---|---|
| Running 24/7 | $124/mo | baseline |
| Weekdays only (off on weekends) | $89/mo | -$35/mo (29%) |
| Business hours only (10×5) | $37/mo | -$87/mo (70%) |
Assumes a 730-hour month at on-demand list price. Actual savings depend on when the instance is actually used.
About the c5 family
C5 is AWS's compute-optimized Intel family — a high vCPU-to-memory ratio built for CPU-bound work like batch processing, video encoding, and CI/CD build fleets. Build agents and load-test rigs are classic C5 tenants: they need real CPU during a run, then sit completely idle between runs. That gap between "when a build kicks off" and "when the box is provisioned" is one of the most common sources of pure waste we see in dev clouds.
Regional pricing varies: c5.xlarge runs $0.1700/hr in us-east-1, the cheapest region priced here, versus $0.2620/hr in sa-east-1, the priciest — a 35% spread across regions for the identical instance type.
The next size up in the same family, c5.2xlarge (8 vCPU / 16 GB RAM), costs about $248/mo running 24/7 at its cheapest region — roughly 100% more than c5.xlarge's ~$124/mo — for 2x the vCPU.
Common questions
How much does an idle c5.xlarge cost per month?
At the cheapest listed region (us-east-1), a c5.xlarge costs $0.1700/hr, or about $124/mo if it runs 24/7. That's the on-demand list price — an idle instance costs exactly the same as a busy one, since cloud billing doesn't know the difference.
How much can I save by scheduling it off outside work hours?
Restricting it to business hours only (10×5) saves about $87/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $35/mo (29%).
Should CI build agents run around the clock?
Almost never — build fleets have the burstiest usage profile in a dev cloud: real load during working-hours pushes, near-zero overnight and on weekends. Autoscaling helps, but a floor of always-on agents quietly becomes the dominant cost. Leasing agents up for the workday and letting them stop afterwards is usually the single biggest win on a c5 fleet.
Other c5 sizes
Stop paying for idle AWS servers
Idlefy runs a free audit of your fleet, then flips dev servers to stopped-by-default: lease one when you need it, and
when the lease ends it shuts itself off — stop, not terminate, persistent disks intact. Timers are set by your team, never
guessed, and Idlefy only manages instances tagged idlefy=enabled — on AWS that boundary is enforced by the IAM policy itself.
Prices are on-demand list price for Linux instances and exclude storage, network, data transfer, and any negotiated or volume discounts. Actual bills vary by usage and account-level pricing. Prices as of 2026-07-20. Spot figures are indicative — AWS values are derived from AWS's published typical savings vs on-demand for the region; GCP values are the listed Spot price. Spot capacity can be reclaimed by the provider. Stopping preserves EBS and persistent-disk volumes; data on local instance-store or local-SSD drives does not survive a stop.