Docs / AWS Bedrock

AWS Bedrock

Connect to AWS Bedrock using IAM roles or access keys, select a foundation model, and validate cost and latency on a representative dataset before production. Use tagging and CloudWatch metrics for deep visibility.

Bedrock supports multiple providers and models across regions. Adopt least-privilege IAM policies, prefer role-based auth (IRSA/EC2/ECS roles), and restrict network paths. Track version usage to plan controlled upgrades.

AWS Bedrock console showing model selection and region configuration

Setup

  1. 1

    Choose a model/region Pick the foundation model and region closest to users while meeting compliance.

  2. 2

    Configure IAM Create least-privilege policies and use roles over long-lived access keys.

  3. 3

    Enable observability Emit request metrics and tags for project, environment, and feature attribution.

  4. 4

    Validate and roll out Compare against baseline for quality/cost, then roll out with monitors.

Minimal Bedrock client setup
import boto3
from evaligo.integrations import BedrockIntegration

session = boto3.Session()
br_client = session.client('bedrock-runtime', region_name='us-east-1')

integration = BedrockIntegration(client=br_client, model_id='anthropic.claude-3-sonnet')

client = integration.create_client(temperature=0.3, max_tokens=1500)
print('Bedrock client ready:', bool(client))
Info

Cost controls: Use AWS Budgets with alerts and tag-based allocation. Combine with Evaligo cost tracking to identify optimization opportunities.

Evaluation comparison between Bedrock model and baseline with latency and cost breakdown

Related Documentation

Setup Tracing
Instrument and monitor requests
Cost Tracking
Allocate spend via tags and metadata
Dashboards
Create operational dashboards