# Atlas with Amazon Nova Pro: Bedrock Billing and a 300K Window (2026) > Amazon Nova Pro costs $0.80 / $3.20 per Mtok on a 300,000 token window and bills through your existing AWS account, with no new vendor contract. Amazon Nova Pro is Amazon's flagship Nova, a 300K tokens multimodal model at $0.80 / $3.20 per Mtok (input / output). Inside Atlas, the real advantage of Amazon Nova Pro is that it bills through your existing AWS account with no new vendor contract, so procurement, IAM, and data residency all inherit from an account you already have. At roughly a sixth of Claude Opus 4.8's rate, Amazon Nova Pro is cheap, but it trails Claude and GPT-5 clearly on agentic coding: Nova's strength is price and procurement, not capability. ## Key takeaways - Amazon Nova Pro costs $0.80 / $3.20 per Mtok, roughly a sixth of Claude Opus 4.8's rate, on a 300,000 token window. - Amazon Nova Pro is billed through AWS, so procurement, IAM, and data residency all inherit from your existing account. - Atlas authenticates Bedrock through the standard AWS chain: `AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, `AWS_BEARER_TOKEN_BEDROCK`, or web identity token files. - Amazon Nova Pro trails Claude and GPT-5 clearly on agentic coding; Nova's strength is price and procurement, not capability. - Bedrock model IDs are region-prefixed (us., eu.), which is an easy misconfiguration when switching regions. ## Why pick Amazon Nova Pro for Atlas instead of a direct API? Amazon Nova Pro is billed through AWS, so procurement, IAM, and data residency all inherit from your existing account rather than needing a new vendor. For teams where adding a vendor takes months, Amazon Nova Pro at $0.80 / $3.20 per Mtok is the model that can start today. Procurement is the hidden gate on AI adoption, and Amazon Nova Pro walks around it. If your organization already runs on AWS, Amazon Nova Pro requires no new contract, no new data processing agreement, and no new security review of an unfamiliar vendor. IAM policies you already maintain govern access, and the region you already chose governs residency. Atlas authenticates Bedrock through the standard AWS chain: `AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, `AWS_BEARER_TOKEN_BEDROCK`, or web identity token files, so the credentials your team already uses are the credentials Atlas uses. ## How much does Amazon Nova Pro cost compared to Claude Opus 4.8? Amazon Nova Pro costs $0.80 / $3.20 per Mtok, roughly a sixth of Claude Opus 4.8's rate, on a 300,000 token window. That price point is the core argument for running Atlas on Amazon Nova Pro, and it holds on both the input and the output side. The economics of Amazon Nova Pro are straightforward: roughly a sixth of Claude Opus 4.8's rate, on a 300,000 token context window that is larger than many frontier models offer. Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion, which pushes a lot of tokens through the input side, and $0.80 per Mtok makes that cheap. Atlas computes a unified diff for every file edit and surfaces it for approval before writing, so the output side at $3.20 per Mtok covers the diffs. For high-volume, routine work across a large team, Amazon Nova Pro keeps the bill small. ## How do you configure Atlas for Amazon Nova Pro on Bedrock? Configure AWS credentials as usual for Amazon Nova Pro: `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`. Then enable the Nova Pro model in the Bedrock console for that region, because Bedrock models are opt-in per account, and run `atlas models amazon-bedrock` to confirm Atlas resolved it. Amazon Nova Pro requires one step that direct-API models do not: model access is opt-in per AWS account, so you must enable Nova Pro in the Bedrock console for the region you plan to use. Once enabled, select amazon.nova-pro-v1:0 from the `/models` dialog in Atlas. Atlas authenticates Bedrock through the standard AWS chain, so `AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, `AWS_BEARER_TOKEN_BEDROCK`, or web identity token files all work. If `atlas models amazon-bedrock` shows nothing, the usual cause is that Nova Pro has not been enabled in that region's Bedrock console. ## What is the region-prefix trap with Bedrock model IDs? Bedrock model IDs are region-prefixed with us. and eu., which is an easy misconfiguration when switching regions. An Atlas session that worked in us-east-1 can fail after an `AWS_REGION` change, because the Amazon Nova Pro model ID itself carries a region prefix. The region prefix on Bedrock model IDs catches people out. Amazon Nova Pro is exposed as amazon.nova-pro-v1:0, but Bedrock model IDs are region-prefixed (us., eu.), so moving an Atlas configuration between regions is not just an `AWS_REGION` change. If a working setup breaks after a region switch, check the model ID prefix before anything else, then re-run `atlas models amazon-bedrock` to see what Atlas actually resolved in the new region. Remember that Bedrock models are opt-in per account, so the model may also simply not be enabled in the new region's console yet. ## When should you pick a different model than Amazon Nova Pro? Pick a different model than Amazon Nova Pro when agentic coding quality is the priority. Amazon Nova Pro trails Claude and GPT-5 clearly on agentic coding; Nova's strength is price and procurement, not capability, even at $0.80 / $3.20 per Mtok on a 300K window. Amazon Nova Pro is an honest tradeoff, and the tradeoff is capability. On hard, multi-step agentic coding tasks inside Atlas, Claude and GPT-5 clearly outperform Amazon Nova Pro, so a team optimizing purely for output quality should look elsewhere. A team optimizing for the ability to start now, on an existing AWS account, at roughly a sixth of Claude Opus 4.8's rate, has a strong case for Amazon Nova Pro. Atlas lets you switch the active model and provider on the fly with favorites and recents, so Amazon Nova Pro can carry routine volume while a stronger model handles the hardest tasks. ## Setup 1. Configure AWS credentials as usual: `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`. 2. Enable the Nova Pro model in the Bedrock console for that region (models are opt-in per account). 3. Run `atlas models amazon-bedrock` to confirm Atlas resolved it. 4. Select amazon.nova-pro-v1:0 from the `/models` dialog. 5. If you switch AWS regions, re-check the region-prefixed model ID (us., eu.) before assuming Atlas is misconfigured. ## FAQ ### How much does Amazon Nova Pro cost per million tokens? Amazon Nova Pro costs $0.80 / $3.20 per Mtok (input / output), roughly a sixth of Claude Opus 4.8's rate, on a 300,000 token window. ### How do I use Amazon Nova Pro with Atlas? Configure AWS credentials as usual with `export AWS_PROFILE=my-profile` and `export AWS_REGION=us-east-1`, enable Nova Pro in the Bedrock console for that region, run `atlas models amazon-bedrock`, then select amazon.nova-pro-v1:0 from `/models`. ### Why does Atlas not see my Bedrock model? Bedrock models are opt-in per account, so Nova Pro must be enabled in the Bedrock console for the region you are using. Bedrock model IDs are also region-prefixed (us., eu.), which is an easy misconfiguration when switching regions. ### What is Amazon Nova Pro's context window? Amazon Nova Pro is a 300K tokens multimodal model. That window is larger than several frontier models offer, at $0.80 / $3.20 per Mtok. ### Is Amazon Nova Pro good for agentic coding? Amazon Nova Pro trails Claude and GPT-5 clearly on agentic coding. Nova's strength is price and procurement, not capability, so it suits routine volume rather than the hardest tasks. ### Which AWS credentials does Atlas use for Bedrock? Atlas authenticates Bedrock through the standard AWS chain: `AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, `AWS_BEARER_TOKEN_BEDROCK`, or web identity token files. ### Do I need a new vendor contract to use Amazon Nova Pro? No. Amazon Nova Pro is billed through AWS, so procurement, IAM, and data residency all inherit from your existing account rather than needing a new vendor. --- Canonical HTML: https://runatlas.sh/resources/models/amazon-nova-pro Source of truth: aeo_pages row `/resources/models/amazon-nova-pro` (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.