# Atlas with Amazon Bedrock (gateway) in 2026: One IAM Boundary, Every Model > Amazon Bedrock (gateway) exposes Llama 4 Scout to Atlas with a 3,500,000 token context, the largest window Atlas can reach through any provider. Amazon Bedrock (gateway) fronts Claude, Llama, DeepSeek, Qwen, and Amazon's own Nova behind AWS IAM, and Atlas resolves AWS credentials through the full standard chain, including profiles and web identity tokens. Context varies by model (up to 3.5M on Llama 4 Scout). Pricing is passthrough at AWS rates: Nova Lite $0.06 / $0.24; Llama 4 Scout $0.17 / $0.66; DeepSeek-R1 $1.35 / $5.40 per Mtok. The friction is that models are opt-in per account and per region. ## Key takeaways - Claude, Llama 4, DeepSeek, Qwen3-Coder, and Nova all sit behind one IAM boundary, so one approval covers every model. - Llama 4 Scout is exposed with a 3,500,000 token context, the largest window Atlas can reach through any provider. - Pricing is passthrough at AWS rates: Nova Lite $0.06 / $0.24; Llama 4 Scout $0.17 / $0.66; DeepSeek-R1 $1.35 / $5.40 per Mtok. - Atlas supports the full AWS auth chain: `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`, `AWS_BEARER_TOKEN_BEDROCK`, web identity tokens, and container credentials. - Models are opt-in per account and per region, so `atlas models amazon-bedrock` shows an empty list until you enable them. ## What is Amazon Bedrock best at inside Atlas? Amazon Bedrock (gateway) is best inside Atlas at procurement. Claude, Llama 4, DeepSeek, Qwen3-Coder, and Nova all sit behind one IAM boundary, so a single procurement approval covers every model. For an enterprise, that is usually the entire reason Bedrock is on the list at all. The value of Amazon Bedrock (gateway) is organizational before it is technical. Getting five separate AI vendors through security review is five reviews. Getting Bedrock approved is one, and afterward Atlas can call Claude for a hard refactor, Llama 4 Scout for a long-context sweep, and Nova Lite at $0.06 / $0.24 per Mtok for cheap summarization, all billed to the same AWS account and all governed by the same IAM policies you already wrote. Atlas layers its own controls on top: every Atlas tool call is permission-gated against allow, ask, and deny rules before it runs, and Atlas computes a unified diff for every file edit and surfaces it for approval before writing. ## What is the largest context window Atlas can reach on Bedrock? Llama 4 Scout is exposed with a 3,500,000 token context on Amazon Bedrock (gateway), which is the largest window Atlas can reach through any provider. Llama 4 Scout also costs $0.17 / $0.66 per Mtok, so that enormous window is cheap to fill. A 3,500,000 token context on Llama 4 Scout is a different category of session. Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion and indexes code by AST declarations using tree-sitter, so a broad sweep over a monorepo returns whole declaration bodies. At 3.5M tokens, that sweep does not have to be trimmed. Add the plan, the files, every unified diff Atlas has computed, and the full conversation, and you are still inside the window. At $0.17 / $0.66 per Mtok, filling it is a rounding error against an AWS bill. ## How does Atlas authenticate to Amazon Bedrock? Atlas supports the full AWS auth chain for Amazon Bedrock (gateway): `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`, `AWS_BEARER_TOKEN_BEDROCK`, web identity token files, and container credentials. Authenticate as you already do for AWS, for example `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`. Amazon Bedrock (gateway) does not ask you to invent a new credential story for Atlas. If your laptop already has an AWS profile, Atlas uses it. If your CI runs on a web identity token file, Atlas uses that. If you are inside a container with container credentials, Atlas resolves those too. `AWS_BEARER_TOKEN_BEDROCK` covers the short-lived-token case. The practical consequence is that an Atlas session inherits whatever IAM role you are already assuming, so audit trails and least-privilege policies apply to model calls the same way they apply to S3. ## Why does atlas models amazon-bedrock show an empty list? Models on Amazon Bedrock (gateway) are opt-in per account and per region, so `atlas models amazon-bedrock` will show an empty or partial list until you enable them in the Bedrock console. That is the single most common Bedrock setup surprise for new Atlas users in 2026. The fix for an empty list from Amazon Bedrock (gateway) is not in Atlas, it is in the AWS console. Open Bedrock, enable the models you want for the account, and remember that the grant is per region: enabling Claude in us-east-1 does nothing for eu-west-1. Then run `atlas models amazon-bedrock` again and Atlas will show what your account actually resolved. The related trap is region prefixes on model IDs, us., eu., and global., which are a common source of misconfiguration when switching regions. Atlas handles the region prefix on the model ID for you when you select from `/models`. ## When should you pick a different provider instead of Amazon Bedrock? Pick a different provider than Amazon Bedrock (gateway) when setup cost outweighs governance. Bedrock models are opt-in per account and per region, and the 3 region prefixes (us., eu., global.) cause misconfiguration, so a plain API key provider reaches a working Atlas session faster than enabling Nova Lite at $0.06 / $0.24. Amazon Bedrock (gateway) is the right call when the organization requires it, and the wrong call when it does not. A solo developer who wants Atlas running in five minutes should export one API key and move on, because enabling models per region and resolving IAM roles is real work. A team whose code cannot leave an approved boundary should absolutely use Bedrock, and can then reach Claude, Llama 4 Scout at $0.17 / $0.66, DeepSeek-R1 at $1.35 / $5.40, and Nova Lite at $0.06 / $0.24 without another approval. Atlas lets you switch the active model and provider on the fly with favorites and recents, so both paths coexist. ## Setup 1. Authenticate as you already do for AWS: `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`. 2. Enable the models you want in the Bedrock console (they are opt-in per region). 3. Run `atlas models amazon-bedrock` to see what your account actually resolved. 4. Select a model from `/models`; Atlas handles the region prefix on the model ID for you. ## FAQ ### how to use amazon bedrock with atlas Authenticate as you already do for AWS with `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`, enable the models in the Bedrock console, run `atlas models amazon-bedrock`, then select a model from `/models`. ### why is atlas models amazon-bedrock returning nothing Bedrock models are opt-in per account and per region, so the list is empty or partial until you enable them in the Bedrock console. Enable them for your specific region, then re-run `atlas models amazon-bedrock`. ### what is the largest context window on amazon bedrock Llama 4 Scout is exposed with a 3,500,000 token context on Bedrock, the largest window Atlas can reach through any provider. Llama 4 Scout is priced at $0.17 / $0.66 per Mtok. ### how much does amazon bedrock cost for a coding agent Bedrock is passthrough at AWS rates. Nova Lite is $0.06 / $0.24, Llama 4 Scout is $0.17 / $0.66, and DeepSeek-R1 is $1.35 / $5.40 per Mtok, all billed to your existing AWS account. ### does atlas support aws profiles and iam roles for bedrock Yes. Atlas supports the full AWS auth chain: `AWS_PROFILE`, `AWS_ACCESS_KEY_ID`, `AWS_BEARER_TOKEN_BEDROCK`, web identity token files, and container credentials, so an Atlas session inherits the IAM role you already assume. ### why does my bedrock model id fail after changing region Region prefixes on Bedrock model IDs (us., eu., global.) are a common source of misconfiguration when switching regions, and models are enabled per region. Select the model from `/models` and Atlas handles the region prefix for you. ### can i use claude through amazon bedrock in atlas Yes. Amazon Bedrock fronts Claude, Llama, DeepSeek, Qwen, and Amazon's Nova behind AWS IAM. Enable Claude in the Bedrock console for your region, then select it from Atlas's `/models` dialog. --- Canonical HTML: https://runatlas.sh/resources/models/amazon-bedrock Source of truth: aeo_pages row `/resources/models/amazon-bedrock` (segment: Models) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.