us-west-2: US West (Oregon)
us-west-2 is the code for the US West (Oregon) region, located in Oregon in the north-western United States. It is enabled by default, is one of AWS's largest regions, and is the usual West Coast home for new workloads and the most common disaster-recovery partner for us-east-1.
us-east-1 vs us-west-2
The two are the big general-purpose US regions, on opposite coasts. Choosing between them mostly comes down to where your users are:
| Consideration | us-east-1 | us-west-2 |
|---|---|---|
| Closest users | US East Coast, Europe-bound traffic | US West Coast, traffic to Asia-Pacific |
| Global-service anchors | Yes (CloudFront certs, billing metrics, Lambda@Edge) | No |
| New services | Usually first | Usually first or close behind |
| Role in DR | Often primary | Often the recovery region, being on the other side of the country |
Pricing for common services is generally in line between them, but compare the specific line items. If you run in both, budget for inter-region transfer on whatever you replicate.
Checking us-west-2 health and outages
During a suspected incident, work from the outside in:
- Check the public AWS Health Dashboard filtered to Oregon. Posted events are confirmed, so there may be a delay after symptoms start.
- Check AWS Health in your account for events tied to your resources in us-west-2.
- Look at your own alarms: errors rising in one region only, across unrelated services, point to a regional problem rather than a deployment.
The Health API is reached through us-east-1 even when the event is in Oregon, and requires a Business, Enterprise On-Ramp or Enterprise support plan:
aws health describe-events --region us-east-1 \
--filter regions=us-west-2,eventStatusCodes=open \
--query 'events[].[service,eventTypeCode,statusCode]' --output tableFor a broader routine, see how to check for an AWS outage.
Targeting us-west-2
aws lambda list-functions --region us-west-2
export AWS_REGION=us-west-2
aws configure set region us-west-2The service endpoint pattern is <service>.us-west-2.amazonaws.com (for example sqs.us-west-2.amazonaws.com). Infrastructure-as-code tools usually take the region from the provider block or stack settings rather than the environment, so check both when a deploy lands somewhere unexpected.
Who chooses Oregon, and the alternatives
Oregon suits West Coast user bases, teams that want a large region without the extra blast radius of us-east-1, and anyone needing a geographically distant pair for an East Coast primary. Its neighbours: us-west-1 (California) is closer to the Bay Area but smaller and often pricier; ca-central-1 and ca-west-1 cover Canadian data residency; across the Pacific, ap-northeast-1 (Tokyo) is a frequent second region for transpacific products.
Region-specific details that trip people up
- AMI IDs differ per region. An AMI ID copied from a us-east-1 tutorial fails with
InvalidAMIID.NotFoundhere. Look up the current Amazon Linux image for Oregon from the public SSM parameter instead of hard-coding it. - Zone names are per account.
us-west-2ain one account may be a different physical zone fromus-west-2ain another; use zone IDs such asusw2-az1when aligning subnets between accounts for low-latency peering. - Quotas start at defaults. Raising a limit in us-east-1 does nothing for Oregon; request it again here.
aws ssm get-parameter --region us-west-2 \
--name /aws/service/ami-amazon-linux-latest/al2023-ami-kernel-default-x86_64 \
--query Parameter.Value --output textQuestions
Where is us-west-2?
In Oregon, in the north-western United States. AWS doesn't publish exact data-centre addresses.
How do I check the AWS Health Dashboard for us-west-2?
Open the public AWS Health Dashboard and filter by US West (Oregon), then check your account's AWS Health page for events affecting your own resources.
Is us-west-2 more reliable than us-east-1?
AWS doesn't publish per-region reliability rankings. us-east-1 incidents tend to be more visible because global features depend on it; whichever region you use, plan for regional failure with a second region.
When Oregon has a bad hour, you want to know whether your alarms are AWS or your own deploy. CloudConsole, a phone app for AWS, is built to put alarms, recent changes and resource health on one phone screen.
About the app → · Download on the App Store