Foundation Model · Amazon BedrockLlama FamilyFlagship TierTextMulti-Tier Pricing

Llama 3.1 405B

Amazon Bedrock token pricing and cost optimization reference for Llama 3.1 405B.Rates normalized to USD per 1 Million Tokens ($/1M) with prompt caching and batch API discounts across 3 AWS regions.

ProviderMeta

Maker HQMenlo Park, California, USA

Class / TierFlagship

ModalityText

Prompt CachingSave 75%

Batch APISave 50%

AWS Regions3 Global

Bedrock Model IDmeta.llama-3-1-405b-v1:0

Input / Prompt

$2.40/ 1M tokens

$0.0024 per 1K tokens

Output / Completion

$2.40/ 1M tokens

$0.0024 per 1K tokens

Prompt Cache Read

$0.60/ 1M tokens

Save 75% vs prompt

Batch Inference

$1.20/ 1M in

Save 50% via Batch API

Price Ratio

1 : 1.0

Prompt to completion factor

Regional Reach

3AWS Regions

Compare 3 regions ↓

Alternatives to Llama 3.1 405B

Option	Price vs Llama 3.1 405B	Why look at it
Llama 3.1 70B Latency Optimized Compare →	input-62%-$1.50/1M output-62%-$1.50/1M Standard tier, per 1M tokens	Next step down in price from Meta (balanced tier)
Llama 3.1 405B Latency Optimized Compare →	input+25%+$0.60/1M output+25%+$0.60/1M Standard tier, per 1M tokens	Next step up in price from Meta
Llama 3 70B Compare →	input+10%+$0.25/1M output+46%+$1.10/1M Standard tier, per 1M tokens	Same Llama line, different version (balanced tier)
Llama 3.3 70B Compare →	input-70%-$1.68/1M output-70%-$1.68/1M Standard tier, per 1M tokens	Also from Meta (balanced tier)

Llama 3.1 405B Spend Estimator

Model inference spend by prompt volume, cache hit rate, and batch processing.

Prompt Tokens (Millions / month)

M tokens

Completion Tokens (Millions / month)

M tokens

Prompt Cache Hit Rate(75% discount on cached context)

30%

Batch API Mode50% discount on non-realtime async jobs via S3

Estimated Monthly Spend

$0.00

Fresh Prompts:$0.00

Cached Prompts:$0.00

Completions:$0.00

Active: Input: $2.40/1M · Output: $2.40/1M

Key Cost Levers & Architecture

Practical mechanisms to reduce inference costs with Llama 3.1 405B on AWS

Prompt CachingSave ~75%

Caches repetitive system instructions, schemas, and document prefixes in memory with 5-minute and extended 1-hour TTL tiers.

Read Rate: $0.60 / 1M tokens
Write Rate (5m TTL): $3.00 / 1M tokens
Ideal for: Multi-turn conversations, RAG document queries, structured schemas

Batch InferenceSave 50%

Asynchronous bulk processing submitted via Amazon S3 with a standard 24-hour turnaround SLA.

Batch Input: $1.20 / 1M tokens
Batch Output: $1.20 / 1M tokens
Ideal for: Offline classification, synthetic data generation, benchmark evals

Cross-Region & Tiers3 Regions

AWS Bedrock supports standard on-demand inference, priority reserved throughput, and cross-region routing.

Standard: Lowest latency, pay-per-token with zero commitments
Cross-Region Routing: Automatically burst traffic to available regional capacity
GovCloud: Dedicated isolated compliance partitions with +20% uplift

Regional Pricing Matrix

Live rates across all 3 available AWS cloud regions

Baseline: $1.20/1M inGovCloud: $2.40/1M in3 Global Regions

AWS Region	Prompt Input $/1M	Completion Output $/1M	Cache Read $/1M	Batch Input $/1M	Pricing Tier
us-east-1 US East (N. Virginia)	$1.20	$1.20	—	$1.20	Baseline
us-west-2 US West (Oregon)	$2.40	$2.40	—	$1.20	+100% vs Baseline
us-east-2 US East (Ohio)	$2.40	$2.40	—	$1.20	+100% vs Baseline

Developer Quickstart

Invoke Llama 3.1 405B via Amazon Bedrock Converse API

Python (boto3) · Amazon Bedrock Runtime

import boto3

# Amazon Bedrock Converse API invocation
client = boto3.client("bedrock-runtime", region_name="us-east-1")

response = client.converse(
    modelId="meta.llama-3-1-405b-v1:0",
    messages=[
        {
            "role": "user",
            "content": [{"text": "Summarize key features and cost levers of Llama 3.1 405B."}]
        }
    ],
    inferenceConfig={
        "maxTokens": 1024,
        "temperature": 0.7
    }
)

output_text = response["output"]["message"]["content"][0]["text"]
usage = response["usage"]
print(f"Response: {output_text}")
print(f"Usage: {usage['inputTokens']} in, {usage['outputTokens']} out")