AWS AmazonECS documentation change
Summary
Updated prerequisites for linear deployments to include Network Load Balancer and Service Connect requirements, and added detailed Network Load Balancer configuration steps.
Security assessment
Changes involve deployment procedure documentation and Network Load Balancer setup instructions. While health check paths and deregistration delays are mentioned, these are standard operational configurations not tied to security vulnerabilities or new security features.
Diff
diff --git a/AmazonECS/latest/developerguide/deploy-linear-service.md b/AmazonECS/latest/developerguide/deploy-linear-service.md index 000775b42..cd6a4a030 100644 --- a//AmazonECS/latest/developerguide/deploy-linear-service.md +++ b//AmazonECS/latest/developerguide/deploy-linear-service.md @@ -21 +21 @@ Perform the following operations before you start a linear deployment. - 2. Amazon ECS linear deployments require that your service uses one of the following features: Configure the appropriate resources. + 2. Amazon ECS linear deployments require that your service to use one of the following features: Configure the appropriate resources. @@ -25 +25 @@ Perform the following operations before you start a linear deployment. - 3. Create a rule to route traffic to your new service revision. For more information, see [Listener rules](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-rules.html) in the _Elastic Load Balancing Application Load Balancers_. + * Network Load Balancer - For more information, see [Network Load Balancer resources for Amazon ECS blue/green, linear and canary deployments](./nlb-resources-for-blue-green.html). @@ -27 +27 @@ Perform the following operations before you start a linear deployment. - 4. Create a target group for your green service revision. When you use the `awsvpc` network mode for your tasks, the target type must be `ip`. For information about target groups, see [Target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html) in the _Elastic Load Balancing Application Load Balancers_. + * Service Connect - For more information, see [Service Connect resources for Amazon ECS blue/green, linear, and canary deployments](./service-connect-blue-green.html). @@ -191,0 +192,12 @@ Application Load Balancer | +Network Load Balancer | + 1. For **Load balancer type** , select **Network Load Balancer**. + 2. For **Load Balancer** , choose an existing Network Load Balancer. + 3. For **Choose container to load balance** , choose the container that hosts the service. + 4. For **Production listener** , choose the **Production listener port** , and the **Production listener protocol**. This is the listener for your production service revision traffic. + 5. For **Test listener** , choose the **Test listener port** , and the **Test listener protocol**. This is the listener for your test service revision traffic. + 6. For **Target group** , configure the following: + * For **Target group name** , enter a name and a protocol for the target group that the Network Load Balancer routes requests to. + * For **Protocol** , choose the protocol for the target group that the Network Load Balancer routes requests to. By default, the target group routes requests to the first container defined in your task definition. + * For **Deregistration delay** , enter the number of seconds for the load balancer to change the target state to `UNUSED`. The default is 300 seconds. + * For **Health check path** , enter an existing path within your container where the Application Load Balancer periodically sends requests to verify the connection health between the Application Load Balancer and the container. The default is the root directory (`/`). + * For **Alternate group name** , enter the group name for the target group for your test (green) service revision.