AWS elasticbeanstalk documentation change
Summary
Changed all instances of 'ELB' to 'Elastic Load Balancing' for consistent naming
Security assessment
Terminology standardization without functional modifications. Listener configuration remains identical.
Diff
diff --git a/elasticbeanstalk/latest/dg/create_deploy_docker_ecs_listeners.md b/elasticbeanstalk/latest/dg/create_deploy_docker_ecs_listeners.md index 9988feb08..8ff569406 100644 --- a//elasticbeanstalk/latest/dg/create_deploy_docker_ecs_listeners.md +++ b//elasticbeanstalk/latest/dg/create_deploy_docker_ecs_listeners.md @@ -5 +5 @@ -# Using multiple ELB listeners +# Using multiple Elastic Load Balancing listeners @@ -7 +7 @@ -You can configure multiple ELB listeners on a ECS managed Docker environment in order to support inbound traffic for proxies or other services that don't run on the default HTTP port. +You can configure multiple Elastic Load Balancing listeners on a ECS managed Docker environment in order to support inbound traffic for proxies or other services that don't run on the default HTTP port. @@ -9 +9 @@ You can configure multiple ELB listeners on a ECS managed Docker environment in -Create a `.ebextensions` folder in your source bundle and add a file with a `.config` file extension. The following example shows a configuration file that creates an ELB listener on port 8080. +Create a `.ebextensions` folder in your source bundle and add a file with a `.config` file extension. The following example shows a configuration file that creates an Elastic Load Balancing listener on port 8080. @@ -37 +37 @@ For more information on the configuration file format, see [Adding and customizi -In addition to adding a listener to the ELB configuration and opening a port in the security group, you need to map the port on the host instance to a port on the Docker container in the `containerDefinitions` section of the `Dockerrun.aws.json` v2 file. The following excerpt shows an example: +In addition to adding a listener to the Elastic Load Balancing configuration and opening a port in the security group, you need to map the port on the host instance to a port on the Docker container in the `containerDefinitions` section of the `Dockerrun.aws.json` v2 file. The following excerpt shows an example: