The announcement itself is settled. OpenAI confirmed on June 1 that GPT-5.5, GPT-5.4, and Codex are generally available on Amazon Bedrock, accessible through existing AWS security, compliance, procurement, and billing workflows. Enterprise teams already covered the what. The question now is what the integration actually looks like at the endpoint level, and three details deserve attention before you commit to a production architecture.
The 272K figure is the one that matters. OpenAI’s developer documentation lists GPT-5.5’s context window as 400K tokens. That’s the architectural maximum. The effective production input limit, the threshold above which premium pricing tiers apply per OpenAI’s developer docs, is 272K tokens. For most enterprise use cases, 272K is still substantial. But if your team sized retrieval pipelines, document ingestion workflows, or long-context summarization jobs to the 400K headline figure, you’ll want to recalibrate before launch. The practical ceiling and the marketed ceiling aren’t the same number.
The endpoint has an SDK compatibility issue. The Bedrock integration routes through a new bedrock-mantle endpoint using the Responses API. Community reporting from AWS developer forums indicates the official OpenAI Python SDK may not be fully compatible with this endpoint at launch. The scope and current resolution status of this issue haven’t been confirmed from an authoritative AWS or OpenAI source, developers should verify current SDK compatibility directly in AWS documentation before building against this endpoint. Don’t assume your existing OpenAI SDK integration drops in cleanly.
Unanswered Questions
- Has AWS resolved the OpenAI Python SDK compatibility issue with the bedrock-mantle endpoint?
- Are audio and speech modalities now available on Bedrock, or is the launch-day gap still in effect?
- Does the 272K effective input limit apply uniformly across all Bedrock deployment configurations?
Audio modalities aren’t there yet. Per Wire reporting at publication time, audio input and speech modalities weren’t available at launch on Bedrock. This is consistent with selective rollout patterns in cross-platform deployments, not every capability ships simultaneously across surfaces. If your use case involves voice interfaces or audio processing pipelines, verify current modality support in AWS documentation before finalizing architecture. This caveat wasn’t prominently surfaced in initial launch coverage.
On pricing: according to OpenAI’s announcement, usage is billed at standard API rates with no additional Amazon Bedrock platform fees. That framing comes from the vendor and hasn’t been independently confirmed from a separate source, but it’s the stated commercial position as of launch.
The access restructuring that made this possible is also worth understanding precisely. OpenAI and Microsoft restructured their partnership to permit OpenAI to deploy on non-Azure cloud platforms. The nuance is real: per Microsoft’s own disclosure, API products developed jointly with third parties retain Azure exclusivity terms. This isn’t a clean break from the prior arrangement. It’s a targeted expansion that lets OpenAI reach AWS customers without fully abandoning the Microsoft-exclusive structure for certain product categories.
Warning
The 400K context window figure circulating in launch coverage is the architectural maximum, not the effective production limit. The 272K threshold, above which premium pricing applies, is the number your integration team needs. Confirm current limits at platform.openai.com/docs before finalizing pipeline sizing.
What to watch: AWS documentation will be the authoritative source for SDK compatibility resolution and current modality support, both are likely to update faster than vendor blog posts. Codex reached over 5 million active weekly developers before this Bedrock integration went live, per OpenAI’s own reporting, so the demand signal is real. The integration question isn’t whether teams will use this, it’s whether they’ll build against a stable endpoint before the SDK compatibility issues are resolved.
TJS synthesis: Read the architecture documentation before writing a line of integration code. The 272K effective limit, the SDK compatibility gap, and the missing audio modalities aren’t deal-breakers, but teams that sized their systems to the 400K headline and assumed SDK drop-in compatibility will hit friction. Wait for confirmed SDK resolution from AWS before committing to the bedrock-mantle endpoint in production. The announcement was real. The implementation checklist is longer than the press release suggested.