Skip to main content
AWS Bedrock allows you to access models like Claude through your own AWS infrastructure with enterprise-grade security and compliance.

​
Prerequisites

Before setting up AWS Bedrock models, you need:
  1. An AWS account with Bedrock access enabled
  2. IAM credentials with Bedrock permissions
  3. Model access enabled in your AWS Bedrock console
  4. Admin access to your Langdock workspace

​
AWS Setup Steps

​
1. Enable Model Access in AWS Bedrock

  1. Go to the AWS Bedrock Console
  2. Navigate to Model access in the left sidebar
  3. Click Manage model access
  4. Enable the models you want to use (e.g., Claude models from Anthropic)
  5. Wait for access to be granted (this may take a few minutes)

​
2. Create IAM Credentials

  1. Go to the AWS IAM Console
  2. Navigate to Users and click Create user
  3. Give the user a descriptive name (e.g., langdock-bedrock-access)
  4. Attach the AmazonBedrockFullAccess policy or create a custom policy with minimum required permissions:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "bedrock:InvokeModel",
                "bedrock:InvokeModelWithResponseStream"
            ],
            "Resource": "*"
        }
    ]
}
  1. Create an Access Key for the user:
    • Go to the user’s Security credentials tab
    • Click Create access key
    • Select Third-party service
    • Save both the Access Key ID and Secret Access Key
Store your credentials securely. The Secret Access Key is only shown once during creation.

​
Langdock Setup Steps

  1. Go to the model settings and click on Add Model
  2. Configure the Display Settings:
    • Provider: Anthropic (or the appropriate provider for your model)
    • Model name: The model you want to add
    • Hosting provider: AWS Bedrock
    • Region: EU or US based on your Bedrock region
    • Image analysis: Enable if the model supports vision
  3. Configure the Model Configuration:
    • SDK: Select Bedrock
    • Model ID: Use the Bedrock model identifier (see Model IDs below)
    • Context Size: Set according to the model (see the model configuration tables)
  4. Configure the Model Key (AWS credentials):
    When you select the Bedrock SDK, the UI relabels the fields: “Base URL” becomes Access Key ID and “API Key” becomes Secret Access Key.
    • Access Key ID: Your AWS Access Key ID
    • Secret Access Key: Your AWS Secret Access Key
    • Region: Your AWS region (e.g., us-east-1, eu-central-1)
  5. Click Save to add the model
  6. Test the model by sending a prompt before making it visible to all users

​
Model IDs

Bedrock model IDs follow provider-specific formats:
ProviderFormatExample
Anthropicanthropic.{model-name}-v1:0anthropic.claude-sonnet-4-6
Metameta.{model-name}-v1:0meta.llama4-maverick-17b-instruct-v1:0
Amazonamazon.{model-name}-v1:0amazon.nova-pro-v1:0
Check the AWS Bedrock supported models page for the exact model IDs — they include version dates and can change with new releases.

​
Cross-Region Inference Profiles

Bedrock supports cross-region inference profiles, which automatically route requests to available regions for better availability and lower latency. To use them, prefix the model ID with a geographic code:
PrefixScope
global.All commercial AWS regions
us.US regions only
eu.European regions only
apac.Asia-Pacific regions
For example: eu.anthropic.claude-sonnet-4-6 routes within EU regions only. Check the inference profiles documentation for available profiles per model.

​
Supported Regions

AWS Bedrock is available in multiple regions. Ensure your chosen region has access to your desired models:
  • US East (N. Virginia): us-east-1
  • US West (Oregon): us-west-2
  • EU (Frankfurt): eu-central-1
  • EU (Ireland): eu-west-1
  • EU (Paris): eu-west-3
  • Asia Pacific (Tokyo): ap-northeast-1
  • Asia Pacific (Sydney): ap-southeast-2

​
Network Configuration

If your organization uses network allowlisting, add the following domain to your allowlist:
ServiceDomain Pattern
AWS Bedrockbedrock.REGION.amazonaws.com
Replace REGION with your AWS region (e.g., us-east-1).

​
Troubleshooting

“Access Denied” errors:
  • Verify your IAM user has the correct Bedrock permissions
  • Check that model access is enabled in the Bedrock console
  • Ensure the Access Key ID and Secret Access Key are correct
Model not available:
  • Confirm the model is enabled in your AWS Bedrock model access settings
  • Verify the model is available in your selected region
  • Check that the model ID is correct and matches the Bedrock format
Authentication failures:
  • Double-check that the Access Key ID field contains your AWS Access Key ID
  • Verify the Secret Access Key field contains the complete Secret Access Key
  • Ensure the region setting matches your AWS Bedrock region
Slow responses or timeouts:
  • Consider using a region closer to your users
  • Check AWS Service Health Dashboard for any ongoing issues
  • Verify your AWS account has sufficient quotas for the model