AWS cli documentation change
Summary
Removed Network Load Balancer from supported deployment strategies' load balancer requirements
Security assessment
Change limits supported load balancer types but doesn't indicate a security vulnerability or mitigation
Diff
diff --git a/cli/latest/reference/ecs/create-service.md b/cli/latest/reference/ecs/create-service.md index eaf355b0e..65ea916d8 100644 --- a//cli/latest/reference/ecs/create-service.md +++ b//cli/latest/reference/ecs/create-service.md @@ -15 +15 @@ - * [AWS CLI 2.31.27 Command Reference](../../index.html) » + * [AWS CLI 2.31.28 Command Reference](../../index.html) » @@ -104 +104 @@ Rolling updates are the default deployment strategy for services and provide a b - * `LINEAR` : A _linear_ deployment strategy (`LINEAR` ) gradually shifts traffic from the current production environment to a new environment in equal percentage increments over a specified time period. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic. Linear deployments are best suited for the following scenarios: + * `LINEAR` : A _linear_ deployment strategy (`LINEAR` ) gradually shifts traffic from the current production environment to a new environment in equal percentage increments. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic. Linear deployments are best suited for the following scenarios: @@ -108 +108 @@ Rolling updates are the default deployment strategy for services and provide a b - * Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect + * Load balancer requirement: When your service uses Application Load Balancer or Service Connect @@ -113 +113 @@ Rolling updates are the default deployment strategy for services and provide a b - * Load balancer requirement: When your service uses Application Load Balancer, Network Load Balancer, or Service Connect + * Load balancer requirement: When your service uses Application Load Balancer or Service Connect @@ -621,0 +622,2 @@ JSON Syntax: +>> * `LINEAR` \- A _linear_ deployment strategy (`LINEAR` ) gradually shifts traffic from the current production environment to a new environment in equal percentages over time. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic. +>> * `CANARY` \- A _canary_ deployment strategy (`CANARY` ) shifts a small percentage of traffic to the new service revision first, then shifts the remaining traffic all at once after a specified time period. This allows you to test the new version with a subset of users before full deployment. @@ -702 +704 @@ JSON Syntax: ->>> The percentage of production traffic to shift in each step during a linear deployment. Valid values are 3.0 to 100.0. The default value is 10.0. +>>> The percentage of production traffic to shift in each step during a linear deployment. Valid values are multiples of 0.1 from 3.0 to 100.0. The default value is 10.0. @@ -706 +708 @@ JSON Syntax: ->>> The amount of time in minutes to wait between each traffic shifting step during a linear deployment. Valid values are 0 to 1440 minutes (24 hours). The default value is 6. This bake time is not applied after reaching 100% traffic. +>>> The amount of time in minutes to wait between each traffic shifting step during a linear deployment. Valid values are 0 to 1440 minutes (24 hours). The default value is 6. This bake time is not applied after reaching 100 percent traffic. @@ -714 +716 @@ JSON Syntax: ->>> The percentage of production traffic to shift to the new service revision during the canary phase. Valid values are 0.1 to 100.0. The default value is 5.0. +>>> The percentage of production traffic to shift to the new service revision during the canary phase. Valid values are multiples of 0.1 from 0.1 to 100.0. The default value is 5.0. @@ -882 +884 @@ JSON Syntax: ->>> * When you use `create-service` or `update-service` , the The default is `DISABLED` . +>>> * When you use `create-service` or `update-service` , the default is `DISABLED` . @@ -2668,0 +2671,2 @@ service -> (structure) +>>> * `LINEAR` \- A _linear_ deployment strategy (`LINEAR` ) gradually shifts traffic from the current production environment to a new environment in equal percentages over time. With Amazon ECS linear deployments, you can control the pace of traffic shifting and validate new service revisions with increasing amounts of production traffic. +>>> * `CANARY` \- A _canary_ deployment strategy (`CANARY` ) shifts a small percentage of traffic to the new service revision first, then shifts the remaining traffic all at once after a specified time period. This allows you to test the new version with a subset of users before full deployment. @@ -2749 +2753 @@ service -> (structure) ->>>> The percentage of production traffic to shift in each step during a linear deployment. Valid values are 3.0 to 100.0. The default value is 10.0. +>>>> The percentage of production traffic to shift in each step during a linear deployment. Valid values are multiples of 0.1 from 3.0 to 100.0. The default value is 10.0. @@ -2753 +2757 @@ service -> (structure) ->>>> The amount of time in minutes to wait between each traffic shifting step during a linear deployment. Valid values are 0 to 1440 minutes (24 hours). The default value is 6. This bake time is not applied after reaching 100% traffic. +>>>> The amount of time in minutes to wait between each traffic shifting step during a linear deployment. Valid values are 0 to 1440 minutes (24 hours). The default value is 6. This bake time is not applied after reaching 100 percent traffic. @@ -2761 +2765 @@ service -> (structure) ->>>> The percentage of production traffic to shift to the new service revision during the canary phase. Valid values are 0.1 to 100.0. The default value is 5.0. +>>>> The percentage of production traffic to shift to the new service revision during the canary phase. Valid values are multiples of 0.1 from 0.1 to 100.0. The default value is 5.0. @@ -2982 +2986 @@ service -> (structure) ->>>>>> * When you use `create-service` or `update-service` , the The default is `DISABLED` . +>>>>>> * When you use `create-service` or `update-service` , the default is `DISABLED` . @@ -3398 +3402 @@ service -> (structure) ->>>>>> * When you use `create-service` or `update-service` , the The default is `DISABLED` . +>>>>>> * When you use `create-service` or `update-service` , the default is `DISABLED` . @@ -4180 +4184 @@ service -> (structure) ->>>> * When you use `create-service` or `update-service` , the The default is `DISABLED` . +>>>> * When you use `create-service` or `update-service` , the default is `DISABLED` . @@ -4381 +4385 @@ service -> (structure) - * [AWS CLI 2.31.27 Command Reference](../../index.html) » + * [AWS CLI 2.31.28 Command Reference](../../index.html) »