Bedrock adds an Australian routing path for GPT-5.6 Sol

AWS's September 2 guide documents a deployment path for GPT-5.6 Sol from Australia. Applications can invoke global Amazon Bedrock inference profiles from the Sydney or Melbourne source Regions, while Bedrock routes processing to a supported commercial AWS Region. The change is operationally meaningful because the application keeps a regional Bedrock Runtime endpoint instead of selecting a destination Region itself.

The AWS guide describes three GPT-5.6 profile identifiers, one each for Sol, Terra, and Luna, and says customers should first enable Sydney or Melbourne, allow the profiles in any service control policy, and grant the relevant IAM permissions. It also shows Responses API, Chat Completions API, and Bedrock Converse API paths. That makes this more than a console listing: it is an integration pattern with explicit account and policy prerequisites.

OpenAI's own model documentation identifies Sol as the flagship GPT-5.6 tier and lists a 1.05 million-token context window, 128,000 maximum output tokens, text and image input, and no audio or video support. Those are model-level characteristics, not an AWS performance guarantee. AWS's material is therefore best read as a routing and control-plane option for the same class of workload, rather than evidence that a Bedrock profile changes Sol's capability envelope.

There are limits to treat as deployment requirements. AWS says profile membership and model availability can change and directs customers to verify cross-Region support before deployment. Its example also makes the source Region, IAM policy, and service control policy part of the setup. Teams with residency, latency, or egress constraints should validate the actual destination-region rules and their account's permitted profile before moving a production workload.