How much does an idle t3.2xlarge cost on AWS?

A t3.2xlarge billed on-demand and left running around the clock costs about $243/mo at its cheapest listed region (us-east-1). Scheduling it off outside business hours cuts that to roughly $72/mo — a $171/mo saving.

Cheapest on-demand

$0.3328/hr

us-east-1

Running 24/7

$243/mo

730-hour month

Business-hours savings

$171/mo

70% off the 24/7 bill

vCPU 8 Memory 32 GB Family t3 Provider AWS

Price by region

Region Hourly (on-demand) Spot (typical) ≈ Monthly (24/7)
us-east-1 Cheapest $0.3328/hr $0.1231/hr ≈ $243/mo
us-east-2 $0.3328/hr $0.0998/hr ≈ $243/mo
us-west-2 $0.3328/hr $0.1132/hr ≈ $243/mo
ap-south-1 $0.3584/hr $0.1362/hr ≈ $262/mo
eu-west-1 $0.3648/hr $0.1605/hr ≈ $266/mo
eu-central-1 $0.3840/hr $0.1382/hr ≈ $280/mo
ap-southeast-1 $0.4224/hr $0.1478/hr ≈ $308/mo
ap-southeast-2 $0.4224/hr $0.1394/hr ≈ $308/mo
ap-northeast-1 $0.4352/hr $0.1175/hr ≈ $318/mo
sa-east-1 $0.5376/hr $0.1129/hr ≈ $392/mo

What a schedule saves

Schedule Monthly cost Savings vs 24/7
Running 24/7 $243/mo baseline
Weekdays only (off on weekends) $174/mo -$69/mo (29%)
Business hours only (10×5) $72/mo -$171/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.2xlarge runs $0.3328/hr in us-east-1, the cheapest region priced here, versus $0.5376/hr in sa-east-1, the priciest — a 38% spread across regions for the identical instance type.

Common questions

How much does an idle t3.2xlarge cost per month?

At the cheapest listed region (us-east-1), a t3.2xlarge costs $0.3328/hr, or about $243/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 $171/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $69/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.

Run a free idle audit

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.