# Amazon — OpenAI Codex on Amazon Bedrock

- Company: Amazon (amazon.com)
- Announced: 2026-11-11T23:35:47+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/openai-codex-on-amazon-bedrock/
- Record: https://forck.live/items/34923-openai-codex-on-amazon-bedrock
- Subject: Bedrock / Nova
- Models affected: GPT-5.6 Sol, Sol, Terra, Luna

Amazon published a guide for running OpenAI Codex against Amazon Bedrock, aimed at platform teams that want Codex without building a second model-access, identity and operations stack. Codex still runs on the developer workstation, and the design choice is how its model requests reach Bedrock and where policy and operational controls are applied. The post recommends starting with Native AWS Access for a small, least-privilege pilot, and offers AgentCore Gateway when a team wants AWS managed gateway infrastructure for routing or Amazon Bedrock Guardrails, or an LLM Gateway when controls must sit in the request path. A custom integration is described as the advanced version of the LLM Gateway pattern rather than a quick start. The examples use GPT-5.6 Sol and come from the open source Guidance for Codex on AWS repository, which includes quick starts for Native AWS Access, AgentCore Gateway, LiteLLM on ECS, Portkey and the AWS Distro for OpenTelemetry. The walkthrough has three checks: sign in with an IAM Identity Center profile and call Amazon Bedrock Runtime directly, point Codex at the approved model, then run a safe Codex task.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/openai-codex-on-amazon-bedrock/:

> Developers increasingly use Codex with Amazon Bedrock to explore unfamiliar code, make changes, and handle repetitive engineering work. For platform teams, the challenge is to make those tools available without creating a second model-access, identity, and operations stack.
> 
> Codex can use Amazon Bedrock for inference with supported OpenAI models. In this post, we show how to fit that path into the AWS identity, AWS Identity and Access Management (IAM), Regional, and observability practices your organization already uses. Codex still runs on the developer workstation. The main design choice is how its model requests reach Amazon Bedrock and where your organization applies policy and operational controls.
> 
> We begin with a small, least-privilege pilot and work through the checks that matter before access expands. The examples use GPT-5.6 Sol. Before starting the pilot, review Supported models by AWS Region in Amazon Bedrock to confirm that Sol, Terra, or Luna is available in the AWS Region and inference path you plan to use.
> 
> Recommended default: Start with Native AWS Access for a small, least-privilege pilot.

---

Record: https://forck.live/items/34923-openai-codex-on-amazon-bedrock
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
