AWS govcloud-us high security documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' for consistency, clarified FIPS 140-3 compliance requirements, and added explicit encryption requirements for export data
Security assessment
The changes explicitly document FIPS 140-3 cryptographic compliance requirements for TLS termination and mandate encryption for export data traversing global DNS infrastructure. This adds concrete security controls documentation for government workloads.
Diff
diff --git a/govcloud-us/latest/UserGuide/govcloud-elb.md b/govcloud-us/latest/UserGuide/govcloud-elb.md index a57f8427d..1069caa10 100644 --- a//govcloud-us/latest/UserGuide/govcloud-elb.md +++ b//govcloud-us/latest/UserGuide/govcloud-elb.md @@ -9 +9 @@ How Elastic Load Balancing differs for AWS GovCloud (US)Documentation for Elasti -ELB automatically distributes your incoming application traffic across multiple targets, such as EC2 instances. It monitors the health of registered targets and routes traffic only to the healthy targets. +Elastic Load Balancing automatically distributes your incoming application traffic across multiple targets, such as EC2 instances. It monitors the health of registered targets and routes traffic only to the healthy targets. @@ -11 +11 @@ ELB automatically distributes your incoming application traffic across multiple -ELB supports the following types of load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. All four types of load balancers are supported in AWS GovCloud (US) Regions. +Elastic Load Balancing supports the following types of load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. All four types of load balancers are supported in AWS GovCloud (US) Regions. @@ -15 +15 @@ ELB supports the following types of load balancers: Application Load Balancers, -Some features of ELB (ELB) TLS do not support FIPS 140-3 requirements by default. When using the Classic or Network Load Balancer, you can pass TCP traffic and terminate TLS on your target (for example, web server), that is configured to support FIPS 140-3 requirements. Application Load Balancer (ALB) supports selecting FIPS algorithms. +Some features of Elastic Load Balancing (ELB) TLS do not support FIPS 140-3 requirements by default. When using the Classic or Network Load Balancer, you can pass TCP traffic and terminate TLS on your target (for example, web server), that is configured to support FIPS 140-3 requirements. Application Load Balancer (ALB) supports selecting FIPS algorithms. @@ -19 +19 @@ Some features of ELB (ELB) TLS do not support FIPS 140-3 requirements by default - * When using the legacy bucket policy, specify the following AWS account IDs in the policy to grant ELB permission to write logs to your S3 bucket: + * When using the legacy bucket policy, specify the following AWS account IDs in the policy to grant Elastic Load Balancing permission to write logs to your S3 bucket: @@ -21 +21 @@ Some features of ELB (ELB) TLS do not support FIPS 140-3 requirements by default -Region | ELB account ID +Region | Elastic Load Balancing account ID @@ -26 +26 @@ AWS GovCloud (US-West) | 048591011584 - * Export data must be encrypted in transit outside of the export boundary. Because ELB uses global DNS servers, export traffic across ELB must be encrypted. + * Export data must be encrypted in transit outside of the export boundary. Because Elastic Load Balancing uses global DNS servers, export traffic across Elastic Load Balancing must be encrypted. @@ -35 +35 @@ AWS GovCloud (US-West) | 048591011584 -[ELB documentation](https://aws.amazon.com/documentation/elastic-load-balancing/). +[Elastic Load Balancing documentation](https://aws.amazon.com/documentation/elastic-load-balancing/). @@ -41 +41 @@ For AWS Services architected within the AWS GovCloud (US) Regions, the following - * All customer parameters provided as input to ELB (via console, APIs, or other mechanism) are not permitted to contain export-controlled data. Examples include the names of load balancers and the names of load balancer policies. + * All customer parameters provided as input to Elastic Load Balancing (via console, APIs, or other mechanism) are not permitted to contain export-controlled data. Examples include the names of load balancers and the names of load balancer policies.