GPT-5.6 Sol gains a Bedrock route from Australia, with a residency trade-off

AWS says applications using its Sydney or Melbourne Regions can invoke the global Amazon Bedrock inference profiles for OpenAI GPT-5.6 Sol, Terra, and Luna. The application sends its request to an Australian Bedrock Runtime endpoint, while Bedrock selects a supported commercial AWS Region to process it. For GPT-5.6 Sol users, the change is therefore an access and routing option rather than a claim about a new model capability. AWS also documents the profile identifier pattern, including `global.openai.gpt-5.6-sol`, which matters because callers use that profile in place of an ordinary single-Region model target.

The Australian guide follows AWS's broader August announcement that cross-Region inference profiles were available for the GPT-5.6 family across more than 25 AWS Regions. In the broader design, a global profile can draw on capacity in supported commercial Regions, whereas a geographic profile limits processing to its defined geography. That is a meaningful distinction from merely exposing a model at a nearby endpoint: the source Region remains where the application calls Bedrock, but global routing can place inference elsewhere. AWS presents the arrangement primarily as a way to use a larger capacity pool without having to operate destination-Region routing in the application.

For teams with data-location obligations, the important limitation is explicit. A global profile offers the widest routing pool, but AWS says it may select any supported commercial AWS Region; a geographic profile is the option intended to keep processing inside its stated geography. Using Sydney or Melbourne as the API entry point should not therefore be treated as proof that every inference stays in Australia. AWS also cautions that profile membership and model availability can change, so a production rollout should inspect the active profile and policy controls rather than hard-code an assumption from a launch article.

AWS describes all three GPT-5.6 variants as accepting text and image input, returning text, and supporting context windows of up to one million tokens through the Responses, Chat Completions, and Converse APIs. Its Australian walkthrough additionally covers prompt caching, OpenID Connect-based Codex authentication, and CloudWatch monitoring. The practical value for an existing AWS estate is a path to use Sol with its IAM, logging, and observability model; the practical cost is that deployment review must include routing, service-control-policy permissions, and data-processing geography. The documentation verifies the access path, but not the appropriate compliance posture for any particular workload.