AWS Bedrock GPT-5.6: 1M Context and Regions Guide

Quick answer

On Amazon Bedrock, GPT-5.6 Sol, Terra, and Luna each support a 1 million-token context window. The current in-Region availability is narrower than the family name suggests:

Bedrock model	Model ID	In-Region availability
GPT-5.6 Sol	openai.gpt-5.6-sol	us-east-1 (N. Virginia), us-east-2 (Ohio)
GPT-5.6 Terra	openai.gpt-5.6-terra	us-east-1, us-east-2, us-west-2 (Oregon)
GPT-5.6 Luna	openai.gpt-5.6-luna	us-east-1, us-east-2, us-west-2

All three use the OpenAI-compatible Responses API at the Bedrock bedrock-mantle endpoint. The request path is /openai/v1/responses, not the standard Bedrock Runtime InvokeModel or Converse path.

For setup code and authentication, use the Bedrock GPT-5.6 Responses API guide.

What the 1M limit changes

The expanded window makes it technically possible to send larger repositories, document sets, or agent histories in one request. It does not prove that sending everything is the best design.

Before using the full window, test:

1. the rendered token count, including system instructions, tools, images, files, and prior outputs;
2. whether the required evidence is still retrieved and cited when surrounded by irrelevant material;
3. first-token and end-to-end latency at typical and worst-case sizes;
4. input, cache-write, cache-read, reasoning, and output token cost;
5. failure and retry behavior near the limit;
6. whether retention, logging, and data-location controls permit the full source set.

A 1M capacity can reduce application-side chunking, but retrieval is still useful when it narrows evidence, enforces permissions, or keeps changing sources current. Summarization and compaction are also still useful when an agent history contains stale decisions or verbose tool results.

Region selection is a workload constraint

Sol currently has two documented Regions; Terra and Luna have three. The model cards list in-Region endpoints and do not list Geo or Global inference IDs for these models. Do not assume that a cross-Region profile available to another Bedrock model also works for GPT-5.6.

Choose a Region only after checking:

• model availability for the selected tier;
• the location of source data, vector stores, tools, logs, and dependent services;
• residency and contractual requirements;
• service quotas and approved account access;
• failover behavior if the chosen Region or model is unavailable.

The endpoint embeds the Region:

https://bedrock-mantle.us-east-1.api.aws/openai/v1

Changing the Region is therefore an application and operations change, not just a console selection. Revalidate credentials, network policy, quotas, logs, and downstream data flows.

Avoid three context mistakes

Do not mix provider limits

The Bedrock announcement and model cards are the authority for Bedrock access. Direct OpenAI model documentation can show different context limits, model aliases, features, or availability. Keep provider metadata separate in model registries and user interfaces.

Do not treat capacity as guaranteed answer quality

Long input can contain conflicts, duplicates, malicious instructions, or stale files. Preserve source boundaries, prioritize trusted evidence, and evaluate whether the answer cites the correct portion of the input.

Do not resend stable context blindly

If a large prefix repeats, measure prompt caching. Bedrock GPT-5.6 supports implicit caching by default and explicit breakpoints for controlled stable prefixes. See the prompt caching cost guide.

Deployment checklist

• Select Sol, Terra, or Luna from the workload, not only the window size.
• Confirm the exact Bedrock model ID and Region in configuration.
• Use /openai/v1/responses on bedrock-mantle.
• Measure typical, p95, and worst-case token counts.
• Run evidence-retrieval and conflicting-source evaluations at long context.
• Log model, Region, input tokens, cached tokens, cache-write tokens, output tokens, latency, and errors.
• Test quota exhaustion, timeout, retry, and Region recovery.
• Recheck the live model card before production rollout.

Frequently asked questions

Which GPT-5.6 models have a 1 million-token context window on Amazon Bedrock?

AWS states that GPT-5.6 Sol, Terra, and Luna each support a 1 million-token context window on Amazon Bedrock.

Which AWS Regions support GPT-5.6 on Bedrock?

Sol is available in us-east-1 and us-east-2. Terra and Luna are available in those two Regions plus us-west-2, according to the August 3, 2026 AWS announcement and current model cards.

Does a 1 million-token context window remove the need for retrieval or caching?

No. A large window is a capacity limit, not a relevance, latency, or cost guarantee. Measure the real token count, keep evidence scoped, test answer quality, and cache a stable repeated prefix when the workload supports it.

Official sources

• AWS: GPT-5.6 Sol, Terra, and Luna now support 1 million-token context windows
• AWS model card: GPT-5.6 Sol
• AWS model card: GPT-5.6 Terra
• AWS model card: GPT-5.6 Luna

Source check: August 4, 2026. Recheck context, Regions, quotas, pricing, and endpoint support before deployment.