Get started with OpenAI GPT-5.6 Sol, Terra, and Luna on Amazon Bedrock

wpnews.pro

Artificial Intelligence This post is co-written with Chris Dickens from OpenAI.

Developers building agentic coding, long-horizon reasoning, and high-volume inference workloads want frontier models they can call through familiar APIs, without operating separate model infrastructure. OpenAI GPT-5.6 Sol, Terra, and Luna are now generally available on Amazon Bedrock. The three models cover workloads from autonomous coding agents and long-horizon reasoning to high-volume, latency-sensitive inference, and they run with the security, Regional processing, and cost controls of AWS.

You access all three models through the OpenAI Responses API on the bedrock-mantle endpoint. Sol is the flagship reasoning model, Terra balances performance and cost for everyday production work, and Luna is optimized for fast, low-cost inference, so you can right-size capability and cost for each workload. Pricing matches OpenAI first-party rates, and usage counts toward your existing AWS commitments.

In this post, we show you how to select a model, run your first inference through the Responses API, reduce cost with prompt caching and measure cached-token usage, connect the OpenAI Codex coding agent, and plan for quotas and scaling. Your prompts and completions are not used to train any models, and are not shared with the model provider.

The GPT-5.6 family on Amazon Bedrock #

GPT-5.6 introduces a naming system from OpenAI where the number identifies the generation and the names Sol, Terra, and Luna identify durable capability tiers that can advance on their own cadence. The following table summarizes the key specifications for each model on Amazon Bedrock.

openai.gpt-5.6-luna | High-volume, latency-sensitive workloads such as classification, summarization, and routing | US East (N. Virginia), US East (Ohio), US West (Oregon) | All three models support text and image input, text output, a 272K-token context window, and the Responses API. They also support none

, low

, medium

, high

, xhigh

, and max

reasoning effort, so you can switch models without changing your API integration.

Accessing GPT-5.6 through the bedrock-mantle endpoint #

You access GPT-5.6 models through the OpenAI Responses API on the bedrock-mantle

endpoint. The base URL is https://bedrock-mantle.{region}.api.aws , and the Responses API is served at /openai/v1/responses

. Replace {region} with a supported AWS Region, such as us-east-1

. This openai/v1

path is specific to the OpenAI models. The endpoint works with the OpenAI Python and TypeScript SDKs. To run an existing OpenAI SDK application on Amazon Bedrock, replace the OpenAI base URL with the bedrock-mantle endpoint, use the corresponding Amazon Bedrock model ID, and authenticate with an Amazon Bedrock API key or AWS credentials.

Security and data handling

Every model call runs under your AWS Identity and Access Management (IAM) policies, inside your virtual private cloud (VPC), and is logged in AWS CloudTrail. In-Region inference keeps requests within the AWS Region you specify, which helps teams meet data-residency requirements.

GPT-5.6 Sol, Terra, and Luna are third-party models from OpenAI, made available on Amazon Bedrock and subject to the OpenAI terms. For these OpenAI models, classifier-flagged traffic is retained for up to 30 days for automated offline abuse detection. Retained inputs and outputs are stored and processed by AWS and are not shared with the model provider unless you opt in. You control retention configuration through data retention mode.

Get started with GPT-5.6 on Amazon Bedrock #

Complete the following steps to start using GPT-5.6 on Amazon Bedrock.

Prerequisites

To use GPT-5.6 models, you need an AWS account with permissions to run inference on the bedrock-mantle endpoint. One way to grant these is to attach the AWS managed policy AmazonBedrockMantleInferenceAccess to your IAM principal. It grants the read and inference-creation access the examples in this post need, including bedrock-mantle:CreateInference and bedrock-mantle:CallWithBearerToken.

Install the OpenAI Python SDK, version 2.45.0 or later:

You authenticate with an API key. There are two options for authenticating the OpenAI SDK.

Auto-refreshing short-term key: The OpenAI SDK’s native BedrockOpenAI client takes a token provider that generates a short-term key from your AWS credentials and refreshes it before each request. The examples in this post use this client.Short-term key from an environment variable: Set the key on AWS_BEARER_TOKEN_BEDROCK and pass it to the client. Because this key isn’t refreshed, it expires after at most 12 hours. For production, use the auto-refreshing option or store the key in AWS Secrets Manager.

Run your first inference with the Responses API

Using the BedrockOpenAI client from the previous step, call GPT-5.6 Terra through the Responses API. The Responses API uses a single input field and returns the generated text in output_text

.

To move an existing OpenAI SDK application to GPT-5.6 on Amazon Bedrock, update the base URL and the model ID.

Control reasoning effort

GPT-5.6 models can spend additional reasoning tokens on complex, multi-step tasks before answering, which improves results but increases latency and cost. Set the level with the reasoning parameter. Sol, Terra, and Luna support none

, low

, medium

, high

, xhigh

, and max

. Match the level to the task.

Call tools

GPT-5.6 supports tool calling, which lets the model request tools you define and use their results to complete a request. The following example demonstrates client-side tool calling, where your application runs the tool and returns the result to the model. It defines a get_weather tool and completes one round-trip. The model requests the tool, your application runs it and returns the result, and the model produces the final answer.

Because GPT-5.6 models reason before responding, pass the model’s output items (which can include reasoning) back in the next request, as the preceding example does when it appends response.output

to the input

list.

For production deployments, use Amazon Bedrock Guardrails to implement safeguards customized to your use cases and responsible AI policies.

Try GPT-5.6 on the console

GPT-5.6 models run on the next-generation inference engine, which has a new Amazon Bedrock console experience optimized for the bedrock-mantle endpoint and its OpenAI-compatible and Anthropic-compatible APIs.

This experience is project-based. You create a project, assign models, configure API keys, and evaluate models side by side before writing application code. Complete the following steps to try GPT-5.6 without leaving the console:

Open the new Amazon Bedrock consolein a Region where the models are available, such as US East (N. Virginia). If you are in the existing console, chooseTry the new Bedrock console. - Create a project, or open an existing one.
In the model catalog, review the available GPT, Claude, and open-weight models. You can compare up to three models side by side on capabilities, modalities, context window, pricing, and Regional availability.
Choose a GPT-5.6 model to add it to your project.
Start an evaluation, enter a prompt, and review the model’s response. You can select up to three models to compare responses to the same prompt.

The following screenshot shows the model catalog in the new Amazon Bedrock console, where you can browse and compare GPT-5.6 and other models.

Reduce cost with GPT-5.6 prompt caching #

Agentic and multi-step workloads repeat much of their context between calls. System instructions, tool definitions, and reference files often stay the same while only the latest input changes. GPT-5.6 supports prompt caching in two modes on Amazon Bedrock. Implicit caching is on by default, so eligible requests are cached automatically without code changes. Explicit caching lets you mark cache breakpoints for precise control over which parts of a prompt are cached. In both modes, prompt caching reduces the cost of repeatedly processing shared context as request volume grows.

With a cache breakpoint, you mark the end of a reusable prompt prefix. On a subsequent request that shares that prefix, Amazon Bedrock reuses the processed context, and each call pays full price only for the new work. Cached input is billed at a 90% discount compared to uncached input tokens, and tokens written to cache are billed at 1.25 times the uncached input rate. For current rates, see the Amazon Bedrock pricing page. Cached content stays available for reuse for at least 30 minutes, long enough to cover the burst of calls a single agent run generates. Each breakpoint requires a prefix of at least 1,024 tokens, and you can set up to four cache checkpoints per request. If a prefix is shorter than the minimum, the request still succeeds, but nothing is cached and cached_tokens

stays zero.

Explicit caching with cache breakpoints

To cache a prefix, add a prompt_cache_breakpoint

to the content block that ends the reusable section, and set prompt_cache_options

to explicit

mode. Setting a consistent prompt_cache_key

across requests routes them to the same cache and improves match reliability. In the following example, the system instruction is cached, and the user’s question comes after the breakpoint so it can change without invalidating the cached prefix. The same request is sent twice to show a cache write followed by a cache read.

The system_prompt here is an abbreviated placeholder. Replace it with real content of at least 1,024 tokens. With a large enough prefix, the first call reports a nonzero cache_write_tokens

and the second a nonzero cached_tokens

, confirming the prefix was reused. Explicit mode is a good fit for agentic loops with a large, stable prefix, where you want full control over what gets cached.

Implicit caching

If you don’t set prompt_cache_options , GPT-5.6 uses implicit caching, the default mode. Amazon Bedrock places an automatic cache breakpoint on the latest message and honors any explicit breakpoints you add, so a stable prompt prefix can be reused across requests without any change to your input structure. This is the quickest way to benefit from caching. Keep static content (system instructions, tool definitions, reference documents) at the front of the prompt and variable content at the end, set a consistent prompt_cache_key

for related requests, and the endpoint reuses the processed prefix when it matches. The following example uses implicit caching. It sets no prompt_cache_options

and no breakpoint, and reuses the system_prompt

from the previous example (replace it with real content of at least 1,024 tokens) with a consistent prompt_cache_key :

The trade-off is control. In implicit mode, you don’t decide exactly where the cacheable boundary falls. Implicit caching suits chat and Retrieval Augmented Generation (RAG) workloads with a naturally stable prefix, while explicit caching suits agentic loops where you want to pin a large, known prefix and avoid unnecessary cache writes. Billing is the same in both modes. Cache reads receive the 90% discount, and cache writes are billed at 1.25 times the uncached input rate. For current rates, see the Amazon Bedrock pricing page. To turn caching off for a request, set prompt_cache_options

to explicit

mode without adding any breakpoints.

Monitor and evaluate your cache hit rate

Each response reports cache activity in the usage object. The input_tokens_details.cached_tokens

field is the number of input tokens read from cache, and cache_write_tokens

is the number written. Because cached_tokens

is already part of the total input_tokens

, you get the cached-input ratio by dividing cached_tokens

by input_tokens

:

A cache hit appears in the usage object as cached_tokens

greater than zero and cache_write_tokens

of zero. A zero cache_write_tokens

alone doesn’t confirm a hit, since you also see it when nothing was cached. Cache hits aren’t guaranteed on every request, even with an identical prefix, so measure cached_tokens

across calls rather than expecting a hit on any single one.

To track cache performance across many requests, aggregate cached_tokens

and cache_write_tokens

from each response in your application logging. The bedrock-mantle endpoint publishes account, project, and model token metrics to Amazon CloudWatch under the AWS/BedrockMantle namespace, but it does not publish a cache-specific metric, so the response usage object is the authoritative source for cache measurement.

Use GPT-5.6 with Codex #

Codex is the OpenAI coding agent for developers. It works with local files, repositories, terminals, and development environments to write features, fix bugs, run tests, and open pull requests. You can run Codex from the command line (Codex CLI), as an IDE extension for Visual Studio Code and JetBrains, or in the ChatGPT desktop app. Each of these can route its model inference to Amazon Bedrock so it runs in your AWS account with In-Region processing and the access controls described earlier.

To point Codex at Amazon Bedrock, set the model and provider in your ~/.codex/config.toml

file. The new Amazon Bedrock console also includes a Clients section that generates these connection instructions for you.

Codex authenticates with an API key or your AWS SDK credentials. If you set AWS_BEARER_TOKEN_BEDROCK

, Codex uses it first. Otherwise it falls back to the AWS SDK credential chain. The ChatGPT desktop app and the IDE extension might not inherit your shell environment, so place the variables they need in ~/.codex/.env

:

Restart the app or extension after you change ~/.codex/config.toml

or ~/.codex/.env

. If you run the Codex CLI instead, you can export the same variable in your shell rather than using the .env

file. Codex routes inference through the bedrock-mantle endpoint in supported commercial AWS Regions. For coding tasks, higher reasoning effort suits complex refactoring and debugging, while a lower level keeps routine edits fast.

The following screenshot shows Codex in the ChatGPT desktop app configured to run a GPT-5.6 model on Amazon Bedrock.

You can change the reasoning effort in the ChatGPT desktop app, choosing between Light, Medium, High, and Extra High for a task. The following screenshot shows the reasoning-effort selector.

Quotas and scaling #

When you invoke GPT-5.6 models, requests use on-demand inference on the Standard service tier, where you pay per token without reserving capacity.

Inference on the bedrock-mantle endpoint is governed by two per-model, per-Region quotas, one for input tokens per minute and one for output tokens per minute. There is no requests-per-minute quota. Cached input tokens read through prompt caching do not count against the input-tokens-per-minute quota, which is one more reason caching helps at scale. If a token-per-minute quota is exceeded, the endpoint returns an HTTP 429 response. Handle transient throttling with exponential backoff and a bounded retry count, which the OpenAI SDK supports through its max_retries

setting. For more information, refer to Quotas for the bedrock-mantle endpoint.

One recommended way to handle transient throttling is exponential backoff with a bounded retry count. The OpenAI SDK supports this through its max_retries

setting:

To reduce throttling on sustained high volume, spread large workloads across multiple minutes rather than firing them in tight bursts, and increase request rates gradually so throughput can track regional capacity.

Clean up #

On-demand inference incurs charges only when you invoke a model, so there is no infrastructure to tear down. To avoid unintended charges:

If you generated a short-term API key, it expires automatically within 12 hours. To revoke one sooner, delete the API key in the new Amazon Bedrock console. Deleting a key immediately revokes access for any application using it, so confirm no active applications depend on it first.
Each model invocation incurs per-token charges. For current rates, refer to

Amazon Bedrock pricing.

Conclusion #

In this post, we showed how to get started with OpenAI GPT-5.6 Sol, Terra, and Luna on Amazon Bedrock. We covered how to choose a variant, how to run inference through the Responses API on the bedrock-mantle endpoint, how to control reasoning effort and call tools, how to reduce cost with explicit prompt caching and measure your cache hit rate, and how to connect the OpenAI Codex coding agent. We also walked through quotas and scaling for the endpoint.

To get started:

Open the new Amazon Bedrock console, create a project, and evaluate a GPT-5.6 model against your prompts. - Run the Responses API sample from this post against your own data.
Add an explicit cache breakpoint to a repeated prompt prefix and measure the cache hit rate.
Evaluate Sol, Terra, and Luna on your workloads to choose the variant that fits your cost and latency profile.

For more information, refer to the following resources: Amazon Bedrock documentation OpenAI model cards on Amazon Bedrock Prompt caching for faster model inference Quotas for the bedrock-mantle endpoint Amazon Bedrock API keys Amazon Bedrock pricing

To discuss how GPT-5.6 on Amazon Bedrock can support your workloads, contact an AWS Representative.

source & further reading

aws.amazon.com — original article Build an explainable next-best-product recommendation system for banking on AWS Best practices for applying Amazon Bedrock Guardrails to code generation workflows Evaluating AI Agents: A production blueprint with Strands and AgentCore