The 30-Second Brief
- Source report AWS says OpenAI GPT-5.6, GPT-6 and GPT-6.1 models can now be invoked from its Canada Central and Canada West Bedrock regions through cross-Region inference profiles. [1]
- Analysis A Canadian API endpoint is not the same claim as Canadian-only processing. The selected inference profile, its destinations and retention terms belong in the architecture decision.
What Became Available
Source report AWS lists OpenAI GPT-5.6 Sol, Terra and Luna; GPT-6 Astra, Sol and Luna; and GPT-6.1 Sol. The models are exposed through OpenAI-compatible Responses and Chat Completions paths as well as the Bedrock Converse API. AWS says profile availability differs by model and source region; for example, the GPT-5.6 global profile is available from Canada Central but not Canada West at publication time. [1]
The Profile Defines the Processing Boundary
Source report AWS describes US geographic profiles as routing within Canada and the United States, while global profiles can route to supported commercial AWS regions. The general documentation warns that destination sets may differ by source region and that a geographic prefix alone should not be treated as proof of the active destinations. [1] [2]
Analysis Store the exact profile ID and a dated list of destination model ARNs with the system’s data-flow record. Recheck them before a production change, because availability and global destinations can evolve. If policy requires Canada-only processing, neither the US geographic nor global description establishes that requirement.
Permissions and Observability Need Separate Checks
Source report AWS says IAM and service control policies must allow the selected profile and its destinations. It records invocation metrics in the source region and exposes the serving destination in CloudTrail’s inferenceRegion field. Model invocation logging, which can capture full requests and responses, is off by default. [1]
Analysis Test least-privilege invocation with the production role, then confirm that a reviewer can reconstruct which profile and destination handled a request. Decide deliberately whether payload logging is permitted; enabling it for troubleshooting can create a more sensitive data store than the application itself.
Read Retention Terms as Part of the Data Flow
Source report AWS states that content flagged by automated abuse classifiers may be retained for up to 30 days in the destination region. Its general inference-profile documentation also warns that prompts and outputs may be stored in opt-in regions for abuse detection. [1] [2]
Analysis Map those statements to the workload’s data classification, contractual requirements and deletion expectations before migration. This brief is not legal advice, and it does not establish that a workload meets a Canadian residency rule.
Evidence & Uncertainty
Uncertainty AWS is the source for availability, routing and retention behavior. BriefSpire has not invoked these profiles, verified a specific account’s active destinations, measured performance or assessed a regulator’s interpretation. Model and destination availability can change; the live control-plane response is stronger deployment evidence than a launch post.
Story Timeline
October 20, 2026: AWS publishes the Canadian-region access guidance. October 21: BriefSpire checks the source, current documentation and operational boundaries. [1]
Action Center
Selections remain in this browser.
Evidence Explorer
Does a ca-central-1 endpoint guarantee processing stays in Canada?
No. AWS says cross-Region profiles can route to destination regions defined by the selected profile.
Can a team rely on the profile prefix forever?
No. AWS recommends querying the control plane; global destination sets and available profiles can change.
Sources & Transparency
Last source check: . Both sources are AWS publications. Availability and routing claims are vendor-described; governance implications are BriefSpire’s analysis, not legal or compliance advice.