Bug: Codex generates incorrect Amazon Bedrock Mantle endpoint

Open Beginner friendly
#37,246 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
aws, rust
Domain
api, backend, cloud

Research direction

Start by locating the Amazon Bedrock provider endpoint construction and reproduce the issue with the model, provider, and responses configuration shown here. Compare the generated URL with the expected Bedrock Mantle URL; done means requests use the expected path without the extra segment and the regression is covered by an appropriate test.

Written by the indexing model from the issue text.

Description

app aws-bedrock bug windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.730.61639

What subscription do you have?

free

What platform is your computer?

windows x64

What issue are you seeing?

Generated by Codex:
https://bedrock-mantle.ap-south-1.api.aws/openai/v1/responses

unexpected status 401 Unauthorized: The security token included in the request is invalid., url: https://bedrock-mantle.ap-south-1.api.aws/openai/v1/responses, request id: req_cvrakpk7f46eflkscjlacdsxm7xadylrkm3swgweroy2cajbcnma

What steps can reproduce the bug?

model = "openai.gpt-oss-120b"
model_provider = "amazon-bedrock"
model_reasoning_effort = "medium"

[model_providers.amazon-bedrock.aws]
wire_api = "responses"

What is the expected behavior?

Expected by Amazon Bedrock Mantle:

https://bedrock-mantle.ap-south-1.api.aws/v1/responses

As a result, requests fail because the generated endpoint does not match the current Bedrock Mantle API.

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.