Under the Amazon Bedrock data protection architecture, model providers do not have any access to Amazon Bedrock logs, customer prompts, or completions. This is because Amazon Bedrock performs a deep copy of the model provider's inference and training software and deploys it in Model Deployment Accounts owned and operated solely by the Amazon Bedrock service team.
For secure communication with AWS resources, Amazon Bedrock requires TLS 1.2 and recommends TLS 1.3. Additionally, customers should avoid putting sensitive information in tags/free-form fields, AWS is responsible for global infrastructure, and model provider software is run in accounts owned solely by the Bedrock service team.
AWS PrivateLink allows you to create a private connection between your VPC and Amazon Bedrock without needing public IP addresses, an internet gateway, a NAT device, a VPN connection, or an AWS Direct Connect connection. Enabling private DNS on the interface endpoint routes Bedrock VPC API traffic automatically using standard regional DNS names without requiring code changes; otherwise, you would have to explicitly specify the custom VPC endpoint URL in your application code.
To manage and restrict access to Amazon Bedrock through an interface endpoint, you can attach a custom IAM endpoint policy. This policy specifies the permitted principals, actions, and resources, replacing the default policy that allows full access.
AWS PrivateLink allows the creation of a private connection between a VPC and Amazon Bedrock, enabling access without using an internet gateway, NAT device, VPN, or Direct Connect connection, and without requiring public IP addresses on instances. To restrict and control this access, a custom endpoint policy (an IAM resource) can be attached to the interface endpoint to specify allowed principals, actions, and resources.
If private DNS is enabled, all Amazon Bedrock API calls from within the VPC automatically route through the endpoint using standard service DNS names (such as bedrock-runtime.region.amazonaws.com) without any code changes. If private DNS is not enabled, the VPC endpoint URL must be explicitly specified in the API calls.
A highly regulated financial company wants to use Amazon Bedrock but must ensure that third-party model providers have absolutely no access to their proprietary prompts, completions, or system logs. How does Amazon Bedrock isolate and protect this data from model providers?
How confident are you in this answer?