How much does an idle t4g.micro cost on AWS?
A t4g.micro billed on-demand and left running around the clock costs about $4/mo at its cheapest listed region (ap-south-1). Scheduling it off outside business hours cuts that to roughly $1/mo — a $3/mo saving.
Cheapest on-demand
$0.0056/hr
ap-south-1
Running 24/7
$4/mo
730-hour month
Business-hours savings
$3/mo
70% off the 24/7 bill
Price by region
| Region | Hourly (on-demand) | Spot (typical) | ≈ Monthly (24/7) |
|---|---|---|---|
| ap-south-1 Cheapest | $0.0056/hr | $0.0021/hr | ≈ $4/mo |
| us-east-1 | $0.0084/hr | $0.0031/hr | ≈ $6/mo |
| us-east-2 | $0.0084/hr | $0.0033/hr | ≈ $6/mo |
| us-west-2 | $0.0084/hr | $0.0027/hr | ≈ $6/mo |
| eu-west-1 | $0.0092/hr | $0.0044/hr | ≈ $7/mo |
| eu-central-1 | $0.0096/hr | $0.0031/hr | ≈ $7/mo |
| ap-southeast-1 | $0.0106/hr | $0.0045/hr | ≈ $8/mo |
| ap-southeast-2 | $0.0106/hr | $0.0040/hr | ≈ $8/mo |
| ap-northeast-1 | $0.0108/hr | $0.0039/hr | ≈ $8/mo |
| sa-east-1 | $0.0134/hr | $0.0032/hr | ≈ $10/mo |
What a schedule saves
| Schedule | Monthly cost | Savings vs 24/7 |
|---|---|---|
| Running 24/7 | $4/mo | baseline |
| Weekdays only (off on weekends) | $3/mo | -$1/mo (29%) |
| Business hours only (10×5) | $1/mo | -$3/mo (70%) |
Assumes a 730-hour month at on-demand list price. Actual savings depend on when the instance is actually used.
About the t4g family
T4g runs on AWS Graviton2 (Arm64) and offers the best price-performance in the burstable family for software that supports Arm — Node, Go, most modern Java and Python stacks. It's a natural fit for dev/test replicas, CI build agents, and small services where the team has already validated Arm compatibility. Like its x86 siblings, it's cheap enough that nobody bothers scheduling it off, so idle time quietly compounds.
Regional pricing varies: t4g.micro runs $0.0056/hr in ap-south-1, the cheapest region priced here, versus $0.0134/hr in sa-east-1, the priciest — a 58% spread across regions for the identical instance type.
The next size up in the same family, t4g.small (2 vCPU / 2 GB RAM), costs about $8/mo running 24/7 at its cheapest region — roughly 100% more than t4g.micro's ~$4/mo — for the same vCPU count but 2x the RAM.
Common questions
How much does an idle t4g.micro cost per month?
At the cheapest listed region (ap-south-1), a t4g.micro costs $0.0056/hr, or about $4/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 $3/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $1/mo (29%).
Will my software run on t4g (Arm/Graviton)?
Most modern stacks do — Node, Go, Python, and current JVMs all ship Arm64 builds, and popular Docker images publish multi-arch manifests. The usual blockers are older native dependencies and closed-source agents. Teams typically validate once on a single t4g dev box before moving a wider fleet across.
Other t4g 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.