AWS AmazonECS documentation change
Summary
Restructured documentation to emphasize capacity providers over launch types, removed detailed launch type implementation steps, added guidance about task definition compatibility checks during updates, and reorganized best practices sections.
Security assessment
The changes focus on operational best practices and architectural recommendations rather than addressing security vulnerabilities or documenting new security features. While the removed 'security patching and maintenance' line under Fargate launch type might imply security implications, this is part of normal Fargate service documentation rather than a security-specific update. The compatibility check note relates to operational reliability, not security enforcement.
Diff
diff --git a/AmazonECS/latest/developerguide/capacity-launch-type-comparison.md b/AmazonECS/latest/developerguide/capacity-launch-type-comparison.md index 4d81cc101..8193fbe1c 100644 --- a//AmazonECS/latest/developerguide/capacity-launch-type-comparison.md +++ b//AmazonECS/latest/developerguide/capacity-launch-type-comparison.md @@ -5 +5 @@ -Launch typesCapacity providersBest practicesService mutability +Best practices Service mutability @@ -9,103 +9 @@ Launch typesCapacity providersBest practicesService mutability -Amazon ECS provides two methods for configuring capacity for your workloads. You can use launch types or capacity providers. Launch types include EC2, Fargate, and External. Capacity providers offer enhanced flexibility and advanced features for capacity management, including automatic scaling capabilities through Auto Scaling group capacity providers, cost optimization with Fargate and Fargate Spot, and simplified infrastructure management with Amazon ECS Managed Instances. Capacity providers provide better control over resource allocation and can help optimize both performance and costs compared to traditional launch types. Use the following to understand the differences between capacity providers and launch types. - -## Launch types - -Launch types define the infrastructure on which your tasks and services run. When you define tasks, specify `RequiresCompatibilities` to include one or more launch types that are compatible with tasks. - -### EC2 launch type - -Tasks run on Amazon EC2 instances that are managed within the cluster. Responsibilities include: - - * Provisioning and managing Amazon EC2 instances - - * Installing and configuring the Amazon Amazon ECS container agent - - * Scaling the cluster capacity - - * Patching and maintaining the underlying infrastructure - - - - -### Fargate launch type - -Tasks run on AWS-managed infrastructure. AWS handles: - - * Infrastructure provisioning and management - - * Scaling based on task requirements - - * Security patching and maintenance - - * Resource isolation between tasks - - - - -###### Note - -Launch types cannot be used to run tasks on Fargate Spot capacity because Fargate Spot is only available through capacity providers. - -### External launch type - -Tasks run on on-premises servers or virtual machines registered to the cluster using Amazon Amazon ECS Anywhere. - -## Capacity providers - -Capacity providers offer a more flexible and powerful approach to managing compute capacity. - -### Fargate capacity providers - -Fargate capacity providers include the following options: - - * `FARGATE` \- On-demand Fargate capacity - - * `FARGATE_SPOT` \- Spot Fargate capacity for cost optimization - - - - -Fargate is the best choice for the following use cases: - - * Variable or unpredictable workloads - - * True serverless container execution - - * Development and testing environments - - * Rapid scaling without pre-provisioned capacity - - - - -### Amazon ECS Managed Instances - -Amazon ECS Managed Instances combines the flexibility of Amazon EC2 with the simplicity of Fargate. - -Amazon ECS Managed Instances are ideal for the following scenarios: - - * Amazon EC2 flexibility without operational overhead - - * Cost optimization is a priority - - * Automatic scaling and high availability - - * Building new applications or modernizing existing ones - - - - -### Amazon EC2 Auto Scaling group capacity providers - -Custom capacity providers backed by Amazon EC2 Auto Scaling groups for scenarios requiring: - - * Custom AMIs or specialized configurations - - * Specific instance types or hardware features - - * Existing infrastructure investments to leverage - - * Compliance requires specific security configurations - - - +Amazon ECS provides two methods for configuring capacity for workloads. You can use launch types or capacity providers. Launch types include EC2, Fargate, and External. Capacity providers offer enhanced flexibility and advanced features for capacity management. You can run workloads on serverless compute with Fargate and Fargate Spot capacity providers, on self-managed EC2 instances through Auto Scaling group capacity providers, or on fully-managed compute using Amazon ECS Managed Instances capacity providers that combine the simplicity of Fargate with the flexibility of EC2 compute. Capacity providers offer better control over resource allocation and can help optimize both performance and costs. Capacity providers are the recommended way to configure capacity for workloads compared to traditional launch types. Use the following to understand the differences between capacity providers and launch types. @@ -115 +13 @@ Custom capacity providers backed by Amazon EC2 Auto Scaling groups for scenarios -While launch types provide a simple starting point, capacity providers offer the flexibility, optimization, and future-ready architecture that modern containerized applications require. Amazon ECS Managed Instances represents the evolution of container compute, delivering the best of both Amazon EC2 flexibility and Fargate simplicity. +The following are the best practices: @@ -117 +15 @@ While launch types provide a simple starting point, capacity providers offer the -Follow these best practices when migrating to capacity providers: +Use launch types to define infrastructure compatibility @@ -119 +16,0 @@ Follow these best practices when migrating to capacity providers: - * Test task definition compatibility before production migration @@ -121 +18 @@ Follow these best practices when migrating to capacity providers: - * Plan migrations during maintenance windows +Launch types define the infrastructure on which tasks and services run. When you define tasks, specify `RequiresCompatibilities` to include one or more launch types that are compatible with tasks. You can use following launch types: EC2, Fargate, External, and Amazon ECS Managed Instances. While you can also use launch type to run your tasks or services, we recommend using the launch type only for defining compatibilities in your task definitions, and use capacity providers for launching tasks or services. Note that you can choose one or more launch types to define compatibilities for tasks. @@ -123 +20 @@ Follow these best practices when migrating to capacity providers: - * Start with development environments to validate configurations +Use capacity providers to configure compute capacity @@ -125 +21,0 @@ Follow these best practices when migrating to capacity providers: - * Use capacity providers for all new services @@ -126,0 +23 @@ Follow these best practices when migrating to capacity providers: +When you launch tasks or services, configure a capacity provider strategy. Amazon ECS supports following capacity providers: Fargate and FARGATE_SPOT, Auto Scaling groups for self-managed EC2 instances, and Amazon ECS Managed Instances. Note that Spot Fleet is only available as a capacity provider and not as a launch type. You can create one or more Amazon ECS Managed Instances or Auto Scaling groups capacity providers in a cluster. Fargate and Fargate Spot capacity providers are created and managed by Amazon ECS on every cluster and you do not need to create them. A cluster can have a mix of all capacity provider types, however, a capacity provider strategy can't have a mix of different capacity provider types. @@ -127,0 +25 @@ Follow these best practices when migrating to capacity providers: +Update the capacity for services @@ -129,0 +28,2 @@ Follow these best practices when migrating to capacity providers: +You can simply update a capacity provider strategy for a service to move it from one compute type to the other. + @@ -132 +32 @@ Follow these best practices when migrating to capacity providers: -Amazon ECS supports updating services between different capacity providers, allowing for: +Amazon ECS supports updating services between different capacity providers. This allows for: @@ -145 +45,5 @@ The following is a high-level overview of the process: - 1. Update the task definition – Ensure `requiresCompatibilities` includes the target capacity provider. + 1. Update the task definition – Ensure `requiresCompatibilities` includes the target capacity provider, for example` MANAGED_INSTANCES`. + +###### Note + +Task definitions must pass compatibility validation for the target capacity provider. If the `requiresCompatibilities` check fails for the task definition version, the `UpdateService` call fails. @@ -149 +53 @@ The following is a high-level overview of the process: - 3. Update the service – Modify the service to use a capacity provider strategy. + 3. Update the service – Modify the service to use a capacity provider strategy instead of the launch type. @@ -158,5 +62 @@ The following is a high-level overview of the process: -### Supported update paths - -The following explains the upgrade paths. - -#### Capacity provider to capacity provider +### Capacity provider to capacity provider @@ -164 +64 @@ The following explains the upgrade paths. -All capacity provider to capacity provider migrations are supported: +All capacity provider to capacity provider updates are supported: @@ -181 +81 @@ All capacity provider to capacity provider migrations are supported: -#### Launch type to capacity provider +### Launch type to capacity provider @@ -183 +83 @@ All capacity provider to capacity provider migrations are supported: -All launch type to capacity provider migrations are supported: +All launch type to capacity provider updates are supported: @@ -191 +91 @@ All launch type to capacity provider migrations are supported: - * EC2 launch type to EC2; Auto Scaling group capacity provider + * EC2 launch type to EC2 Auto Scaling group capacity provider @@ -206 +106 @@ All launch type to capacity provider migrations are supported: -#### Launch type to launch type +### Launch type to launch type @@ -208 +108 @@ All launch type to capacity provider migrations are supported: -Launch type to launch type migrations are not supported: +Launch type to launch type updates are not supported: