Controlled Operation of the ChatGPT Desktop App via a Single Bedrock Endpoint in AWS GovCloud (US)
AWS published a configuration guide detailing how to route model inference for the ChatGPT desktop app (including the Codex coding agent) entirely to the Amazon Bedrock Mantle endpoint in the us-gov-west-1 region, while implementing a verifiable controlled deployment by security teams through network domain whitelisting, administrator policy files, and API-mode sign-in.
For organizations with data residency requirements, using OpenAI's coding agents presents a specific contradiction: model capabilities reside in the cloud, but inference data cannot leave controlled regions. On October 30, 2026, AWS published a configuration guide demonstrating how to resolve this contradiction within AWS GovCloud (US)—routing all model inference for the ChatGPT desktop app and Codex to the Amazon Bedrock Mantle endpoint in the us-gov-west-1 region, while simultaneously prohibiting the application from connecting to any OpenAI-owned domains via network policies.
The core mechanism of this architecture is network-domain-level restriction. The configuration file explicitly sets bedrock-mantle.us-gov-west-1.api.aws as the sole permitted external domain, while api.openai.com, chatgpt.com, auth.openai.com, platform.openai.com, and others are all set to deny. This means that even though the desktop application itself is distributed by OpenAI, its runtime network egress is locked to the AWS GovCloud (US) Bedrock endpoint, ensuring that inference data does not flow to OpenAI infrastructure.
The configuration employs a two-file model, reflecting a layered design for security governance. requirements.toml is an administrator-controlled rules file that establishes security limits users cannot override—for example, disabling browser use, remote desktop control, memory features, plugins, feedback, and telemetry export. config.toml instructs the application on how to operate: selecting which model provider (amazon-bedrock), which region, which named profile, sandbox mode, and network proxy settings. Administrators define impassable boundaries through the former, while users operate within those boundaries using the latter.