AWS toolkit-for-visual-studio documentation change
Summary
Updated terminology from 'ELB load balancer' to 'Elastic Load Balancing load balancer'
Security assessment
This is a branding terminology update without technical changes to security configurations. No security mechanisms, access controls, or vulnerabilities are addressed. The change improves clarity but has no security impact.
Diff
diff --git a/toolkit-for-visual-studio/latest/user-guide/vpc-tkv.md b/toolkit-for-visual-studio/latest/user-guide/vpc-tkv.md index 0ba90b7e3..d46ac27c9 100644 --- a//toolkit-for-visual-studio/latest/user-guide/vpc-tkv.md +++ b//toolkit-for-visual-studio/latest/user-guide/vpc-tkv.md @@ -36 +36 @@ This section describes how to create an Amazon VPC that contains both public and -This is the minimal VPC configuration required to deploy an AWS Elastic Beanstalk environment in a VPC. In this scenario, the Amazon EC2 instances that host your application reside in the private subnet; the ELB load balancer that routes incoming traffic to your application resides in the public subnet. +This is the minimal VPC configuration required to deploy an AWS Elastic Beanstalk environment in a VPC. In this scenario, the Amazon EC2 instances that host your application reside in the private subnet; the Elastic Load Balancing load balancer that routes incoming traffic to your application resides in the public subnet. @@ -89 +89 @@ To delete the VPC, you must first terminate any Amazon EC2 instances in the VPC. - 1. If you have deployed an application to an AWS Elastic Beanstalk environment in the VPC, delete the environment. This will terminate any Amazon EC2 instances hosting your application along with the ELB load balancer. + 1. If you have deployed an application to an AWS Elastic Beanstalk environment in the VPC, delete the environment. This will terminate any Amazon EC2 instances hosting your application along with the Elastic Load Balancing load balancer.