Data protection in Amazon Q Developer
The AWS
shared
responsibility model
For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS 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 AWS resources. We recommend TLS 1.2 or later.
-
Set up API and user activity logging with AWS CloudTrail.
-
Use AWS encryption solutions, along with all default security controls within AWS 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-2 validated cryptographic modules when accessing AWS 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-2
.
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 Amazon Q or other AWS services using the AWS Management Console, API, AWS Command Line Interface (AWS CLI), or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs.
Amazon Q stores your questions, its responses, and additional context, such as console metadata and code in your IDE, to generate responses to your questions. Your code is also stored for features like code transformation and software development in the IDE. This data is stored for up to 90 days to provide the service, and then is permanently deleted. For information about how data is encrypted, see Data encryption in Amazon Q Developer. For information about how AWS may use some questions that you ask Amazon Q and its responses to improve our services, see Amazon Q Developer service improvement.
Regardless of where you use Amazon Q Developer, data is sent to and stored in an AWS Region in the US. With cross-region inferencing, your requests to Amazon Q Developer may be processed in the US East (N. Virginia) Region, the US West (Oregon) Region, or the US East (Ohio) Region, even if the AWS Management Console is set to a different AWS Region. Data processed during troubleshooting console error sessions is stored in the US West (Oregon) Region. All other data is stored in the US East (N. Virginia) Region.