AWS whitepapers documentation change
Summary
Updated navigation links and formatting in GDPR compliance whitepaper, changed from PDF reference to markdown version, updated breadcrumb navigation, and added hyperlinks to AWS service documentation (Amazon VPC, AWS Client VPN, AWS Direct Connect).
Security assessment
The changes are primarily formatting and navigation improvements. The content still discusses encryption in transit as a security best practice for GDPR compliance, but no specific security vulnerability or incident is mentioned. The updates include adding hyperlinks to AWS service pages and correcting navigation paths, which are routine documentation maintenance tasks.
Diff
diff --git a/whitepapers/latest/navigating-gdpr-compliance/encrypt-data-in-transit.md b/whitepapers/latest/navigating-gdpr-compliance/encrypt-data-in-transit.md index b628dfe8e..8c9444514 100644 --- a//whitepapers/latest/navigating-gdpr-compliance/encrypt-data-in-transit.md +++ b//whitepapers/latest/navigating-gdpr-compliance/encrypt-data-in-transit.md @@ -1 +1 @@ -[](/pdfs/whitepapers/latest/navigating-gdpr-compliance/navigating-gdpr-compliance.pdf#encrypt-data-in-transit "Open PDF") +[View a markdown version of this page](encrypt-data-in-transit.md) @@ -3 +3 @@ -[Documentation](/index.html)[AWS Whitepapers](https://aws.amazon.com/whitepapers/)[AWS Whitepaper](welcome.html) +[](/pdfs/whitepapers/latest/navigating-gdpr-compliance/navigating-gdpr-compliance.pdf#encrypt-data-in-transit "Open PDF") @@ -5 +5 @@ -This whitepaper is for historical reference only. Some content might be outdated and some links might not be available. +[Documentation](/index.html)[AWS Whitepapers](https://aws.amazon.com/whitepapers/)[AWS Whitepaper](navigating-gdpr-compliance-on-aws.html) @@ -11 +11 @@ AWS strongly recommends encrypting data in transit from one system to another, i -When you create an AWS account, a logically isolated section of the AWS Cloud—the Amazon Virtual Private Cloud (Amazon VPC—is provisioned to it. There, you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selecting your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can also create a hardware Virtual Private Network (VPN) connection between your corporate datacenter and your Amazon VPC, so you can use the AWS Cloud as an extension of your corporate datacenter. +When you create an AWS account, a logically isolated section of the AWS Cloud—the [Amazon Virtual Private Cloud](https://aws.amazon.com/vpc/) (Amazon VPC)—is provisioned to it. There, you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selecting your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can also create a hardware Virtual Private Network (VPN) connection between your corporate datacenter and your Amazon VPC, so you can use the AWS Cloud as an extension of your corporate datacenter. @@ -13 +13 @@ When you create an AWS account, a logically isolated section of the AWS Cloud— -For protecting communication between your Amazon VPC and your corporate datacenter, you can select from [several VPN connectivity options](https://docs.aws.amazon.com/vpc/latest/userguide/vpn-connections.html), and choose one that best matches your needs. You can use the AWS Client VPN to enable secure access to your AWS resources using client-based VPN services. You can also use a third-party software VPN appliance available in the AWS Marketplace, which you can install on an Amazon EC2 instance in your Amazon VPC. Alternatively, you can create an IPsec VPN connection to protect the communication between your VPC and your remote network. To create a dedicated private connection from a remote network to your Amazon VPC, you can use [Direct Connect](https://aws.amazon.com/directconnect/). You can combine this connection with an AWS Site-to-Site VPN to create an IPsec-encrypted private connection. +For protecting communication between your Amazon VPC and your corporate datacenter, you can select from several VPN connectivity options, and choose one that best matches your needs. You can use the [AWS Client VPN](https://aws.amazon.com/vpn/client-vpn/) to enable secure access to your AWS resources using client-based VPN services. You can also use a third-party software VPN appliance available in the AWS Marketplace, which you can install on an Amazon EC2 instance in your Amazon VPC. Alternatively, you can create an IPsec VPN connection to protect the communication between your VPC and your remote network. To create a dedicated private connection from a remote network to your Amazon VPC, you can use [AWS Direct Connect](https://aws.amazon.com/directconnect/). You can combine this connection with an AWS Site-to-Site VPN to create an IPsec-encrypted private connection.