GKRootWire
AI Google Adds 'Preferred Source' Button to Help Publishers Fight AI Traffic LossesGadgets Linkdaze Launches a Smart Calendar Aimed at Running Your Whole HouseholdSecurity Popular Rust Crate arrayref Hijacked to Spread Infostealer MalwareCloud & Sysadmin GitHub Details Cause of August 17 Outage, Outlines Reliability FixesDev Tools Show HN: 'Huzzah' Proposes a Fresh Take on AI-Assisted CodingCloud & Sysadmin The Weird Science of Cooling Data Centers With UrineAI Google Adds 'Preferred Source' Button to Help Publishers Fight AI Traffic LossesGadgets Linkdaze Launches a Smart Calendar Aimed at Running Your Whole HouseholdSecurity Popular Rust Crate arrayref Hijacked to Spread Infostealer MalwareCloud & Sysadmin GitHub Details Cause of August 17 Outage, Outlines Reliability FixesDev Tools Show HN: 'Huzzah' Proposes a Fresh Take on AI-Assisted CodingCloud & Sysadmin The Weird Science of Cooling Data Centers With Urine
Dev Tools

Bug in Codex's AWS Bedrock Integration Triggers 10x Overcharges

A reported issue in OpenAI's Codex tool is causing some users to rack up bills far higher than expected when routing requests through AWS Bedrock.

A GitHub issue filed against OpenAI's Codex project describes a bug where usage routed through AWS Bedrock results in charges roughly ten times higher than anticipated. The issue has drawn attention on Hacker News, with developers sharing similar billing surprises after integrating Codex with Bedrock-hosted models.

While exact technical details are still being worked out in the thread, the pattern suggests a miscalculation somewhere in how token usage or request counts are tracked and billed when Codex talks to Bedrock's API layer instead of OpenAI's own infrastructure.

As of this writing, the issue remains open, with commenters comparing notes on their AWS invoices and asking OpenAI for a fix or clearer documentation on how the integration bills usage.

Why it matters: Billing bugs in AI tooling are especially costly because usage-based pricing can scale silently until an invoice arrives. Teams running Codex against Bedrock should audit recent bills and consider usage caps or alerts until this is resolved, since a 10x multiplier can turn a modest experiment into a budget crisis.

Sources: Hacker News