How much does an idle m6i.xlarge cost on AWS?
An m6i.xlarge billed on-demand and left running around the clock costs about $140/mo at its cheapest listed region (us-east-1). Scheduling it off outside business hours cuts that to roughly $42/mo — a $98/mo saving.
Cheapest on-demand
$0.1920/hr
us-east-1
Running 24/7
$140/mo
730-hour month
Business-hours savings
$98/mo
70% off the 24/7 bill
Price by region
| Region | Hourly (on-demand) | Spot (typical) | ≈ Monthly (24/7) |
|---|---|---|---|
| us-east-1 Cheapest | $0.1920/hr | $0.0787/hr | ≈ $140/mo |
| us-east-2 | $0.1920/hr | $0.0672/hr | ≈ $140/mo |
| us-west-2 | $0.1920/hr | $0.0749/hr | ≈ $140/mo |
| ap-south-1 | $0.2020/hr | $0.0707/hr | ≈ $147/mo |
| eu-west-1 | $0.2140/hr | $0.1070/hr | ≈ $156/mo |
| eu-central-1 | $0.2300/hr | $0.0874/hr | ≈ $168/mo |
| ap-southeast-1 | $0.2400/hr | $0.1176/hr | ≈ $175/mo |
| ap-southeast-2 | $0.2400/hr | $0.0960/hr | ≈ $175/mo |
| ap-northeast-1 | $0.2480/hr | $0.0868/hr | ≈ $181/mo |
| sa-east-1 | $0.3060/hr | $0.0612/hr | ≈ $223/mo |
What a schedule saves
| Schedule | Monthly cost | Savings vs 24/7 |
|---|---|---|
| Running 24/7 | $140/mo | baseline |
| Weekdays only (off on weekends) | $100/mo | -$40/mo (29%) |
| Business hours only (10×5) | $42/mo | -$98/mo (70%) |
Assumes a 730-hour month at on-demand list price. Actual savings depend on when the instance is actually used.
About the m6i family
M6i is the sixth-generation Intel Ice Lake refresh of the general-purpose line, with higher per-core performance and more consistent latency than M5 at a similar price point. Teams upgrade existing M5 fleets to M6i for staging and QA environments to get closer parity with newer production hardware. The upgrade rarely comes with a corresponding schedule review, so the same idle nights-and-weekends pattern just moves to slightly more expensive hardware.
Regional pricing varies: m6i.xlarge runs $0.1920/hr in us-east-1, the cheapest region priced here, versus $0.3060/hr in sa-east-1, the priciest — a 37% spread across regions for the identical instance type.
The next size up in the same family, m6i.2xlarge (8 vCPU / 32 GB RAM), costs about $280/mo running 24/7 at its cheapest region — roughly 100% more than m6i.xlarge's ~$140/mo — for 2x the vCPU.
Common questions
How much does an idle m6i.xlarge cost per month?
At the cheapest listed region (us-east-1), an m6i.xlarge costs $0.1920/hr, or about $140/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 $98/mo (70%) versus running 24/7. A lighter schedule — on around the clock on weekdays, off on weekends — still saves about $40/mo (29%).
Is m6i worth it over m5 for dev and staging?
If you are provisioning fresh, yes — newer Ice Lake cores at a comparable price. Upgrading an existing, quiet m5 environment purely for speed rarely pays back, since dev boxes spend most of their week idle anyway. Match production hardware where parity matters — performance testing — and schedule everything else off.
Other m6i 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.