Data protection in Amazon Application Recovery Controller
The Amazon shared
responsibility model
For data protection purposes, we recommend that you protect Amazon Web Services 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 in the Amazon CloudTrail User Guide.
-
Use Amazon encryption solutions, along with all default security controls within Amazon Web Services 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
.
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 ARC or other Amazon Web Services 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.
Encryption at rest
Customer configuration information is stored in service-owned Amazon DynamoDB global tables, and is encrypted at rest.
Datasets that contain the status of cells in a ARC cluster are written to an Amazon EBS volume for backup. ARC uses the default Amazon EBS encryption while the data is at rest.
Encryption in transit
Customer requests and responses—for ARC configuration, readiness status queries, cell state updates, and so on—are encrypted during transport throughout the service by using TLS.