Verified, then logged.
Sun 22 Nov 2026 · 00:33 KST / 15:33 UTC한국어 | ENSearch /

02 / IT · Analysis

AWS outlines three Codex access paths through Bedrock

AWS set out how teams can choose between direct access using existing credentials and gateways that enforce controls on model requests.

Two developer workstations connect to server equipment through separate cable routes, one passing through a network gateway and the other connecting directly. AI-generated image

AWS outlined three ways to connect Codex to Amazon Bedrock for development teams preparing enterprise deployments.

The AWS guide described a setup in which Codex runs on a developer’s computer and sends model requests to Bedrock, AWS’s model service. This fits the coding tool into an organisation’s existing AWS authentication and operations.

The guide makes the location of controls the basis for choosing a path. Direct access and gateways divide operational responsibility according to the controls a team needs.

Direct access with existing credentials

AWS recommended Native AWS Access for pilots where existing authentication and access permissions are sufficient. Employees use their organisation’s existing sign-in system to obtain temporary AWS credentials for Codex.

The guide instructed teams to keep Codex’s model-provider settings in user-level or centrally managed configuration. This prevents a code repository from changing the model provider.

AWS presented AgentCore Gateway as an option for teams needing an AWS-managed gateway. It recommended an LLM Gateway, a gateway for large language model requests, when controls must operate in the request path. Teams should consider building their own gateway only when the existing paths cannot meet their requirements.

User separation after sign-in

AWS instructed teams to test a direct model call, configure Codex and then run a safe task, in that order. The direct call isolates AWS access problems, while the final task checks the Codex configuration.

The guide’s user-separation check requires different users to run the same harmless task and confirm that their temporary access sessions and audit records remain distinct. Successful sign-in alone does not establish that activity can be attributed separately to each user.

Token counts and billing evidence

AWS distinguished Codex activity metrics from Bedrock service records. It instructed teams to use billing records for actual charges and avoid presenting token counts as a cost report.

The guide stated that “Telemetry does not establish correctness or safety.” Developers must still review and test generated changes before merging them into the codebase.

AWS placed hard budget limits in gateway policy when enforcement is needed in the request path. Monitoring usage and restricting requests therefore require separate controls.

The guide leaves teams to choose where those controls operate and test the resulting setup before expanding access. AWS did not disclose specific settings for hard budget limits in this guide.