Skip to main content
Bedrock Chat requires specific AWS services to be available in your chosen deployment region. This page outlines the supported regions and service availability requirements.

​
Supported Deployment Regions

Bedrock Chat can be deployed in regions where Amazon OpenSearch Serverless and Ingestion APIs are available (required for bots and knowledge bases).

​
Fully Supported Regions

As of August 2025, the following regions support all required services:
  • us-east-1 - US East (N. Virginia)
  • us-east-2 - US East (Ohio)
  • us-west-1 - US West (N. California)
  • us-west-2 - US West (Oregon)
  • ap-south-1 - Asia Pacific (Mumbai)
  • ap-northeast-1 - Asia Pacific (Tokyo)
  • ap-northeast-2 - Asia Pacific (Seoul)
  • ap-southeast-1 - Asia Pacific (Singapore)
  • ap-southeast-2 - Asia Pacific (Sydney)
  • eu-central-1 - Europe (Frankfurt)
  • eu-west-1 - Europe (Ireland)
  • eu-west-2 - Europe (London)
  • eu-south-2 - Europe (Spain)
  • eu-north-1 - Europe (Stockholm)
  • ca-central-1 - Canada (Central)
  • sa-east-1 - South America (São Paulo)
Check the official AWS documentation for the most up-to-date list of regions where OpenSearch Serverless is available.

​
Service Availability Requirements

Bedrock Chat requires the following AWS services in your deployment region:

​
Core Services (Required)

Amazon OpenSearch Serverless

Vector database for knowledge bases (RAG)

OpenSearch Ingestion APIs

Document ingestion for knowledge bases

Amazon DynamoDB

Conversation and bot metadata storage

Amazon S3

Document storage and static hosting

AWS Lambda

Backend API functions

Amazon API Gateway

REST and WebSocket APIs

Amazon Cognito

User authentication

Amazon CloudFront

Frontend content delivery

​
Optional Services

  • Lambda SnapStart: Improves Lambda cold start performance
    • Not available in all regions (check availability)
    • Can be disabled with enableLambdaSnapStart: false

​
Bedrock Region Configuration

The bedrockRegion parameter specifies where Bedrock API calls are made. This can be different from your deployment region.

​
Important Considerations

Bedrock is NOT available in all AWS regions. You must choose a region where Bedrock is available.
  1. Deployment Region: Where Bedrock Chat infrastructure is deployed
  2. Bedrock Region: Where Bedrock API calls are made (can be different)

​
Example Configuration

// Deploy infrastructure in Tokyo
// But use Bedrock in US East
bedrockChatParams.set("default", {
  bedrockRegion: "us-east-1",  // Bedrock API calls
});

// Deploy to ap-northeast-1 (Tokyo)
npx cdk deploy --all

​
Bedrock Available Regions

Check which regions support Bedrock:
Model Availability: Different Bedrock regions support different models. Ensure the models you want to use are available in your chosen Bedrock region.

​
Cross-Region and Global Inference

Bedrock Chat supports cross-region and global inference for improved availability and performance:

​
Cross-Region Inference

Routes inference requests within the same AWS region group (e.g., within US regions). 
bedrockChatParams.set("default", {
  enableBedrockCrossRegionInference: true,  // default: true
});

​
Global Inference

Routes inference requests to the optimal region worldwide based on latency and availability. 
bedrockChatParams.set("default", {
  enableBedrockGlobalInference: true,  // default: true
});
Some Service Control Policies (SCPs) may restrict cross-region or global inference. You can disable these features independently if needed.

​
Frontend WAF Region

US East 1 Required: CloudFront Web ACLs (AWS WAF) must be created in the us-east-1 region.
If your organization restricts resource creation outside your primary region: 
bedrockChatParams.set("default", {
  enableFrontendWaf: false,  // Disable CloudFront WAF
});
Disabling the Frontend WAF removes IP allow/deny controls at the CloudFront edge. Authentication and other application controls continue to work normally.

​
Region-Specific Considerations

​
Lambda SnapStart Regions

Lambda SnapStart is not available in all regions. If deploying to a region without SnapStart support: 
bedrockChatParams.set("default", {
  enableLambdaSnapStart: false,
});
Or via command line: 
./bin.sh  # SnapStart is disabled by default in bin.sh

​
IPv6 Support

CloudFront supports IPv6 in all regions by default. To disable: 
bedrockChatParams.set("default", {
  enableFrontendIpv6: false,
});
Or via command line: 
./bin.sh --disable-ipv6

​
Multi-Region Deployments

You can deploy Bedrock Chat in multiple regions for:
  • High Availability: Redundancy across regions
  • Data Residency: Keep data in specific geographic regions
  • Latency Optimization: Serve users from nearby regions

​
Example: Multi-Region Setup

// Tokyo deployment
bedrockChatParams.set("tokyo", {
  bedrockRegion: "us-east-1",  // Bedrock calls to US
});

// Frankfurt deployment
bedrockChatParams.set("frankfurt", {
  bedrockRegion: "us-east-1",  // Bedrock calls to US
});
Deploy to specific regions: 
# Deploy to Tokyo (ap-northeast-1)
AWS_DEFAULT_REGION=ap-northeast-1 npx cdk deploy --all -c envName=tokyo

# Deploy to Frankfurt (eu-central-1)
AWS_DEFAULT_REGION=eu-central-1 npx cdk deploy --all -c envName=frankfurt
Each regional deployment is independent with its own users, bots, and data.

​
Verifying Service Availability

Before deploying, verify service availability in your chosen region:
1

Check OpenSearch Serverless

Visit the OpenSearch Service console in your target region and verify Serverless is available.
2

Check Bedrock Availability

Visit the Bedrock console in your Bedrock region and verify model access.
3

Verify Other Services

Ensure your account has access to Lambda, API Gateway, DynamoDB, and other required services.

​
Pricing Considerations

Different regions have different pricing for AWS services. Key considerations:
  • Data Transfer: Cross-region Bedrock API calls incur data transfer charges
  • OpenSearch Serverless: Pricing varies by region
  • CloudFront: Pricing varies by edge location
Use the AWS Pricing Calculator to estimate costs for your chosen regions.

​
Next Steps

CloudShell Deployment

Deploy to your chosen region

Parameters Reference

Configure region-specific parameters

Multi-Environment

Set up multiple environments

Bedrock Model Access

Enable models in your Bedrock region

Build docs developers (and LLMs) love

Get started for freeTalk to us