Amazon Bedrock ensures data privacy and security for enterprise users through encryption, access controls, and strict isolation of customer data. As a managed service, Bedrock encrypts data both in transit and at rest using AWS Key Management Service (KMS). For example, data sent to third-party models via API calls is protected with TLS encryption, and stored inputs or outputs (if retained) are encrypted using customer-managed keys. Bedrock also prevents third-party model providers from accessing or retaining user data—requests are processed without exposing sensitive information to model vendors.
The service enforces granular access controls through AWS Identity and Access Management (IAM). Developers can define policies to restrict which users, roles, or applications can invoke specific models. For instance, a team working with financial data might limit access to Bedrock’s Claude model to only authorized personnel, while blocking other models. Bedrock also integrates with AWS PrivateLink, enabling private network connectivity to avoid exposing traffic to the public internet. Additionally, audit logs via AWS CloudTrail track all API activity, allowing enterprises to monitor model usage and verify compliance with internal policies.
Bedrock addresses compliance by adhering to AWS’s global security standards, including SOC 2, ISO 27001, and GDPR. Third-party models available in Bedrock are vetted to meet AWS’s security requirements, ensuring they don’t store or misuse customer data. For example, when using Stability AI’s models, prompts and outputs are transiently processed without being retained by Stability AI. Enterprises can also configure data residency rules, ensuring processing occurs in specific geographic regions. By combining AWS infrastructure safeguards with contractual obligations for third-party providers, Bedrock minimizes risks while maintaining interoperability with external models.