AWS publishes an enterprise rollout guide for Codex on Amazon Bedrock: sign in through IAM Identity Center and call GPT-5.6 Sol, Terra or Luna on Bedrock
Codex can use Bedrock for inference, so you don't need a second model-access and identity stack. The three rollout paths and what to check in a pilot.
// Key points
- Codex still runs on the developer's workstation, sending inference to supported OpenAI models through Bedrock; the examples use GPT-5.6 Sol, and Sol, Terra and Luna each need checking per account, Region and inference path.
- Three paths: Native AWS Access (the recommended starting point), AgentCore Gateway (managed routing and Bedrock Guardrails), or your own LLM gateway (controls in the request path).
- Identity flows from the existing IdP via SAML and SCIM into IAM Identity Center, which issues temporary credentials to Codex; the provider setting lives in user-level or managed config so a repository cannot change it.
- The open-source Guidance for Codex on AWS repository has quick starts for LiteLLM, Portkey, ADOT and CloudWatch.
Builder's takeRead with ChatGPT Enterprise arriving in AWS Marketplace on 11-09: OpenAI's enterprise products are moving into AWS billing and identity as a whole. If you already buy through AWS, follow the guide with five people on Native AWS Access for two weeks, attribute usage to each IAM identity, then decide whether you need a gateway.
// Background · from #OpenAI
Full timeline →- Nov 10 OpenAI describes Control Room, a central system that tracks model workloads across its research infrastructure and can rapidly stop them
- Nov 10 ChatGPT Enterprise is now available in AWS Marketplace, through existing AWS purchasing and billing
- Nov 8 OpenAI partners with Hacktron to find vulnerabilities in its own systems and test connections with third-party services using frontier AI