AWS AmazonECS documentation change
Summary
Updated terminology from 'EC2 launch type' to 'EC2' and 'Fargate launch type' to 'Fargate' in multiple sections. Minor phrasing improvements for consistency.
Security assessment
Changes are terminology updates and phrasing improvements without any security context. No vulnerabilities, mitigations, or security features are mentioned.
Diff
diff --git a/AmazonECS/latest/developerguide/service-event-messages-list.md b/AmazonECS/latest/developerguide/service-event-messages-list.md index c897f62ec..7f7f00e01 100644 --- a//AmazonECS/latest/developerguide/service-event-messages-list.md +++ b//AmazonECS/latest/developerguide/service-event-messages-list.md @@ -21 +21 @@ The service scheduler sends this event message when it couldn't find the availab -Use capacity providers to automatically scale your EC2 instances. For more information, see [Amazon ECS capacity providers for the EC2 launch type ](./asg-capacity-providers.html). +Use capacity providers to automatically scale your EC2 instances. For more information, see [Amazon ECS capacity providers for EC2 workloads](./asg-capacity-providers.html). @@ -88 +88 @@ Some task definition parameters require a specific Docker remote API version to -A common cause of this error is if your service is using tasks that use the `awsvpc` network mode and the EC2 launch type. The cluster you specified doesn't have a container instance registered to it in the same subnet that was specified in the `awsvpcConfiguration` when the service was created. +A common cause of this error is if your service is using tasks that use the `awsvpc` network mode and EC2. The cluster you specified doesn't have a container instance registered to it in the same subnet that was specified in the `awsvpcConfiguration` when the service was created. @@ -92 +92 @@ You can use the AWSSupport-TroubleshootECSContainerInstance runbook to troublesh -For more information on which attributes are required for specific task definition parameters and agent configuration variables, see [Amazon ECS task definition parameters for the Fargate launch type](./task_definition_parameters.html) and [Amazon ECS container agent configuration](./ecs-agent-config.html). +For more information on which attributes are required for specific task definition parameters and agent configuration variables, see [Amazon ECS task definition parameters for Fargate](./task_definition_parameters.html) and [Amazon ECS container agent configuration](./ecs-agent-config.html). @@ -165 +165 @@ AWS Fargate is transitioning from task count-based quotas to vCPU-based quotas. -You can request a quota increase for the Fargate vCPU-based quota. For more information, see [Amazon ECS service quotas](./service-quotas.html). To request a Fargate quota increase, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_. +You can request a quota increase for Fargate vCPU-based quota. For more information, see [Amazon ECS service quotas](./service-quotas.html). To request a Fargate quota increase, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the _Service Quotas User Guide_. @@ -189 +189 @@ Use `describe-services` to verify that you have a capacity provider associated w -Verify that there is available capacity in the capacity provider, In the case of the EC2 launch type, make sure that the container instances meet the task definition requirements. +Verify that there is available capacity in the capacity provider, In the case of EC2, make sure that the container instances meet the task definition requirements. @@ -248 +248 @@ Some task definition parameters require a specific Docker remote API version to -A common cause of this error is if your service is using tasks that use the `awsvpc` network mode and the EC2 launch type and the cluster you specified doesn't have a container instance registered to it in the same subnet that was specified in the `awsvpcConfiguration` when the service was created. +A common cause of this error is if your service is using tasks that use the `awsvpc` network mode and EC2 and the cluster you specified doesn't have a container instance registered to it in the same subnet that was specified in the `awsvpcConfiguration` when the service was created. @@ -252 +252 @@ You can use the AWSSupport-TroubleshootECSContainerInstance runbook to troublesh -For more information on which attributes are required for specific task definition parameters and agent configuration variables, see [Amazon ECS task definition parameters for the Fargate launch type](./task_definition_parameters.html) and [Amazon ECS container agent configuration](./ecs-agent-config.html). +For more information on which attributes are required for specific task definition parameters and agent configuration variables, see [Amazon ECS task definition parameters for Fargate](./task_definition_parameters.html) and [Amazon ECS container agent configuration](./ecs-agent-config.html).