Question

A European healthcare company must build a clinical document summarization application using Amazon Bedrock. Regulatory requirements mandate that all patient data, including inference requests and responses, must never leave the EU. The team wants to use Anthropic Claude models but discovers their preferred model version is not yet available in any EU region. Compliance has explicitly rejected any cross-region inference that could route data outside the EU. Which approach best satisfies both the functional and compliance requirements?

Accepted Answer

Select a foundation model that is available within an EU Bedrock region (such as an EU-hosted Claude or alternative model), even if it is not the exact preferred version, and deploy the workload entirely in that region

Answer

Use the model in a US region and rely on Bedrock Guardrails to redact PII before the request leaves the EU, ensuring no identifiable data crosses the boundary

Answer

Enable cross-region inference profiles restricted to the EU-US corridor so Bedrock automatically balances load while keeping data in the EU whenever possible

Answer

Deploy the preferred model version by importing it via Bedrock Custom Model Import into a US region and connect to it over a VPC endpoint with PrivateLink