Data protection in Amazon WorkSpaces - Amazon WorkSpaces
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Data protection in Amazon WorkSpaces

The Amazon shared responsibility model applies to data protection in Amazon WorkSpaces. As described in this model, Amazon is responsible for protecting the global infrastructure that runs all of the Amazon Web Services Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. This content includes the security configuration and management tasks for the Amazon Web Services that you use. For more information about data privacy, see the Data Privacy FAQ.

For data protection purposes, we recommend that you protect Amazon Web Services account credentials and set up individual user accounts with 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 recommend TLS 1.2 or later.

  • 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 confidential or sensitive information, such as your customers' email addresses, into tags or free-form fields such as a Name field. This includes when you work with WorkSpaces or other Amazon services using the console, API, Amazon CLI, or Amazon SDKs. Any data that you enter into tags or free-form 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

You can encrypt the storage volumes for your WorkSpaces using Amazon KMS Key from Amazon Key Management Service. For more information, see Encrypted WorkSpaces.

When you create WorkSpaces with encrypted volumes, WorkSpaces uses Amazon Elastic Block Store (Amazon EBS) to create and manage those volumes. EBS encrypts your volumes with a data key using the industry-standard AES-256 algorithm. For more information, see Amazon EBS Encryption in the Amazon EC2 User Guide for Windows Instances.

Encryption in transit

For PCoIP, data in-transit is encrypted using TLS 1.2 encryption and SigV4 request signing. The PCoIP protocol uses encrypted UDP traffic, with AES encryption, for streaming pixels.The streaming connection, using port 4172 (TCP and UDP), is encrypted by using AES-128 and AES-256 ciphers, but the encryption defaults to 128-bit. You can change this default to 256-bit, either by using the Configure PCoIP Security Settings Group Policy setting for Windows WorkSpaces, or by modifying the PCoIP Security Settings in the pcoip-agent.conf file for Amazon Linux WorkSpaces.

To learn more about Group Policy administration for Amazon WorkSpaces, see Configure PCoIP security settings in Manage your Windows WorkSpaces. To learn more about modifying the pcoip-agent.conf file, see Control PCoIP Agent behavior on Amazon Linux WorkSpaces and PCoIP Security Settings in the Teradici documentation.

For WorkSpaces Streaming Protocol (WSP), streaming and control data in-transit is encrypted using DTLS 1.2 encryption for UDP traffic and TLS 1.2 encryption for TCP traffic, with AES-256 ciphers.