OpenAI Models and Codex Generally Available on Amazon Bedrock

The pricing structure is the quiet headline. OpenAI's models on Bedrock are billed per token at first-party rates with no AWS surcharge, and usage counts toward existing AWS spend commitments — "you pay per token with no seat licenses and no per-developer commitments" ^[2]. That collapses a procurement obstacle that has held many enterprises on Azure for OpenAI access: finance teams running an Enterprise Discount Program with AWS can now route OpenAI calls through committed spend instead of cutting a second invoice. Combined with AWS's enterprise controls — "IAM permissions, VPC and PrivateLink isolation, KMS encryption, and AWS CloudTrail audit logging" ^[1]— and the guarantee that processing stays inside the selected Bedrock region ^[2], the offering is engineered to look like a default rather than a migration.

Third-party reporting frames the broader commercial backdrop as a roughly $38B multi-year AWS deal ^[7], which helps explain why the dollar-for-dollar math works for both sides: AWS converts model traffic into committed cloud spend, while OpenAI gets distribution scale without giving up unit economics.

Until April, OpenAI's frontier distribution flowed through one hyperscaler. The Bedrock GA — landing one day after Microsoft's exclusivity ended ^[6]— ends that single-cloud era and puts OpenAI on the same Bedrock shelf where Anthropic has been AWS's flagship model partner. AWS CEO Matt Garman framed it bluntly: customers "trust the security of AWS" and were being forced "to go to other places" for OpenAI, friction the integration removes ^[5]. Sam Altman reinforced the immediacy: "this is not something in the future — it's starting right now" ^[5].

The competitive read is that Microsoft retains the M365/Copilot distribution moat — a stickiness contrarian voices have flagged in early developer discussions — while AWS gains a credible OpenAI inference business and a defensive answer to Azure for AI-first enterprise workloads. For OpenAI, two hyperscalers reduce single-vendor exposure heading into Managed Agents.

AWS's GA blog reports that around 5 million people use Codex weekly to write, review, refactor, debug, and modernize code ^[1], with earlier figures from the April partnership announcement citing 4 million developers weekly ^[2]. The GA pivot is governance: Codex on Bedrock is accessible via the Codex App, Codex CLI, and IDE integrations across VS Code, JetBrains, and Xcode, with all inference routed through OpenAI's Responses API hosted on Bedrock ^[2].

That means IDE-grade dev tooling now answers to IAM permissions, VPC isolation, KMS keys, and CloudTrail logs, and AWS explicitly states that prompts and responses are not used to train models or shared with model providers ^[1]. For regulated buyers — financial services, healthcare, defense contractors — who blocked or restricted other AI coding assistants on data-residency or audit grounds, the compliance posture is now equivalent to other Bedrock workloads. Early Reddit threads in r/aws have specifically probed BAA coverage and gating, signaling that compliance-bound teams are reading the GA announcement through that lens.

Bedrock Managed Agents, powered by OpenAI, is the next layer up. AWS describes it as "built with the OpenAI harness and engineered to unlock the full potential of OpenAI frontier models, delivering faster execution, sharper reasoning, and reliable steering of long-running tasks" ^[3]. Early endorsers include Box — whose Intelligent Content Management platform serves more than 115,000 organizations ^[4]— and Salesforce, with President of Enterprise & AI Technology Joe Inzerillo calling it "a really exciting step forward in agent infrastructure" ^[3].

AWS has also previewed Daybreak cybersecurity tools as a follow-on. Read together, the sequencing is deliberate: ship the models and Codex first to seed adoption inside existing AWS guardrails, then layer agent orchestration and security tooling on top so the most valuable workloads — long-running enterprise agents — land natively on Bedrock rather than via cross-cloud plumbing.

Within hours of GA, practitioner reaction skewed practical. On X, the dominant framing was "big unlock for AWS-locked teams," with engineers immediately publishing the minimal config change to point Codex at Bedrock and confirming GPT-5.5 and GPT-5.4 both work end-to-end. On Reddit, the angle split: r/aws threads pressed on BAA coverage and limited-preview gating, while r/OpenAI parsed the Microsoft/OpenAI revenue-share mechanics that made the AWS path commercially viable.

A community engineering analysis in r/LocalLLM quantified PrivateLink egress savings in the thousands of dollars per month for a 100 RPS RAG pipeline, contrasting the $0.01/GB PrivateLink rate with $0.09/GB public-internet egress, alongside 40-70ms roundtrip improvements when inference stays inside the AWS network boundary. The shape of the early conversation suggests adoption will be selective rather than wholesale: workloads already on AWS will route to Bedrock for the egress and governance wins, while greenfield agent-first deployments remain a contested ground between Bedrock Managed Agents and Microsoft's M365/Copilot distribution.