Data protection in Amazon EMR
The Amazon shared
responsibility model
For data protection purposes, we recommend that you protect Amazon account credentials and set up individual accounts with Amazon Identity and Access Management. 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 TLS to communicate with Amazon resources. We require TLS 1.2.
-
Set up API and user activity logging with Amazon CloudTrail.
-
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 personal data that is stored in Amazon S3.
-
If you require FIPS 140-2 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-2
.
We strongly recommend that you never put sensitive identifying information, such as your customers' account numbers, into free-form fields such as a Name field. This includes when you work with Amazon EMR or other Amazon services using the console, API, Amazon CLI, or Amazon SDKs. Any data that you enter into Amazon EMR or other services might get picked up for inclusion in diagnostic logs. When you provide a URL to an external server, don't include credentials information in the URL to validate your request to that server.