Canadian cloud regions compared
All three major providers run two Canadian regions each. That means a Canadian company can keep production and its disaster recovery copy inside the country on any of them.
AWS runs Canada Central (ca-central-1, Montreal area) and Canada West (ca-west-1, Calgary). Azure runs Canada Central (Toronto) and Canada East (Quebec City). Google Cloud runs Montreal (northamerica-northeast1) and Toronto (northamerica-northeast2). Each provider's pair lets you run production and a disaster recovery copy without data leaving Canada.
| Provider | Region | Code | Location | Availability zones |
|---|---|---|---|---|
| AWS | Canada (Central) | ca-central-1 | Montreal area | Yes |
| AWS | Canada West (Calgary) | ca-west-1 | Calgary | Yes |
| Azure | Canada Central | canadacentral | Toronto | Yes |
| Azure | Canada East | canadaeast | Quebec City | No |
| Google Cloud | Montreal | northamerica-northeast1 | Montreal | Yes |
| Google Cloud | Toronto | northamerica-northeast2 | Toronto | Yes |
Which Canadian region should be primary?
Pick the region with the widest service catalogue on your provider as primary: ca-central-1 on AWS, Canada Central on Azure, and either Montreal or Toronto on Google Cloud. The newer or smaller region in each pair lags on some services, so check that every service in your architecture is available there before you design disaster recovery around it.
Disaster recovery inside Canada
For a customer that requires Canadian storage, backups and replicas have to stay in Canada too. The standard pattern is production in the primary region and backups or a warm standby in the second.
- AWS. AWS Backup cross-region copy from ca-central-1 to ca-west-1, S3 replication, RDS cross-region read replicas.
- Azure. Canada Central and Canada East are a paired region, so geo-redundant storage replicates between them automatically. Canada East has no availability zones, so it suits recovery rather than zone-redundant production.
- Google Cloud. Dual-region storage and Cloud SQL cross-region replicas between Montreal and Toronto.
Backup and disaster recovery covers the evidence an auditor asks for.
Services that are not regional
Some services process data outside the region you choose. Identity services (AWS IAM, Microsoft Entra ID, Google Cloud Identity), content delivery networks, DNS and support tooling are global or tenant-geography based. That is normally acceptable: they process account metadata, not customer records. It belongs in your data flow diagram and in any privacy impact assessment, and it is why "all our data is in Canada" should be written as "customer data is stored and processed in Canadian regions".
Enforcing the region choice
A region choice that relies on engineers remembering is a promise. One that is enforced is a control with evidence.
| Provider | Mechanism |
|---|---|
| AWS | Service control policy denying actions outside approved regions, with exceptions for global services; Control Tower region deny |
| Azure | Azure Policy "Allowed locations" assigned at the management group |
| Google Cloud | Organization policy constraint gcp.resourceLocations |
Does AWS have a region in Toronto?
No. AWS's Canadian regions are Canada (Central) in the Montreal area and Canada West in Calgary. Azure's Canada Central and Google Cloud's northamerica-northeast2 are the Toronto regions.
Is using a Canadian region enough for data residency?
It covers where data is stored. It does not cover who can access it from outside Canada, such as support staff or subprocessors, or legal access under foreign law. Contracts that require Canadian residency usually ask about both. Data residency in Canada covers this.
Are all services available in Canadian regions?
Most core compute, storage, database and security services are. Newer services, some AI services and specialised hardware sometimes launch in US regions first. Check the provider's regional services list before committing an architecture that needs a specific service.
Planning a move into Canadian regions?
Firms in the network plan and run region migrations with the compliance evidence intact.
Get matched