Data protection in AWS Resource Groups - AWS Resource Groups

Data protection in AWS Resource Groups

The AWS shared responsibility model applies to data protection in AWS Resource Groups. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS 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 AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.

For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or 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 require TLS 1.2 and recommend TLS 1.3.

  • 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 Resource Groups 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 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.

Data encryption

Compared to other AWS services, AWS Resource Groups has a minimal attack surface, because it does not provide a way of changing, adding, or deleting AWS resources except for groups. Resource Groups collects the following service-specific information from you.

  • Group names (not encrypted, not private)

  • Group descriptions (not encrypted, but private)

  • Member resources in groups (these are stored in logs, which are not encrypted)

Encryption at rest

There are no additional ways of isolating service or network traffic specific to Resource Groups. If applicable, use AWS-specific isolation. You can use the Resource Groups API and console in a VPC to help maximize privacy and infrastructure security.

Encryption in transit

AWS Resource Groups data is encrypted in transit to the service's internal database for backup. This is not user-configurable.

Key management

AWS Resource Groups is not currently integrated with AWS Key Management Service and does not support AWS KMS keys.

Internetwork traffic privacy

AWS Resource Groups uses HTTPS for all transmissions between Resource Groups users and AWS. Resource Groups uses transport layer security (TLS) 1.2, but also supports TLS 1.0 and 1.1.