How much does an idle t3.xlarge cost on AWS?
A t3.xlarge billed on-demand and left running around the clock costs about $121/mo at its cheapest listed region (us-east-1). Scheduling it off outside business hours cuts that to roughly $36/mo — a $85/mo saving.
Cheapest on-demand
$0.1664/hr
us-east-1
Running 24/7
$121/mo
730-hour month
Business-hours savings
$85/mo
70% off the 24/7 bill
Price by region
| Region | Hourly (on-demand) | Spot (typical) | ≈ Monthly (24/7) |
|---|---|---|---|
| us-east-1 Cheapest | $0.1664/hr | $0.0649/hr | ≈ $121/mo |
| us-east-2 | $0.1664/hr | $0.0582/hr | ≈ $121/mo |
| us-west-2 | $0.1664/hr | $0.0732/hr | ≈ $121/mo |
| ap-south-1 | $0.1792/hr | $0.0788/hr | ≈ $131/mo |
| eu-west-1 | $0.1824/hr | $0.1058/hr | ≈ $133/mo |
| eu-central-1 | $0.1920/hr | $0.0902/hr | ≈ $140/mo |
| ap-southeast-1 | $0.2112/hr | $0.0972/hr | ≈ $154/mo |
| ap-southeast-2 | $0.2112/hr | $0.1014/hr | ≈ $154/mo |
| ap-northeast-1 | $0.2176/hr | $0.0653/hr | ≈ $159/mo |
| sa-east-1 | $0.2688/hr | $0.0672/hr | ≈ $196/mo |
What a schedule saves
| Schedule | Monthly cost | Savings vs 24/7 |
|---|---|---|
| Running 24/7 | $121/mo | baseline |
| Weekdays only (off on weekends) | $87/mo | -$35/mo (29%) |
| Business hours only (10×5) | $36/mo | -$85/mo (70%) |
Assumes a 730-hour month at on-demand list price. Actual savings depend on when the instance is actually used.
About the t3 family
T3 is AWS's third-generation burstable, general-purpose family: a baseline vCPU allocation topped up with CPU credits for short spikes. It fits small web servers, microservices, and low-to-moderate-traffic apps that mostly idle with the occasional burst. That exact shape — quiet most of the day, busy in short windows — is why so many dev and staging environments run on t3 and then sit fully idle overnight and on weekends.
Regional pricing varies: t3.xlarge runs $0.1664/hr in us-east-1, the cheapest region priced here, versus $0.2688/hr in sa-east-1, the priciest — a 38% spread across regions for the identical instance type.
The next size up in the same family, t3.2xlarge (8 vCPU / 32 GB RAM), costs about $243/mo running 24/7 at its cheapest region — roughly 100% more than t3.xlarge's ~$121/mo — for 2x the vCPU.
Common questions
How much does an idle t3.xlarge cost per month?
At the cheapest listed region (us-east-1), a t3.xlarge costs $0.1664/hr, or about $121/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 $85/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $35/mo (29%).
Does stopping a t3 instance reset its CPU credits?
No — that was the old t2 behavior. On t3 the accrued credit balance survives a stop and persists for up to seven days, so a dev box parked overnight restarts with its credits intact; balances only expire after a week stopped. And since t3 launches in unlimited mode by default, even a longer pause just means a small surcharge on the first burst instead of throttling. The stopped hours themselves cost nothing but EBS storage.
Other t3 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.