aws-bedrocklisted

# AWS Bedrock Bedrock is the unified front door to multiple foundation models on AWS, with IAM-based access, regional residency, VPC endpoints, and built-in CloudWatch / CloudTrail. Reach for it when "we need the same model, but inside our AWS boundary, billed on our AWS account" matters more than calling provider SDKs directly. ## When to Activate - Calling Claude / Nova / Llama / Mistral / Cohere through `bedrock-runtime` - Building Bedrock Agents or Knowledge Bases (RAG with managed retrieval) - Adding Bedrock Guardrails (PII, profanity, contextual filters) - Embeddings via Titan / Cohere - Comparing Bedrock vs direct provider SDKs (Anthropic, OpenAI) - Provisioned throughput planning ## Bedrock vs Direct Provider SDKs | Need | Pick | |---|---| | Stay inside one AWS account / billing / IAM | Bedrock | | Latest Anthropic / OpenAI features same-day | Direct SDK | | Data residency (EU/AP), VPC endpoints | Bedrock | | PrivateLink, no public internet | Bedrock | | Lowest absolute cost on a single model | Often direct SDK | | Multi-model ensemble in one IAM boundary | Bedrock | Bedrock typically lags the provider's own API by weeks for new features. Confirm `Converse` supports a feature before designing around it. ## Converse API: The Default `Converse` (and `ConverseStream`) is the unified, model-agnostic API. Prefer it over `InvokeModel` — it normalises message structure, tool use, and streaming across models. ```python import boto3 client = boto3.client("bedrock-run