CloudConsole

ca-west-1: Canada West (Calgary)

Updated 16 November 2026 · How we write and check guides

Short answer

ca-west-1 is the code for the Canada West (Calgary) region in Alberta. It is an opt-in region, so an administrator must enable it before resources can be created there. Its main job is to give Canadian workloads a second, geographically separate home inside Canada, alongside ca-central-1 in Montreal.

World map marking ca-west-1 (Calgary); nearest regions us-west-2 710 km, us-west-1 1,600 km, us-east-2 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.

What the Calgary region adds

Before ca-west-1, a Canadian organisation that wanted disaster recovery and in-country data had only one region to work with, so recovery meant spreading across Availability Zones in Montreal. Calgary changes that: you can replicate to a second region thousands of kilometres away without data leaving Canada.

  • Disaster recovery within Canada: pair ca-central-1 with ca-west-1 for backups, replicas and pilot-light environments.
  • Western Canadian users: Alberta and British Columbia are closer to Calgary than to Montreal.
  • Sector requirements: energy, public-sector and health customers in the west sometimes ask for local hosting.

Enabling ca-west-1

New regions are disabled by default. Until you enable it, the region doesn't appear in most console selectors and API calls to it fail with an authentication or opt-in error. To check and enable it with the Account Management API:

aws account get-region-opt-status --region-name ca-west-1

aws account enable-region --region-name ca-west-1

# repeat the first command until the status reads ENABLED

Enabling is not instant; the status passes through ENABLING first. In AWS Organizations the management account (or a delegated administrator) can enable it for member accounts by adding --account-id 123456789012. If your organisation uses a region-deny SCP, add ca-west-1 to the allowed list as well, or enabling will look successful while every call still gets denied.

Targeting ca-west-1 once it's on

export AWS_REGION=ca-west-1
aws ec2 describe-availability-zones \
  --query 'AvailabilityZones[].[ZoneName,ZoneId]' --output table

Endpoints follow <service>.ca-west-1.amazonaws.com. One credential trap: session tokens issued by the global STS endpoint (sts.amazonaws.com) are, by default, only valid in regions that are enabled by default. Tools using that global endpoint can fail in Calgary with an invalid-token error. Use the regional STS endpoint, or change the global endpoint token setting in IAM account settings so tokens are valid in all regions.

Service coverage and alternatives

A newer region typically starts with a core set of services and gains others over time, so a design that works in Montreal may need a substitute here. Check the AWS Regional Services List for each managed service in your recovery plan, not just compute and storage. If something is missing, options are to recover that component into ca-central-1 anyway, or to fall back to a US region for non-resident data. The other Canadian region is ca-central-1; the nearest US region is us-west-2 in Oregon.

Replication between Montreal and Calgary

The two Canadian regions are roughly 3,000 km apart, so the round trip between them is far longer than between Availability Zones. That rules out synchronous replication for most databases: plan for asynchronous copies and decide how much data loss (RPO) and downtime (RTO) the business accepts. Snapshot copies, S3 replication and database read replicas are the usual tools; check each one is supported for the pair before writing it into the runbook. Remember to request service quotas in Calgary that match production, since a recovery region running on default limits will throttle under real load.

Questions

Is ca-west-1 enabled by default?

No. It is an opt-in region; enable it in the account settings or with aws account enable-region before using it.

Where is ca-west-1?

In Calgary, Alberta, in western Canada.

Why do I get an invalid token error in ca-west-1?

Session tokens from the global STS endpoint are only valid in default-enabled regions unless you change the IAM setting. Use a regional STS endpoint or switch the token version for all regions.

When this happens away from your desk

A failover to a second region is the moment you most need to see both at once. CloudConsole, a phone app for AWS, is built to show alarms and resources from several regions on your phone.

About the app → · Download on the App Store

Sources