> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Move EC2 Instances to a Cheaper Region in the Same Geography

> Run steady EC2 workloads in the cheapest AWS region of the same geography, where the same instance costs less.

The same EC2 instance type is priced differently in different regions. nOps finds on-demand instances in US and European regions where the same instance type and operating system costs at least 10% less in a major region of the same geography, and estimates the compute saving from running the workload there.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Compute |
| **Service** | Amazon EC2 |
| **Action** | Modify |
| **Effort** | High |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Workloads are often placed in a region for historical reasons. When latency and data residency allow, moving steady compute to a cheaper region lowers its price with no change in size.

## How nOps finds it

nOps reads the last 7 complete days of on-demand EC2 billing for instances in US and European regions that ran on all 7 days. The target region is the cheapest of us-east-1, us-east-2 and us-west-2 for US instances, or of eu-west-1, eu-central-1 and eu-north-1 for European ones, for the same instance type and operating system. An instance is flagged when the target lists at least 10% cheaper. The saving is the on-demand cost, scaled to a month, times that list-price difference. Auto Scaling, EKS and Karpenter instances, instances mostly covered by Reserved Instances or Savings Plans, and savings under \$50 a month are left out.

## Before you start

Confirm latency to users and dependencies, data residency rules, and that every service the workload uses is available in the target region.

## How to implement

1. Check latency, data residency and compliance requirements, and the services the workload depends on.
2. Estimate the cost of moving data and of any new cross-region traffic.
3. Copy the AMI to the target region (`aws ec2 copy-image`) and copy any EBS snapshots and data.
4. Recreate networking (VPC, subnets, security groups) and launch the instance in the target region.
5. Move traffic with DNS, test, then terminate the old instance.
6. Update Terraform or CloudFormation to deploy to the new region.

## Risks and considerations

* This is a migration with real effort, not a setting change. The estimate covers compute only.
* Cross-region data transfer and moving storage can reduce or cancel the saving.
* Reserved Instances and Savings Plans tied to the current region do not move.
* To roll back, keep the old instance or its AMI until the move is proven.

## FAQs

> [accordion] Does nOps include data transfer in the saving?
>
> No. The saving is the instance price difference only. Add your own estimate for data transfer and migration effort.

## Related

* [Rightsize EC2 Instance](https://help.nops.io/inform/supported-recommendations/rightsize-ec2-instance)
* [Migrate EC2 Instance to Graviton](https://help.nops.io/inform/supported-recommendations/migrate-ec2-instance-to-graviton)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.