OutYet reporting
AWS adds GPT-5.6 Sol to Bedrock with caching and regional limits
AWS says its Bedrock service now offers GPT-5.6 Sol alongside Terra and Luna, adding an AWS deployment path with prompt caching, IAM controls, and a narrower regional footprint for Sol.
Amazon Web Services says GPT-5.6 Sol, Terra, and Luna are generally available through Amazon Bedrock, putting OpenAI's three-tier GPT-5.6 family behind AWS's managed inference service. For Sol, AWS describes the model as the flagship reasoning tier and says developers can call the family through the Responses API. This is a deployment-surface update rather than a new model-status determination: the announcement documents AWS availability and does not establish release state or trigger alerts.
The timing matters because OpenAI's July 9 product page presented Sol, Terra, and Luna as the GPT-5.6 family, while AWS published its Bedrock announcement on July 13. Both companies describe Sol as the highest-capability tier, Terra as the balanced option, and Luna as the lower-cost option. AWS also says Bedrock pricing matches OpenAI's first-party rates and that usage can count toward existing AWS commitments, which may matter to teams that already buy compute and model access through AWS.
The most concrete platform difference in the AWS announcement is prompt caching. AWS says developers can mark reusable prompt sections with cache breakpoints, after which Bedrock can reuse processed context for later requests that share it; it says cached input receives a 90 percent discount and remains reusable for at least 30 minutes. OpenAI's own page emphasizes Sol's higher reasoning settings and multi-agent capabilities, but neither provider's benchmark claims substitute for an independent evaluation of a particular agent workflow or deployment.
The operational limits are as important as the extra access path. AWS lists Sol in US East (N. Virginia) and US East (Ohio), while Terra and Luna are also listed for US West (Oregon); teams with regional requirements should check that distinction before treating the family as interchangeable. AWS further says classifier-flagged traffic can be retained for up to 30 days for automated abuse detection. That makes the Bedrock route potentially useful for AWS-native applications, but teams should validate region, retention, caching behavior, and total cost against their own prompts before relying on the vendor's performance and efficiency claims.