AWS AmazonECS documentation change
Summary
Updated terminology from 'launch type' to 'capacity' and 'Amazon EC2', removed references to launch type validation, simplified logging driver documentation, and adjusted EC2 capacity provider references.
Security assessment
The changes primarily update terminology (e.g., 'launch types' to 'capacity') and remove redundant information about logging drivers. There is no evidence of security vulnerability fixes, security feature additions, or security-related configuration changes. The modifications appear to be documentation restructuring and terminology alignment rather than security-focused updates.
Diff
diff --git a/AmazonECS/latest/developerguide/task_definition_parameters_ec2.md b/AmazonECS/latest/developerguide/task_definition_parameters_ec2.md index 52f4f97a7..cd421baa0 100644 --- a//AmazonECS/latest/developerguide/task_definition_parameters_ec2.md +++ b//AmazonECS/latest/developerguide/task_definition_parameters_ec2.md @@ -5 +5 @@ -FamilyLaunch typesTask roleTask execution roleNetwork modeRuntime platformTask sizeContainer definitionsElastic Inference accelerator nameTask placement constraintsProxy configurationVolumesTagsOther task definition parameters +FamilyCapacityTask roleTask execution roleNetwork modeRuntime platformTask sizeContainer definitionsElastic Inference accelerator nameTask placement constraintsProxy configurationVolumesTagsOther task definition parameters @@ -7 +7 @@ FamilyLaunch typesTask roleTask execution roleNetwork modeRuntime platformTask s -# Amazon ECS task definition parameters for the EC2 launch type +# Amazon ECS task definition parameters for Amazon EC2 @@ -9 +9 @@ FamilyLaunch typesTask roleTask execution roleNetwork modeRuntime platformTask s -Task definitions are split into separate parts: the task family, the AWS Identity and Access Management (IAM) task role, the network mode, container definitions, volumes, task placement constraints, and launch types. The family and container definitions are required in a task definition. In contrast, task role, network mode, volumes, task placement constraints, and launch type are optional. +Task definitions are split into separate parts: the task family, the AWS Identity and Access Management (IAM) task role, the network mode, container definitions, volumes, task placement constraints, and capacity. The family and container definitions are required in a task definition. In contrast, task role, network mode, volumes, task placement constraints, and launch type are optional. @@ -13 +13 @@ You can use these parameters in a JSON file to configure your task definition. -The following are more detailed descriptions for each task definition parameter for the EC2 launch type. +The following are more detailed descriptions for each task definition parameter for Amazon EC2 @@ -26 +26 @@ When you register a task definition, you give it a family, which is similar to a -## Launch types +## Capacity @@ -28 +28 @@ When you register a task definition, you give it a family, which is similar to a -When you register a task definition, you can specify a launch type that Amazon ECS should validate the task definition against. If the task definition doesn't validate against the compatibilities specified, a client exception is returned. For more information, see [Amazon ECS launch types](./launch_types.html). +When you register a task definition, you can specify the capacity that Amazon ECS should validate the task definition against. If the task definition doesn't validate against the compatibilities specified, a client exception is returned. @@ -41 +41 @@ Valid Values: `EC2` -The launch type to validate the task definition against. This initiates a check to ensure that all of the parameters that are used in the task definition meet the requirements of the launch type. +The capacity to validate the task definition against. This initiates a check to ensure that all of the parameters that are used in the task definition meet the requirements of Amazon EC2. @@ -92 +92 @@ When running tasks that use the `host` network mode, do not run containers using -If the network mode is `awsvpc`, the task is allocated an elastic network interface, and you must specify a `NetworkConfiguration` when you create a service or run a task with the task definition. For more information, see [Amazon ECS task networking options for the EC2 launch type](./task-networking.html). +If the network mode is `awsvpc`, the task is allocated an elastic network interface, and you must specify a `NetworkConfiguration` when you create a service or run a task with the task definition. For more information, see [Amazon ECS task networking options for EC2](./task-networking.html). @@ -362 +362 @@ For tasks that use the `awsvpc` network mode, you use `containerPort` to specify -Suppose that you're using containers in a task with the EC2 launch type and you specify a container port and not a host port. Then, your container automatically receives a host port in the ephemeral port range. For more information, see `hostPort`. Port mappings that are automatically assigned in this way don't count toward the 100 reserved ports quota of a container instance. +Suppose that you're using containers in a task with the EC2 capacity providers and you specify a container port and not a host port. Then, your container automatically receives a host port in the ephemeral port range. For more information, see `hostPort`. Port mappings that are automatically assigned in this way don't count toward the 100 reserved ports quota of a container instance. @@ -1107 +1107 @@ Consider the following when specifying a log configuration for your containers: - * Amazon ECS supports a subset of the logging drivers that are available to the Docker daemon. Additional log drivers might be available in future releases of the Amazon ECS container agent. + * Amazon ECS supports a subset of the logging drivers that are available to the Docker daemon. @@ -1989 +1989 @@ The configuration details for the App Mesh proxy. -For tasks that use the EC2 launch type, the container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the `ecs-init` package to enable a proxy configuration. If your container instances are launched from the Amazon ECS-optimized AMI version `20190301` or later, then they contain the required versions of the container agent and `ecs-init`. For more information, see [Amazon ECS-optimized Linux AMIs](./ecs-optimized_AMI.html). +For tasks that use EC2, the container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the `ecs-init` package to enable a proxy configuration. If your container instances are launched from the Amazon ECS-optimized AMI version `20190301` or later, then they contain the required versions of the container agent and `ecs-init`. For more information, see [Amazon ECS-optimized Linux AMIs](./ecs-optimized_AMI.html). @@ -2440 +2440 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Task definition parameters for the Fargate launch type +Task definition parameters for Fargate