CloudConsole

us-east-2: US East (Ohio)

Updated 16 November 2026 · How we write and check guides

Short answer

us-east-2 is the code for the US East (Ohio) region, located in central Ohio. It serves the same eastern US users as us-east-1 with similar latency, is enabled by default, and is a common choice either as a quieter primary region or as the disaster-recovery partner for us-east-1.

World map marking us-east-2 (Ohio); nearest regions us-east-1 500 km, ca-central-1 980 km, ca-west-1 2,700 km
Approximate location of the city AWS names for this region, and the nearest other regions by straight-line distance: a rough guide to latency, not a measurement.

us-east-1 vs us-east-2

Both regions sit in the eastern United States, a few hundred miles apart, so for an end user in New York or Chicago the difference in round-trip time is small. The practical differences are elsewhere:

us-east-1 (N. Virginia)us-east-2 (Ohio)
Global featuresHosts CloudFront certificates, Lambda@Edge, billing metricsNone of these; you still need us-east-1 for them
Service catalogueWidest; new launches usually start hereBroad, but occasionally a newer service or instance type arrives later
LoadBusiest regionGenerally less contended
PricingAmong the lowestFor many services the same list price as us-east-1

Check the AWS Regional Services List before committing, especially for newer services; don't assume parity.

Latency and distance between the two

AWS doesn't publish an official round-trip figure between regions, and it shifts with routing. Measure it for your own workload: start a small instance in each region and ping or run an HTTP benchmark between them, or compare Latency metrics from a load balancer in each. As a rule of thumb, the pair is close enough that synchronous calls from one to the other are tolerable for occasional use but not for chatty database traffic.

Remember that traffic between the two is inter-region data transfer and is billed per GB in each direction it leaves a region. Replicating a busy database or S3 bucket from us-east-1 to us-east-2 has a running cost worth estimating before you switch it on.

Using us-east-2 in the CLI, SDKs and config

# per command
aws s3 ls --region us-east-2

# for the shell
export AWS_REGION=us-east-2

# set it as the default for a profile
aws configure set region us-east-2 --profile dr

Endpoints follow <service>.us-east-2.amazonaws.com, for example lambda.us-east-2.amazonaws.com. Unlike us-east-1, an S3 create-bucket here needs LocationConstraint=us-east-2 in the bucket configuration. Availability Zone names run us-east-2a, us-east-2b and so on; use AZ IDs (use2-az1…) when coordinating placement across accounts, because the letter-to-zone mapping can differ per account.

Using us-east-2 as the DR region for us-east-1

  • Replicate the data, not just the code. S3 Cross-Region Replication, DynamoDB global tables, Aurora Global Database and cross-region snapshot copies all support this pair.
  • Avoid hidden us-east-1 dependencies. If your failover runbook needs to edit IAM or a CloudFront distribution, it depends on control planes in us-east-1. Pre-create roles and DNS records in advance.
  • Request quotas ahead of time. Service quotas are per region; a DR region with default EC2 or Lambda concurrency limits won't absorb production load.
  • Practise. Run a game day; an untested failover usually fails on a missing secret, parameter or AMI.

Questions

Is us-east-2 cheaper than us-east-1?

For many services the list price is the same. Check the specific service's pricing page, as some instance types and services differ, and remember inter-region data transfer costs if you use both.

What is the latency between us-east-1 and us-east-2?

AWS doesn't publish an official figure. The regions are a few hundred miles apart, so it is low, but measure it from instances in each region for your workload.

Where is us-east-2?

In Ohio, in the central-eastern United States. AWS doesn't disclose exact data-centre locations.

When this happens away from your desk

If you've just failed over to Ohio, you want to watch both regions at once, often from wherever you happen to be. CloudConsole, a phone app for AWS, is built to show alarms and resources from several regions side by side.

About the app → · Download on the App Store

Sources