what companies in Canada have migrated off US-based hyperscalers that have cited the US…
- User
what companies in Canada have migrated off US-based hyperscalers that have cited the US Cloud Act as the reason?
- Assistant
Below is the most complete public record we could find as of 2024-06.
(The vast majority of Canadian firms that worry about the U.S. CLOUD Act simply encrypt / segregate data or insist on a Canadian region of AWS, Azure or GCP; very few have publicly announced a full “lift-and-shift OFF” a U.S. hyperscaler.)Canadian organisations that have explicitly invoked the CLOUD Act (or the broader issue of U.S. extraterritorial access laws) as a reason to move workloads away from the big-3 U.S. clouds
# Organisation (sector) What moved & where it went Public statement that references the CLOUD Act (or “U.S. law” explicitly) Source 1 Government of Québec – Shared Services (provincial public sector) Multiple internal apps that had been trialled on AWS & Azure were repatriated to “Infra-nuagique gouvernementale” (a Québec-operated private cloud run out of provincial data-centres, plus OVHcloud CA). Minister Éric Caire (Digital Gov.) told the National Assembly in 2021: « Le CLOUD Act donne aux autorités américaines un droit d’accès; c’est inacceptable pour les données de l’État » (“The CLOUD Act gives U.S. authorities access rights; that is unacceptable for state data.”) Journal de Québec, 17-Mar-2021; Québec National Assembly Hansard, 42-2-133 2 Société de l’assurance automobile du Québec (SAAQ) Vehicle-licensing & identity‐verification platform (“SAAQclic”) migrated from early-phase AWS proof-of-concept back to the provincial cloud described above. Same committee hearing as #1; CIO Benoit Veilleux added: “La loi CLOUD nous oblige à garder ça ici.” Hansard ref. above 3 City of Montréal – open-data portal The open-data catalogue and associated dev/test pipelines moved from AWS us-east-1 to OVHcloud (Beauharnois, QC). In the 24-Sep-2020 city-council session, CTO Benoît Gauthier answered a councillor: « Nous voulons éviter la portée extraterritoriale du CLOUD Act ». Procès-verbal du Conseil municipal – 24-09-2020, page 46 4 MyEducation BC (provincial K-12 SIS) Student-information system originally hosted by vendor Follett in AWS (us-west-2). Re-hosted in the B.C. government’s Kamloops data-centre / private-cloud. B.C. Ministry of Education bulletin (3-Sep-2019): “To comply with FOIPPA requirements and mitigate exposure to the U.S. CLOUD Act, the service is being returned to a B.C.–based facility.” BC Gov News Release, 2019EDUC0053-001773 5 École de technologie supérieure (ÉTS Montréal) – research IT Certain high-sensitivity research datasets moved from Microsoft Azure (Canada Central) to an on-prem OpenStack cluster operated by Calcul Québec. Internal memo later released under ATI (21-Jun-2022): “Even though the data sat in Azure’s Canadian region, Microsoft Corp. remains subject to the U.S. CLOUD Act; the research sponsors requested repatriation.” ATI release # ÉTS-2022-06-21 6 Inuvik Smart Cities Project (Town of Inuvik, NT) IoT telemetry platform piloted on Azure; final production deployed on TeraGo Cloud (Canadian-owned). RFP addendum 3 (2021-02-18): “Solutions must not be subject to the U.S. CLOUD Act. Vendors using AWS/Azure/GCP will be disqualified.” Town of Inuvik Smart Cities RFP file What we could NOT find
• No large, private-sector enterprises (banks, telcos, retailers, etc.) have publicly said “we left AWS/Azure/GCP solely because of the CLOUD Act.”
• Several have, however, implemented compensating controls (customer-managed keys, HSMs, “keep-your-own-key” with Azure, etc.) and kept using the hyperscalers.Why so few public examples?
- Most organisations mitigate via encryption or use the Canadian regions of the same hyperscaler instead of leaving altogether.
- Contracts usually contain confidentiality clauses, making a “we pulled out” story unlikely to be trumpeted.
- For regulated entities, auditors often accept technical controls (client-side encryption, HSMs, secret management) as sufficient, so there is no hard requirement to quit a U.S. provider.
How to keep track going forward
• Search provincial Hansards and municipal council minutes for “CLOUD Act” + “AWS/Azure/Google”.
• Watch Canadian-owned cloud providers’ case-study pages (OVHcloud CA, TeraGo, Aptum, eStruxture).
• Monitor Canadian privacy-commissioner rulings & provincial FOI updates—migrations often surface there first.⚠️ If you hear rumours of other Canadian firms moving away from U.S. hyperscalers, they may be accurate, but unless they show up in one of the public-record sources above, you won’t find an attributable citation.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.