AWS verified-access documentation change
Summary
Replaced 'Elastic Load Balancing' with 'ELB' abbreviation in two places
Security assessment
Purely cosmetic change updating terminology without altering security implications or content. No security-related modifications were made.
Diff
diff --git a/verified-access/latest/ug/getting-started.md b/verified-access/latest/ug/getting-started.md index a479b2158..0c6493184 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 Elastic Load Balancing. Associate your security group with the load balancer. + * An application running behind an internal load balancer from ELB. 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 Elastic Load Balancing 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 ELB and a public domain certificate in AWS Certificate Manager.