GPT-5.6 Sol is in Bedrock's global route, not the India-resident profile

AWS's August 27 Bedrock update creates an important deployment distinction for GPT-5.6 users in India. The India geographic cross-Region profiles are available for GPT-5.6 Terra and Luna, while GPT-5.6 Sol is listed with the global cross-Region inference option. That is a concrete availability change for Sol users, but it is not equivalent to a claim that Sol can be served under the same India-only routing boundary as Terra or Luna.

AWS describes the India geographic profiles as routing only between Mumbai, ap-south-1, and Hyderabad, ap-south-2. The two documented profile IDs are in.openai.gpt-5.6-terra and in.openai.gpt-5.6-luna. By contrast, a global profile can route an inference request to supported commercial AWS Regions worldwide, even when the request begins at an India endpoint. The source therefore makes the boundary operational rather than merely geographic branding.

For teams that use the OpenAI SDK, the practical attraction is that Bedrock supports OpenAI-compatible Responses and Chat Completions APIs as well as its native interfaces. AWS also says the India profiles provide a one-million-token context window, accept text and image input, and return text output. But model choice and routing choice remain coupled: an application that needs Sol should not assume the India profile IDs shown for Terra and Luna apply to it.

The data-handling caveat is equally material. AWS says India-profile prompts and outputs may move between the two India Regions and are encrypted in transit; it also states that Bedrock uses zero data retention by default, while content flagged by automated abuse classifiers for certain models, including GPT-5.6, can be retained for offline abuse detection. This is an availability and configuration story, not evidence of a newly released model or a performance comparison among the GPT-5.6 variants. Technical buyers should validate the exact inference profile, routing boundary, retention terms, and access policy required for their workload before treating Sol as suitable for an India-only deployment.