GPT-5.5 - Amazon Bedrock
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

GPT-5.5

OpenAI logo. OpenAI — GPT-5.5

Model Details

GPT-5.5 is OpenAI's most capable model, designed for advanced coding, research, analysis, software operation, document workflows, and long-running agentic tasks. GPT-5.5 can understand open-ended goals, use tools, reason across longer workflows, navigate ambiguity, and carry complex tasks through to completion with less orchestration. For more information about model development and performance, see the model/service card.

  • Model launch date: June 1, 2026

  • EOL no sooner than: June 1, 2027

  • Legacy period: at least 6 months

  • Model lifecycle policy: Model lifecycle (For Models Launched Prior to Sept 7 2026)

  • Model EOL date: N/A

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Active

  • Context window: 1,050,000 tokens, shared between input and output

  • Max output tokens: 128,000

  • Marketplace product ID: prod-indw4nwkcsyua

Input Modalities Output Modalities
not-supported Audionot-supported Embedding
supported Imagenot-supported Image
not-supported Speechnot-supported Speech
supported Textsupported Text
not-supported Videonot-supported Video

Endpoints and APIs supported

The following tables show which endpoints and APIs are supported for GPT-5.5. For more information, see APIs supported by Amazon Bedrock and Inference endpoints supported by Amazon Bedrock.

Endpoint support

Endpoint Supported
bedrock-runtime supported
bedrock-mantle supported

APIs supported on bedrock-runtime endpoint

Messages Responses Chat Completions Converse Invoke
not-supported supported supported supported not-supported

APIs supported on bedrock-mantle endpoint

Messages Responses Chat Completions Converse Invoke
not-supported supported supported not-supported not-supported
Note

On bedrock-mantle, both inference APIs use the /openai/v1 base path, not /v1. Use either API with this model:

  • For Responses, use /openai/v1/responses.

  • For Chat Completions, use /openai/v1/chat/completions.

This applies to inference only. Model discovery stays on /v1/models, as it does for every model on bedrock-mantle. A request to /openai/v1/models returns 404. For more information, see Get list of models.

Tip

Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Inference endpoints supported by Amazon Bedrock for details.

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

Supported Not Supported

Features supported using bedrock-mantle endpoint

Converse content blocks

On the bedrock-runtime endpoint, Converse accepts text and image content blocks in user messages. This model doesn't accept document content blocks, and it doesn't accept an image content block inside a toolResult. A request that includes either is rejected with a ValidationException. To send a document to this model, use the Responses API with an input_file content part instead.

Pricing

All prices are in USD per 1 million tokens for the Standard tier.

The Input — 30-minute cache write column is the price per 1 million tokens written to the prompt cache. The 30-minute figure is how long a cached prompt prefix is retained, not a quantity of tokens. For more information, see prompt caching.

Commercial In-Region prices include a 10% fee over OpenAI rates. You do not need to add this fee.

Long-context rates apply to all input and output tokens, not just tokens above 272K.

Priority and Flex tiers are not supported for this model.

Commercial Regions — short context (272K input tokens or fewer)

Inference option Input Input — 30-minute cache write Input — cache read Output
In-Region$5.50—$0.55$33.00

Commercial Regions — long context (more than 272K input tokens)

Inference option Input Input — 30-minute cache write Input — cache read Output
In-Region$11.00—$1.10$49.50

Programmatic Access

Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.

Endpoint Model ID In-Region endpoint URL Geo inference ID Global inference ID
bedrock-runtime openai.gpt-5.5 Not supported us.openai.gpt-5.5 global.openai.gpt-5.5
bedrock-mantle openai.gpt-5.5 https://bedrock-mantle.{region}.api.aws/openai/v1 Not supported Not supported

For example, if region is us-east-1 (N. Virginia), then the bedrock-mantle endpoint URL will be "https://bedrock-mantle.us-east-1.api.aws/openai/v1". On bedrock-runtime, the base URL is "https://bedrock-runtime.{region}.amazonaws.com/openai/v1" and requests must name a cross-Region inference ID — us.openai.gpt-5.5 or global.openai.gpt-5.5 — as the model.

Service Tiers

Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers the fastest response times for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). Reserved provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see service tiers.

Standard Priority Flex Reserved
supported not-supported not-supported not-supported

Regional Availability

Regional availability at a glance

Amazon Bedrock offers three inference options: In-Region keeps requests within a single Region for strict compliance, Geo Cross-Region routes across Regions within a geography (such as US, EU, and APAC) while respecting data residency, and Global Cross-Region routes anywhere worldwide when there are no residency constraints. Refer to the Regional availability by models page for more details.

Availability differs by endpoint.

Availability using the bedrock-mantle endpoint

Region In-Region Geo Global
us-east-1 (N. Virginia)supportednot-supportednot-supported
us-east-2 (Ohio)supportednot-supportednot-supported

Availability using the bedrock-runtime endpoint

Region In-Region Geo Global
us-east-1 (N. Virginia)not-supportedsupportedsupported
us-east-2 (Ohio)not-supportedsupportedsupported
us-west-1 (N. California)not-supportedsupportedsupported
us-west-2 (Oregon)not-supportedsupportedsupported
ca-central-1 (Canada)not-supportedsupportedsupported
ca-west-1 (Calgary)not-supportedsupportedsupported
mx-central-1 (Mexico)not-supportednot-supportedsupported
eu-central-1 (Frankfurt)not-supportednot-supportedsupported
eu-central-2 (Zurich)not-supportednot-supportedsupported
eu-north-1 (Stockholm)not-supportednot-supportedsupported
eu-south-1 (Milan)not-supportednot-supportedsupported
eu-south-2 (Spain)not-supportednot-supportedsupported
eu-west-1 (Ireland)not-supportednot-supportedsupported
eu-west-2 (London)not-supportednot-supportedsupported
eu-west-3 (Paris)not-supportednot-supportedsupported
ap-east-2 (Taipei)not-supportednot-supportedsupported
ap-northeast-1 (Tokyo)not-supportednot-supportedsupported
ap-northeast-2 (Seoul)not-supportednot-supportedsupported
ap-northeast-3 (Osaka)not-supportednot-supportedsupported
ap-south-1 (Mumbai)not-supportednot-supportedsupported
ap-south-2 (Hyderabad)not-supportednot-supportedsupported
ap-southeast-1 (Singapore)not-supportednot-supportedsupported
ap-southeast-2 (Sydney)not-supportednot-supportedsupported
ap-southeast-3 (Jakarta)not-supportednot-supportedsupported
ap-southeast-4 (Melbourne)not-supportednot-supportedsupported
ap-southeast-5 (Malaysia)not-supportednot-supportedsupported
ap-southeast-6 (New Zealand)not-supportednot-supportedsupported
ap-southeast-7 (Thailand)not-supportednot-supportedsupported
il-central-1 (Tel Aviv)not-supportednot-supportedsupported
me-central-1 (UAE)not-supportednot-supportedsupported
me-south-1 (Bahrain)not-supportednot-supportedsupported
af-south-1 (Cape Town)not-supportednot-supportedsupported
sa-east-1 (São Paulo)not-supportednot-supportedsupported

Quotas and Limits

Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more information, see Quotas for Amazon Bedrock documentation and see the limits for the model.

Sample Code

Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account.

Step 2 - API key: Go to the Amazon Bedrock console and generate a long-term API key.

Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.

For both APIs, choose the OpenAI SDK tab.

OpenAI SDK
pip install openai

Step 4 - Set environment variables

Configure your environment to use the API key for authentication.

bedrock-runtime
OPENAI_API_KEY="<provide your Bedrock API key>" OPENAI_BASE_URL="https://bedrock-runtime.us-east-2.amazonaws.com/openai/v1"
bedrock-mantle
OPENAI_API_KEY="<provide your Bedrock API key>" OPENAI_BASE_URL="https://bedrock-mantle.us-east-2.api.aws/openai/v1"
Note

On bedrock-runtime, name a cross-Region inference profile as the model — us.openai.gpt-5.5 or global.openai.gpt-5.5. This model is not available for in-Region inference on that endpoint. Your IAM identity also needs bedrock:InvokeModel on your account's default project (arn:aws:bedrock:{region}:{account-id}:project/default) in addition to the inference profile.

Step 5 - Run your first inference request

Save the file as bedrock-first-request.py

bedrock-mantle

Use the settings from Step 4 - Set environment variables. Choose the bedrock-mantle tab. The Chat tab uses the Chat Completions API.

Responses API
from openai import OpenAI client = OpenAI() response = client.responses.create( model="openai.gpt-5.5", input="Can you explain the features of Amazon Bedrock?" ) print(response)
Chat
from openai import OpenAI client = OpenAI() response = client.chat.completions.create( model="openai.gpt-5.5", messages=[{"role": "user", "content": "Can you explain the features of Amazon Bedrock?"}] ) print(response)