Data protection in IAM Identity Center
The AWS shared
responsibility model
We recommend that you secure your data in the following ways:
-
Use multi-factor authentication (MFA) with IAM Identity Center.
-
Use TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3.
-
Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see Working with CloudTrail trails in the AWS CloudTrail User Guide.
-
Use AWS encryption solutions, along with all default security controls within AWS services.
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 AWS IAM Identity Center, or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for diagnostic logs.
Encryption in transit
IAM Identity Center protects data in transit, as it travels to and from the service, by automatically encrypting all inter-network data using the Transport Layer Security (TLS) 1.2 or TLS 1.3 encryption protocol. Direct HTTPS requests sent to the IAM Identity Center APIs, other than OIDC and SCIM APIs, are signed by using the AWS Signature Version 4 Algorithm to establish a secure connection.
Data privacy
With IAM Identity Center, you retain control of your organization’s data. Your user and group identities stored in IAM Identity Center are shared with other AWS services such as AWS managed applications only if you enable them with IAM Identity Center, and if needed by those services.
For additional information, see the
AWS Data Privacy
FAQ
Data retention
IAM Identity Center stores your data such as user and group identities, and metadata, until you delete them from the service. When you delete an IAM Identity Center instance, the data it contains is also deleted.