AWS elasticloadbalancing documentation change
Summary
Updated references from 'ELB' to 'Elastic Load Balancing' for consistency, including links to GitHub repositories, API documentation, and user guides. No functional changes.
Security assessment
Changes are purely branding/nomenclature updates replacing 'ELB' acronym with full service name. No security vulnerabilities, configurations, or features are mentioned or modified in the diff. Updates include non-security links and general migration instructions.
Diff
diff --git a/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.md b/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.md index 10c13b5a6..7638943e9 100644 --- a//elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.md +++ b//elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.md @@ -9 +9 @@ Benefits of migratingMigration wizardCopy utility migrationManual migrationPreve -Elastic Load Balancing supports the following types of load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. For information about the different features of each load balancer type, see [ELB features](https://aws.amazon.com/elasticloadbalancing/features/). +Elastic Load Balancing supports the following types of load balancers: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers. For information about the different features of each load balancer type, see [Elastic Load Balancing features](https://aws.amazon.com/elasticloadbalancing/features/). @@ -135 +135 @@ The wizard creates a new load balancer. The wizard doesn't convert the existing -The load balancer copy utilities are available within the ELB Tools repository, on the AWS GitHub page. +The load balancer copy utilities are available within the Elastic Load Balancing Tools repository, on the AWS GitHub page. @@ -139 +139 @@ The load balancer copy utilities are available within the ELB Tools repository, - * [ELB Tools](https://github.com/aws/elastic-load-balancing-tools) + * [Elastic Load Balancing Tools](https://github.com/aws/elastic-load-balancing-tools) @@ -150 +150 @@ The load balancer copy utilities are available within the ELB Tools repository, -The following information provides general instructions for manually creating a new Application Load Balancer or Network Load Balancer based on an existing Classic Load Balancer in a VPC. You can migrate using the AWS Management Console, the AWS CLI, or an AWS SDK. For more information, see [Getting started with ELB](./load-balancer-getting-started.html). +The following information provides general instructions for manually creating a new Application Load Balancer or Network Load Balancer based on an existing Classic Load Balancer in a VPC. You can migrate using the AWS Management Console, the AWS CLI, or an AWS SDK. For more information, see [Getting started with Elastic Load Balancing](./load-balancer-getting-started.html). @@ -208 +208 @@ If you migrated your Classic Load Balancer to an Application Load Balancer or Ne - * Update code that uses ELB API version 2012-06-01 to use version 2015-12-01. + * Update code that uses Elastic Load Balancing API version 2012-06-01 to use version 2015-12-01. @@ -219 +219 @@ If you migrated your Classic Load Balancer to an Application Load Balancer or Ne - * [Identity and access management for ELB](./load-balancer-authentication-access-control.html) + * [Identity and access management for Elastic Load Balancing](./load-balancer-authentication-access-control.html) @@ -245 +245 @@ You can create an IAM policy that prevents users from creating Classic Load Bala -Both the [ELB V2](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awselasticloadbalancingv2.html) and [ELB V1](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awselasticloadbalancing.html) APIs provide a `CreateLoadBalancer` API action. When you create a Classic Load Balancer, you use the V1 API action, which creates both the load balancer and listeners. When you create an Application Load Balancer, Network Load Balancer, or Gateway Load Balancer, you use the V2 API action, which creates only the load balancer. The V2 API provides a `CreateListener` action, which you use to create listeners for a load balancer after you create it. +Both the [Elastic Load Balancing V2](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awselasticloadbalancingv2.html) and [Elastic Load Balancing V1](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awselasticloadbalancing.html) APIs provide a `CreateLoadBalancer` API action. When you create a Classic Load Balancer, you use the V1 API action, which creates both the load balancer and listeners. When you create an Application Load Balancer, Network Load Balancer, or Gateway Load Balancer, you use the V2 API action, which creates only the load balancer. The V2 API provides a `CreateListener` action, which you use to create listeners for a load balancer after you create it.