AWS verified-access documentation change
Summary
Updated load balancer references from 'ELB' to 'Elastic Load Balancing'
Security assessment
The changes standardize service names without modifying security configurations or access controls. No vulnerabilities or security features are mentioned. This maintains documentation consistency but doesn't impact security posture.
Diff
diff --git a/verified-access/latest/ug/getting-started.md b/verified-access/latest/ug/getting-started.md index 0c6493184..a479b2158 100644 --- a//verified-access/latest/ug/getting-started.md +++ b//verified-access/latest/ug/getting-started.md @@ -44 +44 @@ The following are the prerequisites for completing this tutorial: - * An application running behind an internal load balancer from ELB. Associate your security group with the load balancer. + * An application running behind an internal load balancer from Elastic Load Balancing. Associate your security group with the load balancer. @@ -122 +122 @@ Use the following procedure to create a Verified Access group. -Use the following procedure to create a Verified Access endpoint. This step assumes that you have an application running behind an internal load balancer from ELB and a public domain certificate in AWS Certificate Manager. +Use the following procedure to create a Verified Access endpoint. This step assumes that you have an application running behind an internal load balancer from Elastic Load Balancing and a public domain certificate in AWS Certificate Manager.