← All PostsAmazon ECS Gateway: Managed Ingress for ECS Services
AWSECSCloud

Amazon ECS Gateway: Managed Ingress for ECS Services

November 7, 2026

Amazon ECS Gateway is an account-level ingress resource that builds and manages the Application Load Balancer, certificate and security groups for your ECS services, so each team stops wiring them by hand. AWS announced it on October 20, and it costs nothing beyond the resources it provisions. It's a good fit for platform teams that want one set of networking rules, but its limits matter: HTTPS on 443 only, and no documented way to use your own domain.

Key Takeaways

  • A platform team defines a gateway once. App teams opt in by adding a gateway connector to a service.
  • Under the hood it's ALBs with host-based routing, up to 25 services per ALB.
  • Each service gets a generated HTTPS hostname. Custom domains aren't covered in the announcement or the docs.
  • It supports HTTPS on port 443, awsvpc networking and the EC2, Fargate and Managed Instances launch types. Express Mode services can't use it.
  • ECS doesn't repair resources you change outside it, and it doesn't consolidate half-empty ALBs.

What problem does ECS Gateway solve?

Without it, every new ECS service needs an ALB, an ACM certificate, a WAF web ACL and security groups, and someone has to keep them in sync as things change. The AWS announcement says that slows deployments and causes configuration drift.

The gateway moves that work to one place. Platform teams set subnets, security groups, TLS settings, listener settings and WAF once. Application teams just say which port to expose.

How does ECS Gateway work?

The ECS docs break it into four pieces:

  • Gateway: the Region-level resource that holds the ingress configuration.
  • Gateway-cluster association: links a gateway to a cluster. It's many-to-many, with up to five gateways per cluster.
  • Gateway connector: a setting on the service that opts it in. It names the container port and can include an access-type filter and a health check.
  • Gateway route: the record of one service connected to one gateway, created and deleted by ECS.

Nothing is provisioned until the first service connects. Then ECS creates what that service needs: a certificate, a DNS hostname, a listener rule, a target group and a service security group that only accepts traffic from the load balancer. Shared pieces like the ALB and listener are reused across services.

How do I set it up?

The AWS CLI has three steps, per the AWS post and a hands-on test by Classmethod:

  • Create an IAM role that ECS can assume to build networking resources, and attach the managed gateway infrastructure policy.
  • Run aws ecs create-gateway with a name, that role's ARN and a configuration, then aws ecs associate-gateway-with-cluster to link it to a cluster.
  • Create or update a service with the --gateway-connectors parameter, which sets the named port, an access-type filter such as PUBLIC or PRIVATE, and a health check.

The AWS post's service example leaves the health check as a placeholder, so check the API reference for the full shape before copying anything. The task definition needs a named port mapping for the connector to reference.

You can also use the console, SDKs or CloudFormation, and existing services with their own load balancers can add a connector through UpdateService, so adoption can be gradual.

What did the hands-on test show?

Classmethod ran it in Tokyo with one public and one private gateway, each fronting an nginx service on Fargate. A few details from that write-up are worth knowing:

  • Creating the gateways made no ALB. The load balancers appeared about 12 seconds after the services were created.
  • Endpoints look like sv-<random ID>.ecs.<region>.on.aws, so recreating a service with the same name gives a new URL.
  • DNS returned A records directly, not a CNAME, with a 60-second TTL.
  • Deletion protection was on by default even though the author hadn't set it, and deleting a gateway meant waiting for it to reach UPDATE_COMPLETE.
  • Leaving out the access-type filter lets a service connect to any compatible gateway in its VPC, including one added later.

What are the limits?

Several matter for production:

  • Only HTTPS on port 443 is supported, for hostname-based web apps and APIs. Services must use awsvpc networking.
  • The gateway and service must be in the same account and VPC, and the gateway must cover every AZ the service uses.
  • A service gets one connector and can't pick a gateway by name.
  • Name, scheme, subnets, IP address type and listener port and protocol can't change after creation. Changing them means a new gateway and moving services.
  • The default maxAlbCount is 10. If it's reached and no ALB has room, the deployment fails. The docs list 200 load balancers per gateway as the ceiling.
  • Express Mode services aren't supported.

Can I use my own domain?

That's the big open question. InfoQ's write-up says custom domains, Route 53 and CNAME records aren't covered in the announcement or the docs. Commenters pointed out that routing relies on the generated hostname, so a plain CNAME wouldn't work, and a CloudFront setup in front was floated but not settled.

Until AWS documents a path, plan around the generated hostname, or keep your own ALB for anything that needs a branded domain.

What are the operational risks?

Two caveats from the docs and InfoQ. ECS doesn't repair resources modified or deleted outside it, which can break traffic and make later deployments or cleanup fail. And ALBs aren't consolidated when services leave, so partly filled ones can linger, and each one is billed.

Reaction to the launch was mixed. Some commenters saw it as little more than an ALB and DNS wrapper that a CDK construct could replace, while others liked letting a platform team set networking once, as long as it doesn't take too much control away.

Wrapping Up

ECS Gateway is worth trying if you run many similar HTTPS services on ECS and your platform team wants a single place to enforce ingress rules. Test it with one non-critical service first, and check the custom domain and cost questions before you move anything that matters.

Sources

Frequently Asked Questions

What is Amazon ECS Gateway?

An account-level ingress resource for Amazon ECS. Platform teams define networking once, and ECS provisions the ALB, certificate, listener rules and security groups for each connected service.

Does ECS Gateway cost extra?

No separate charge. You pay for what it provisions in your account, such as Application Load Balancers, CloudWatch logs and metrics, ACM certificates and data transfer.

Can I use a custom domain with ECS Gateway?

The announcement and docs don't cover it. Each service gets a generated HTTPS hostname, and commenters noted a CNAME wouldn't work because routing depends on that hostname.

Which ECS launch types does ECS Gateway support?

ECS on EC2, AWS Fargate and ECS Managed Instances, all with awsvpc network mode. Express Mode services can't connect to a gateway.

How many services can share one load balancer?

Up to 25 services share an ALB with host-based routing. The default maxAlbCount is 10, and if it's reached with no room, the deployment fails.