New AWS ECS Gateway Enables Shared Load Balancing

The service allows up to 25 containerized services to utilize one load balancer, simplifying infrastructure management.

Updated on Oct. 20, 2026 in Data Centers

Bold flat-color editorial illustration featuring a central geometric volume connected to smaller surrounding blocks, depicting infrastructure consolidation.
Amazon Web Services launched the Amazon ECS Gateway, allowing multiple services to share a single load balancer to streamline infrastructure management. AI Illustration. Upload story photo >

Live Poll

Do you trust new automated cloud management tools to improve your development workflow?

Amazon Web Services has launched Amazon ECS Gateway, a new tool designed to allow multiple services within the Amazon Elastic Container Service to share a single Application Load Balancer. The service is now generally available across all commercial AWS regions at no additional charge.

Why it matters

This release simplifies infrastructure management for platform teams by reducing the deployment overhead associated with individual load balancers. By enabling shared resources, organizations can minimize configuration drift and streamline scaling across their containerized environments.

The ECS Gateway allows up to 25 services to share one Application Load Balancer, with support for up to 10,000 clusters per gateway and a default quota of 10 for maxAlbCount. Each cluster supports up to five gateway associations, compatible with Amazon ECS EC2, AWS Fargate, and ECS Managed Instances.

The players

Amazon Web Services

A subsidiary of Amazon providing a broad cloud computing platform that includes compute, storage, and networking services.

Amazon Elastic Container Service

A highly scalable, high-performance container orchestration service that supports Docker containers and allows users to run applications on a managed cluster.

The details

Platform teams initiate the process by creating a gateway and configuring core network parameters, including subnets, security groups, Transport Layer Security (TLS) certificates — cryptographic keys that secure internet communications — and listener settings. Application teams then integrate their services by adding a specific gateway connector parameter during the service creation or update workflow. This abstraction layer enables centralized management of shared infrastructure components, decoupling the load balancing configuration from individual service definitions.

Timeline

  1. October 20, 2026: Amazon Web Services launched Amazon ECS Gateway.

The Tech Race

This development marks a departure from the traditional one-to-one model of provisioning an Amazon Application Load Balancer for every individual container service. It follows a broader industry trend toward reducing operational complexity in cloud infrastructure through abstracted resource sharing.

Platform engineers can immediately begin consolidating their load balancer configurations across existing Amazon ECS EC2, AWS Fargate, and managed instance deployments. Because the service is available at no extra cost in all commercial regions, teams can migrate to this shared model without immediate budget adjustments.

The takeaway

The move toward shared gateways signals a push to curb the rising costs and management overhead of high-density microservices architectures. Teams should audit their current load balancer utilization to identify opportunities to consolidate under the new 25-service limit per gateway.

Further reading

For more information on optimizing your cloud infrastructure, visit our Data Centers section.

Live Poll

Do you trust new automated cloud management tools to improve your development workflow?