GPT-56T 861 —
MUSE-SPK 835 -0.7%
GPT-56SC 828 -5.2%
QWEN-38X 824 —
CL-OP55X 822 —
GROK-46H 822 -5%
GPT-6A 820 —
GLM-5 784 -8.4%
CL-FAB5H 743 -5.6%
KIMI-K3X 742 -8.4%
CL-OP5H 720 -5.8%
CL-OP5X 709 -18%
CL-OP46H 698 -5.9%
CL-OP47H 690 -5.9%
GEM-38FH 677 +0.1%
GEM-37FH 657 -24%
GPT-56S 622 —
CL-OP47 582 -0.7%
GPT-55H 582 —
INKL 531 —
GEM-31P 513 —
GEM-3P 499 —
CL-OP46 496 -0.2%
CL-OP48 490 —
GPT-56T 861 —
MUSE-SPK 835 -0.7%
GPT-56SC 828 -5.2%
QWEN-38X 824 —
CL-OP55X 822 —
GROK-46H 822 -5%
GPT-6A 820 —
GLM-5 784 -8.4%
CL-FAB5H 743 -5.6%
KIMI-K3X 742 -8.4%
CL-OP5H 720 -5.8%
CL-OP5X 709 -18%
CL-OP46H 698 -5.9%
CL-OP47H 690 -5.9%
GEM-38FH 677 +0.1%
GEM-37FH 657 -24%
GPT-56S 622 —
CL-OP47 582 -0.7%
GPT-55H 582 —
INKL 531 —
GEM-31P 513 —
GEM-3P 499 —
CL-OP46 496 -0.2%
CL-OP48 490 —
← Back to feed

OpenAI Frontier Models and Codex Go GA on AWS — 5 Million Weekly Codex Users, GovCloud Now Included

OpenAI’s frontier models and Codex coding agent are now generally available on AWS, moving out of the limited preview that launched earlier this year and opening access to millions of AWS enterprise customers — including those operating in government cloud environments.

The GA release covers two products. OpenAI models on Amazon Bedrock let teams build AI applications through AWS-native security and governance controls, with access through IAM, single invoicing, and the compliance frameworks enterprises already use. Codex on Amazon Bedrock brings OpenAI’s software engineering agent — 5 million weekly active users as of the announcement — into the same AWS environment where engineering teams build and ship.

The previous covered story on this integration noted “limited preview.” GA changes the operational reality: procurement, security review, and production readiness are now resolved through AWS rather than a separate OpenAI relationship. That distinction matters more than it sounds for enterprise buyers. Procurement teams that already have AWS master agreements and security teams that have already approved Bedrock don’t need a new vendor review cycle. OpenAI effectively inherits the access that AWS has already negotiated.

GovCloud Changes the Addressable Market

The GovCloud inclusion is the headline most likely to drive near-term adoption. Federal agencies, defense contractors, and regulated industries that operate exclusively in AWS GovCloud regions have been locked out of the frontier model market in a practical sense: the compliance pathway did not exist.

That changes today. OpenAI on AWS GovCloud gives those customers a path to GPT-5.5 and Codex inside an environment that already satisfies FedRAMP, ITAR, and equivalent regulatory requirements. The addressable market expands to include the $200M+ Defense Department AI contract that was previously under dispute, as well as any agency running AI workloads through AWS’s government infrastructure.

The Strategic Context

OpenAI ended Microsoft exclusivity earlier this year, opening AWS and Google as deployment paths for OpenAI workloads. The AWS GA launch is the first major exercise of that broader distribution strategy at scale.

For Amazon, it is a competitive response to Anthropic’s deep integration with AWS — including Claude on Bedrock, a $25B Amazon commitment to Anthropic, and Anthropic’s Platform on AWS going GA with full feature parity, IAM auth, and single-invoice billing. Offering OpenAI models on Bedrock makes Amazon the neutral infrastructure provider rather than an implicit Anthropic channel partner.

For OpenAI, AWS distribution removes one of the friction points its enterprise sales team has been navigating: customers who are unwilling to establish a direct OpenAI billing and compliance relationship but already have AWS. Codex, in particular, benefits from this — enterprises building agentic coding workflows are disproportionately running infrastructure on AWS, and having Codex inside the same environment removes a significant integration burden.

The GA announcement lands one month after GitHub Copilot announced it would cancel thousands of Claude Code licenses by June 30 and move to Codex-based CLI tools. Those enterprise teams now have an AWS-native path for exactly that transition.