AWS AmazonECS documentation change
Summary
Updated terminology from 'Elastic Load Balancing' to 'ELB' throughout the document and clarified references to 'Amazon EC2 Auto Scaling group capacity provider' instead of generic 'Auto Scaling group capacity provider'.
Security assessment
The changes are purely terminological updates (branding consistency) and clarifications about capacity providers. No security vulnerabilities, weaknesses, or incidents are mentioned. The existing text about quotas protecting against 'malicious actions that might increase your bill' remains unchanged and wasn't added by this diff.
Diff
diff --git a/AmazonECS/latest/developerguide/operating-at-scale-service-quotas.md b/AmazonECS/latest/developerguide/operating-at-scale-service-quotas.md index 0c4918b4c..58f8bba81 100644 --- a//AmazonECS/latest/developerguide/operating-at-scale-service-quotas.md +++ b//AmazonECS/latest/developerguide/operating-at-scale-service-quotas.md @@ -5 +5 @@ -Elastic Load BalancingElastic network interfacesAWS Cloud Map +ELBElastic network interfacesAWS Cloud Map @@ -9 +9 @@ Elastic Load BalancingElastic network interfacesAWS Cloud Map -Amazon ECS is integrated with several AWS services, including Elastic Load Balancing, AWS Cloud Map, and Amazon EC2. With this tight integration, Amazon ECS includes several features such as service load balancing, Service Connect, task networking, and cluster auto scaling. Amazon ECS and the other AWS services that it integrates with all maintain service quotas and API rate limits to ensure consistent performance and utilization. These service quotas also prevent the accidental provisioning of more resources than needed and protect against malicious actions that might increase your bill. +Amazon ECS is integrated with several AWS services, including ELB, AWS Cloud Map, and Amazon EC2. With this tight integration, Amazon ECS includes several features such as service load balancing, Service Connect, task networking, and cluster auto scaling. Amazon ECS and the other AWS services that it integrates with all maintain service quotas and API rate limits to ensure consistent performance and utilization. These service quotas also prevent the accidental provisioning of more resources than needed and protect against malicious actions that might increase your bill. @@ -17 +17 @@ When scaling your workloads on Amazon ECS, we recommend that you consider the fo - * For tasks that run on Amazon EC2 instances, the maximum number of Amazon EC2 instances that you can register for each cluster is 5,000. If you use Amazon ECS cluster auto scaling with an Auto Scaling group capacity provider, or if you manage Amazon EC2 instances for your cluster on your own, this quota might become a deployment bottleneck. If you require more capacity, you can create more clusters or request a service quota increase. + * For tasks that run on Amazon EC2 instances, the maximum number of Amazon EC2 instances that you can register for each cluster is 5,000. If you use Amazon ECS cluster auto scaling with an Amazon EC2 Auto Scaling group capacity provider, or if you manage Amazon EC2 instances for your cluster on your own, this quota might become a deployment bottleneck. If you require more capacity, you can create more clusters or request a service quota increase. @@ -19 +19 @@ When scaling your workloads on Amazon ECS, we recommend that you consider the fo - * If you use Amazon ECS cluster auto scaling with an Auto Scaling group capacity provider, when scaling your services consider the `Tasks in the PROVISIONING state per cluster` quota. This quota is the maximum number of tasks in the `PROVISIONING` state for each cluster for which capacity providers can increase capacity. When you launch a large number of tasks all at the same time, you can easily meet this quota. One example is if you simultaneously deploy tens of services, each with hundreds of tasks. When this happens, the capacity provider needs to launch new container instances to place the tasks when the cluster has insufficient capacity. While the capacity provider is launching additional Amazon EC2 instances, the Amazon ECS service scheduler likely will continue to launch tasks in parallel. However, this activity might be throttled because of insufficient cluster capacity. The Amazon ECS service scheduler implements a back-off and exponential throttling strategy for retrying task placement as new container instances are launched. As a result, you might experience slower deployment or scale-out times. To avoid this situation, you can plan your service deployments in one of the following ones. Either deploy a large number of tasks don't require increasing cluster capacity, or keep spare cluster capacity for new task launches. + * If you use Amazon ECS cluster auto scaling with an Amazon EC2 Auto Scaling group capacity provider, when scaling your services consider the `Tasks in the PROVISIONING state per cluster` quota. This quota is the maximum number of tasks in the `PROVISIONING` state for each cluster for which capacity providers can increase capacity. When you launch a large number of tasks all at the same time, you can easily meet this quota. One example is if you simultaneously deploy tens of services, each with hundreds of tasks. When this happens, the capacity provider needs to launch new container instances to place the tasks when the cluster has insufficient capacity. While the capacity provider is launching additional Amazon EC2 instances, the Amazon ECS service scheduler likely will continue to launch tasks in parallel. However, this activity might be throttled because of insufficient cluster capacity. The Amazon ECS service scheduler implements a back-off and exponential throttling strategy for retrying task placement as new container instances are launched. As a result, you might experience slower deployment or scale-out times. To avoid this situation, you can plan your service deployments in one of the following ones. Either deploy a large number of tasks don't require increasing cluster capacity, or keep spare cluster capacity for new task launches. @@ -26 +26 @@ In addition to considering Amazon ECS service quota when scaling your workloads, -## Elastic Load Balancing +## ELB @@ -28 +28 @@ In addition to considering Amazon ECS service quota when scaling your workloads, -You can configure your Amazon ECS services to use Elastic Load Balancing to distribute traffic evenly across the tasks. For more information and recommended best practices for how to choose a load balancer, see [Use load balancing to distribute Amazon ECS service traffic](./service-load-balancing.html). +You can configure your Amazon ECS services to use ELB to distribute traffic evenly across the tasks. For more information and recommended best practices for how to choose a load balancer, see [Use load balancing to distribute Amazon ECS service traffic](./service-load-balancing.html). @@ -30 +30 @@ You can configure your Amazon ECS services to use Elastic Load Balancing to dist -### Elastic Load Balancing service quotas +### ELB service quotas @@ -32 +32 @@ You can configure your Amazon ECS services to use Elastic Load Balancing to dist -When you scale your workloads, consider the following Elastic Load Balancing service quotas. Most Elastic Load Balancing service quotas are adjustable, and you can request an increase in the Service Quotas console. +When you scale your workloads, consider the following ELB service quotas. Most ELB service quotas are adjustable, and you can request an increase in the Service Quotas console. @@ -51 +51 @@ There are stricter limitations on the number of targets you can register with a -### Elastic Load Balancing API throttling +### ELB API throttling @@ -53 +53 @@ There are stricter limitations on the number of targets you can register with a -When you configure an Amazon ECS service to use a load balancer, the target group health checks must pass before the service is considered healthy. For performing these health checks, Amazon ECS invokes Elastic Load Balancing API operations on your behalf. If you have a large number of services configured with load balancers in your account, you might slower service deployments because of potential throttling specifically for the `RegisterTarget`, `DeregisterTarget`, and `DescribeTargetHealth` Elastic Load Balancing API operations. When throttling occurs, throttling errors occur in your Amazon ECS service event messages. +When you configure an Amazon ECS service to use a load balancer, the target group health checks must pass before the service is considered healthy. For performing these health checks, Amazon ECS invokes ELB API operations on your behalf. If you have a large number of services configured with load balancers in your account, you might slower service deployments because of potential throttling specifically for the `RegisterTarget`, `DeregisterTarget`, and `DescribeTargetHealth` ELB API operations. When throttling occurs, throttling errors occur in your Amazon ECS service event messages. @@ -59 +59 @@ If you experience AWS Cloud Map API throttling, you can contact Support for guid -With your tasks use the `awsvpc` network mode, Amazon ECS provisions a unique elastic network interface (ENI) for each task. When your Amazon ECS services use an Elastic Load Balancing load balancer, these network interfaces are also registered as targets to the appropriate target group defined in the service. +With your tasks use the `awsvpc` network mode, Amazon ECS provisions a unique elastic network interface (ENI) for each task. When your Amazon ECS services use an ELB load balancer, these network interfaces are also registered as targets to the appropriate target group defined in the service.