AWS AmazonECS documentation change
Summary
Replaced 'ELB' abbreviation with full 'Elastic Load Balancing' service name throughout the document for consistency and clarity
Security assessment
The changes are purely terminological updates without introducing new security concepts. The text about service quotas preventing malicious actions remains unchanged, indicating no new security implications. No vulnerabilities or security incidents are referenced.
Diff
diff --git a/AmazonECS/latest/developerguide/operating-at-scale-service-quotas-best-practice.md b/AmazonECS/latest/developerguide/operating-at-scale-service-quotas-best-practice.md index 3d90cec6f..c0e1c64f5 100644 --- a//AmazonECS/latest/developerguide/operating-at-scale-service-quotas-best-practice.md +++ b//AmazonECS/latest/developerguide/operating-at-scale-service-quotas-best-practice.md @@ -5 +5 @@ -ELBElastic network interfacesAWS Cloud Map +Elastic Load BalancingElastic network interfacesAWS Cloud Map @@ -9 +9 @@ ELBElastic network interfacesAWS Cloud Map -Amazon ECS integrates 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 discovery, 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 integrates 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 discovery, 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. @@ -26 +26 @@ In addition to considering Amazon ECS service quota when scaling your workloads, -## ELB +## Elastic Load Balancing @@ -28 +28 @@ In addition to considering Amazon ECS service quota when scaling your workloads, -You can configure your Amazon ECS services to use ELB to distribute traffic evenly across the tasks. For more information about how to choose a load balancer, see [Use load balancing to distribute Amazon ECS service traffic](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html). +You can configure your Amazon ECS services to use Elastic Load Balancing to distribute traffic evenly across the tasks. For more information about how to choose a load balancer, see [Use load balancing to distribute Amazon ECS service traffic](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html). @@ -30 +30 @@ You can configure your Amazon ECS services to use ELB to distribute traffic even -### ELB service quotas +### Elastic Load Balancing service quotas @@ -32 +32 @@ You can configure your Amazon ECS services to use ELB to distribute traffic even -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. +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. @@ -51 +51 @@ There are stricter limitations on the number of targets you can register with a -### ELB API throttling +### Elastic Load Balancing 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 ELB API operations on your behalf. If you have a large number of services configured with load balancers in your account, you might experience 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. +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 experience 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. @@ -59 +59 @@ If you experience AWS Cloud Map API throttling, you can contact Support for guid -When 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. +When 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.