AWS AmazonECS documentation change
Summary
Restructured cluster documentation to emphasize infrastructure type selection, added detailed sections about Amazon ECS Managed Instances, and clarified capacity provider types
Security assessment
The changes introduce documentation about Amazon ECS Managed Instances' security benefits including 'managed patching and security updates', which improves security posture through automated maintenance. However, there is no evidence this addresses a specific existing security vulnerability.
Diff
diff --git a/AmazonECS/latest/developerguide/clusters.md b/AmazonECS/latest/developerguide/clusters.md index ba028ad02..3f018b7eb 100644 --- a//AmazonECS/latest/developerguide/clusters.md +++ b//AmazonECS/latest/developerguide/clusters.md @@ -5 +5 @@ -Capacity providers +Choosing the right cluster typeCluster componentsCluster conceptsCapacity providers @@ -9 +9 @@ Capacity providers -An Amazon ECS cluster is a logical grouping of tasks or services. In addition to tasks and services, a cluster consists of the following resources: +An Amazon ECS cluster is a logical grouping of tasks or services that provides the infrastructure capacity for your containerized applications. When creating a cluster, you choose from the three primary infrastructure types, each optimized for different use cases and operational requirements. @@ -11 +11 @@ An Amazon ECS cluster is a logical grouping of tasks or services. In addition to - * The infrastructure capacity which can be a combination of the following: +## Choosing the right cluster type @@ -13 +13 @@ An Amazon ECS cluster is a logical grouping of tasks or services. In addition to - * Amazon EC2 instances in the AWS cloud +Amazon ECS offers three infrastructure types for your clusters. Choose the type that best matches your workload requirements, operational preferences, and cost optimization goals: @@ -15 +15 @@ An Amazon ECS cluster is a logical grouping of tasks or services. In addition to - * Serverless (AWS Fargate) in the AWS cloud +Amazon ECS Managed Instances (Recommended) @@ -17 +17,59 @@ An Amazon ECS cluster is a logical grouping of tasks or services. In addition to - * On-premises virtual machines (VM) or servers + +**Best for most workloads** \- AWS fully manages the underlying Amazon EC2 instances, including provisioning, patching, and scaling. This option provides the optimal balance of performance, cost-effectiveness, and operational simplicity. + +**Use when:** + + * You want AWS to handle infrastructure management + + * You need cost-effective compute with automatic optimization + + * You want to focus on your applications rather than infrastructure + + * You need predictable performance with flexible scaling + + + + +Fargate + + +**Serverless compute** \- Pay only for the resources your tasks use without managing any infrastructure. Ideal for variable workloads and getting started quickly. + +**Use when:** + + * You want completely serverless operations + + * You have unpredictable or variable workloads + + * You want to minimize operational overhead + + * You need rapid deployment and scaling + + + + +Amazon EC2 instances + + +**Full control** \- You manage the underlying Amazon EC2 instances directly, including instance selection, configuration, and maintenance. + +**Use when:** + + * You need specific instance types or configurations + + * You have existing Amazon EC2 infrastructure to leverage + + * You require custom AMIs or specialized software + + * You need maximum control over the underlying infrastructure + + + + +###### Note + +Amazon ECS Managed Instances is the recommended choice for most new workloads as it provides the best combination of performance, cost optimization, and operational simplicity while allowing AWS to handle infrastructure management tasks. + +## Cluster components + +In addition to the infrastructure capacity, a cluster consists of the following resources: @@ -21 +79 @@ An Amazon ECS cluster is a logical grouping of tasks or services. In addition to -When you use Amazon EC2 instances for the capacity, the subnet can be in Availability Zones, Local Zones, Wavelength Zones or AWS Outposts. +When you use Amazon ECS Managed Instances or Amazon EC2 instances for the capacity, the subnet can be in Availability Zones, Local Zones, Wavelength Zones, or AWS Outposts. @@ -25 +83 @@ When you use Amazon EC2 instances for the capacity, the subnet can be in Availab -The namespace is used for service-to-service communication with Service Connect. +A namespace is used for service-to-service communication with Service Connect. @@ -33,0 +92,2 @@ CloudWatch Container Insights comes at an additional cost and is a fully managed +## Cluster concepts + @@ -67 +127,5 @@ The cluster has been deleted. Clusters with an `INACTIVE` status may remain disc - * You can use different instance types for the EC2 launch type or Auto Scaling group capacity providers. An instance can only be registered to one cluster at a time. + * A cluster can contain a mix of tasks that are hosted on Amazon ECS Managed Instances, AWS Fargate, Amazon EC2 instances, or external instances. Tasks can run on Amazon ECS Managed Instances, Fargate or EC2 infrastructure as a launch type or a capacity provider strategy. If you use EC2 capacity providers, Amazon ECS doesn't track and scale the capacity of Amazon EC2 Auto Scaling groups. + + * A cluster can contain a mix of Amazon ECS Managed Instances capacity providers, Auto Scaling group capacity providers, and Fargate capacity providers. A capacity provider strategy can only contain Amazon ECS Managed Instances capacity providers, Auto Scaling group capacity providers, or Fargate capacity providers. + + * You can use different instance types for the Amazon ECS Managed Instances and EC2, or Auto Scaling group capacity providers. An instance can only be registered to one cluster at a time. @@ -82 +146,19 @@ Amazon ECS capacity providers manage the scaling of infrastructure for tasks in -For Fargate, you do not need to create or manage the capacity. You just need to associate any of the following pre-defined capacity providers with the cluster: +Amazon ECS offers three types of capacity providers for your clusters: + +Amazon ECS Managed Instances capacity providers + + +AWS fully manages the underlying Amazon EC2 instances, including provisioning, patching, scaling, and lifecycle management. This provides the optimal balance of performance, cost-effectiveness, and operational simplicity. Amazon ECS Managed Instances capacity providers automatically optimize instance selection and scaling based on your workload requirements. + +With Amazon ECS Managed Instances, you benefit from: + + * Automatic instance provisioning and scaling + + * Managed patching and security updates + + * Cost optimization through intelligent instance selection + + * Reduced operational overhead + + + @@ -84 +166 @@ For Fargate, you do not need to create or manage the capacity. You just need to - * Fargate +Fargate capacity providers @@ -86 +167,0 @@ For Fargate, you do not need to create or manage the capacity. You just need to - * Fargate Spot @@ -87,0 +169 @@ For Fargate, you do not need to create or manage the capacity. You just need to +Serverless compute where you pay only for the resources your tasks use without managing any infrastructure. You just need to associate the pre-defined capacity providers (Fargate and Fargate Spot) with the cluster. @@ -88,0 +171 @@ For Fargate, you do not need to create or manage the capacity. You just need to +Auto Scaling group capacity providers @@ -91 +174 @@ For Fargate, you do not need to create or manage the capacity. You just need to -When you use EC2 instances for your capacity, you use Auto Scaling group to manage the EC2 instances. Auto Scaling helps ensure that you have the correct number of EC2 instances available to handle the application load. +When you use Amazon EC2 instances for your capacity, you use Auto Scaling group to manage the Amazon EC2 instances. Auto Scaling helps ensure that you have the correct number of Amazon EC2 instances available to handle the application load. You have full control over the underlying infrastructure. @@ -93 +176 @@ When you use EC2 instances for your capacity, you use Auto Scaling group to mana -A cluster can contain a mix of tasks that are hosted on AWS Fargate, Amazon EC2 instances, or external instances. Tasks can run on Fargate or EC2 infrastructure as a launch type or a capacity provider strategy. If you use EC2 as a launch type, Amazon ECS doesn't track and scale the capacity of Amazon EC2 Auto Scaling groups. For more information about launch types, see [Amazon ECS launch types](./launch_types.html). +A cluster can contain a mix of tasks that are hosted on Amazon ECS Managed Instances, AWS Fargate, Amazon EC2 instances, or external instances. Tasks can run on Amazon ECS Managed Instances, Fargate or EC2 infrastructure as a launch type or a capacity provider strategy. If you use EC2 as a launch type, Amazon ECS doesn't track and scale the capacity of Amazon EC2 Auto Scaling groups. @@ -95 +178 @@ A cluster can contain a mix of tasks that are hosted on AWS Fargate, Amazon EC2 -A cluster can contain a mix of both Auto Scaling group capacity providers and Fargate capacity providers. A capacity provider strategy can only contain Auto Scaling group capacity providers or Fargate capacity providers. +A cluster can contain a mix of Amazon ECS Managed Instances capacity providers, Auto Scaling group capacity providers, and Fargate capacity providers. A capacity provider strategy can only contain Amazon ECS Managed Instances capacity providers, Auto Scaling group capacity providers, or Fargate capacity providers. @@ -105 +188 @@ Example task definitions -Clusters for Fargate +Clusters for Amazon ECS Managed Instances