# Data protection in Amazon Bedrock AgentCore
<a name="data-protection"></a>

The Amazon [shared responsibility model](https://www.amazonaws.cn/compliance/shared-responsibility-model/) applies to data protection in Amazon Bedrock AgentCore. As described in this model, Amazon is responsible for protecting the global infrastructure that runs all of the Amazon Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the Amazon services that you use. For more information about data privacy, see the [Data Privacy FAQ](https://www.amazonaws.cn/compliance/data-privacy-faq/) . For information about data protection in Europe, see the [Amazon Shared Responsibility Model and GDPR](https://www.amazonaws.cn/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the * Amazon Security Blog*.

For data protection purposes, we recommend that you protect Amazon account credentials and set up individual users with Amazon IAM Identity Center or Amazon Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:
+ Use multi-factor authentication (MFA) with each account.
+ Use SSL/TLS to communicate with Amazon resources. We require TLS 1.2 and recommend TLS 1.3.
+ Set up API and user activity logging with Amazon CloudTrail. For information about using CloudTrail trails to capture Amazon activities, see [Working with CloudTrail trails](https://docs.amazonaws.cn/awscloudtrail/latest/userguide/cloudtrail-trails.html) in the * Amazon CloudTrail User Guide*.
+ Use Amazon encryption solutions, along with all default security controls within Amazon services.
+ Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.
+ If you require FIPS 140-3 validated cryptographic modules when accessing Amazon through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see [Federal Information Processing Standard (FIPS) 140-3](https://www.amazonaws.cn/compliance/fips/).

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with AgentCore or other Amazon services using the console, API, Amazon CLI, or Amazon SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

 **AgentCore Gateway-specific considerations** 
+ AgentCore Gateway accepts inputs from customers for tool definitions and service details, which can potentially contain personally identifiable information (PII).
+ Customer data and metadata are stored in Amazon DynamoDB and Amazon Simple Storage Service and are encrypted either with a service key or a customer-managed KMS key.
+ Customer content is not used to provide and maintain the AgentCore Gateway service.
+ Metadata doesn’t include customer information (such as PII).
+ Metrics and logs are stored in CloudWatch.

**Topics**
+ [Data encryption](data-encryption.md)
+ [Protecting your data using VPC and Amazon PrivateLink](vpc.md)
+ [Cross-region inference in Amazon Bedrock AgentCore Memory, Policy in Amazon Bedrock AgentCore, and AgentCore Evaluations](cross-region-inference.md)