DeepSeek-R1
DeepSeek · Active · available in 3 of 31 regions
- Context window
- 128K
- 128,000 tokens
- Max output
- —
- Input / 1M
- $1.35
- us-east-1
- Output / 1M
- $5.40
What DeepSeek-R1 is good for
editorialDeepSeek-R1 offers a 128K-token context window, at the premium end of this provider’s range at $1.35 per 1M input tokens. Callable in 3 of 31 regions.
Suits
- Nothing specific stands out from the published capabilities.
Think twice if
- Agentic loops. No prompt caching published, so every step re-pays full price for the prompt prefix. Expensive for agents that resend a long context.
- Function calling. No tool use, so it cannot drive an agent loop or call your APIs — it answers from what is in the prompt.
- Documents with layout. Text only. Scanned PDFs, screenshots and charts need a vision model or an OCR step first.
- High volume. At $1.35 per 1M input tokens it sits at the expensive end of the DeepSeek range. Worth it for hard tasks, wasteful for bulk extraction.
- Invocation. Reachable only through a cross-region inference profile — calling the bare model ID returns a validation error. Use an ID such as us.deepseek.r1-v1:0.
This section is judgement, not data from AWS. It is composed from the capabilities, context window, price position and region coverage shown elsewhere on this page — so it stays in step with the daily snapshot rather than going stale.
Where teams typically use it
Coding
Writing, reviewing and refactoring code, usually across more than one file.
- · A review pass that flags real defects with a severity and leaves style alone.
- · A framework upgrade applied across a repository, one module at a time, tests green between each.
- · Turning a failing bug report into a reproducing test and then a fix.
Model & inference profile IDs
Base model ID — direct on-demand invoke
Cross-region inference profiles (1)
Regions marked Inference profile only require a profile ID rather than the base model ID — invoking the base ID there returns a validation error. Regional (us., eu.) profiles carry a 10% premium over global.
Pricing by region
USD per 1M tokens| Region | Input | Output | Cache read | Cache write | Batch in | Batch out | Source |
|---|---|---|---|---|---|---|---|
| us-east-1 US East (N. Virginia) | $1.35 | $5.40 | — | — | — | — | API |
| us-east-2 US East (Ohio) | $1.35 | $5.40 | — | — | — | — | API |
| us-west-2 US West (Oregon) | $1.35 | $5.40 | — | — | — | — | API |
Region availability
TPM / RPM are default account quotas from AWS Service Quotas where a model-specific limit is published. They are per-account defaults and adjustable on request.
Where this model actually runs
Under a strict residency constraint, DeepSeek-R1 can be served without the request leaving 1 of the 25 jurisdictions with a Bedrock region.
Common questions
- How much does DeepSeek-R1 cost on Amazon Bedrock?
- $1.35 per 1M input tokens and $5.40 per 1M output tokens in us-east-1.
- Which AWS regions support DeepSeek-R1?
- 3 of 31 regions: us-east-1, us-east-2, us-west-2. Regions marked profile-only need a cross-region inference profile ID such as us.deepseek.r1-v1:0 rather than the bare model ID.
- What is the context window of DeepSeek-R1?
- 128,000 tokens (128K).
- What is the model ID for DeepSeek-R1 on Bedrock?
- deepseek.r1-v1:0. In regions where it is only reachable through a cross-region inference profile, use a prefixed ID instead: us.deepseek.r1-v1:0.