InfoQ

Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support

8.5内容质量
Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support

TL;DR · AI 摘要

AWS新推出的ECS Gateway生成随机主机名,但不支持自定义域名,限制了其在生产环境的应用。

核心要点

  • ECS Gateway为每个服务生成格式为https://<unique-id>.ecs.<region>.on.aws的主机名
  • 当前版本不支持自定义域名,CNAME记录无法解决路由问题
  • 更适合临时/预览环境,现有生产环境需谨慎采用

结构提纲

按章节快速跳转。

  1. §ECS Gateway发布

    AWS推出账户级入口资源ECS Gateway,简化容器工作负载网络配置。

  2. 平台团队定义网络后,应用团队通过连接器附加服务,自动生成主机名和证书。

  3. Reddit用户指出随机主机名导致流量定向困难,CNAME记录无法解决路由问题。

  4. 所有资源直接创建在用户账户,包含IAM角色、子网、TLS证书等基础设施。

  5. 文档未提及自定义域名支持,Route 53和CNAME记录未被讨论。

  6. 更适合临时/预览环境,现有生产环境需评估是否适用。

思维导图

用一张图看清主题之间的关系。

查看大纲文本(无障碍 / 无 JS 友好)
  • Amazon ECS Gateway
    • 核心功能
      • 自动生成主机名
      • 账户级资源管理
    • 限制
      • 无自定义域名支持
      • CNAME路由问题
    • 适用场景
      • 临时环境
      • 预览环境

金句 / Highlights

值得收藏与分享的关键句。

  • I don’t get how this is useful at all since you get a random domain name for your ecs service.

    — Reddit评论

    ⬇︎ 下载 PNG𝕏 分享到 X
  • Amazon ECS uses host-based routing to direct requests from a shared Application Load Balancer to the appropriate service.

    — AWS文档

    ⬇︎ 下载 PNG𝕏 分享到 X
  • It creates host-based rules in the load balancer, so it wouldn’t know where to route if you used a CNAME.

    — Reddit评论

    ⬇︎ 下载 PNG𝕏 分享到 X
#AWS#ECS#云原生#网络#容器化
打开原文

Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support - InfoQ

InfoQ Homepage News Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support

Cloud

Scaling OpenTelemetry: Managing Collectors, Configuration, and Cost (Webinar Nov 19th)

Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support

Nov 02, 2026 3 min read

by

  • Steef-Jan Wiggers

#### Follow us on

Youtube

232K Followers

Linkedin

26K Followers

Instagram

New

RSS

19K Readers

X

57.1k Followers

Facebook

21K Likes

Bluesky

Listen to this article -

0:00

Audio ready to play

Your browser does not support the audio element.

Normal

1.25x

1.5x

Like

new dropdown rading list

  • Reading list

AWS recently released Amazon ECS Gateway , an account-level ingress resource that lets platform teams define networking once, and application teams attach services to it with a connector. Each service gets a generated hostname, and neither the announcement nor the documentation describes how to put a custom domain in front of it.

The gateway is described by principal developer advocate Channy Yun as:

a new account-level resource that simplifies ingress networking for containerized workloads by dynamically provisioning and managing the necessary infrastructure on your behalf, with all resources created directly in your account.

It is available in all commercial regions where ECS runs, at no additional charge beyond the resources it provisions. The first question practitioners asked was how to put their own domain in front of it.

The split it introduces is organizational. Platform teams create a gateway with an infrastructure IAM role, subnets, security groups, TLS certificates, listener settings, and optional WAF web ACLs, then associate it with clusters. Application teams add a gateway connector through CreateService or UpdateService , and ECS provisions per service an ACM certificate, a hostname, a listener rule, a target group, and a security group accepting traffic only from the load balancer.

Amazon ECS Gateway architecture. (Source: AWS News Blog post )

On Reddit , commenter zurnout went straight at the hostname:

I don’t get how this is useful at all since you get a random domain name for your ecs service. How am I going to direct traffic to that? It’s the same thing with ECS Express.

Asked whether a CNAME would solve it, he explained why it would not:

It creates host-based rules in the load balancer, so it wouldn’t know where to route if you used a CNAME.

Commenter ResponsibleWaltz1479 reached the same conclusion, calling the feature usable "for ephemeral /preview environments if the app is not hostname aware," but not for their existing setup.

The documentation supports the reading. Each service "gets a generated hostname in the form https://<unique-id>.ecs.<region>.on.aws," and "Amazon ECS uses host-based routing to direct requests from a shared Application Load Balancer to the appropriate service." Custom domain names, Route 53, and CNAME records go unmentioned. Commenter Kralizek82 raised the one workaround nobody resolved, asking whether a gateway could serve as an internal CloudFront origin.

Opinion split on whether the service is substantial. Commenter bioJesusMain called it:

It’s just ALB and DNS with a wrapper

And commenter aneryx suggested:

It could even just be a CDK construct on top of ALB/NLB and Route 53

Commenter brokenlabrum answered that from experience:

Those higher level L3 constructs have often turned out to be a mistake because they need to expose every knob on the L2 constructs they wrap. And if they’re opinionated and don’t, ejecting from an L3 construct without it deleting your resources is hell.

Commenter Aggressive-Height167 put the case for it, noting that letting a cloud team define networking once while application teams deploy against it "seems like a pretty solid improvement." The test, they added, "is whether it actually removes complexity without taking away too much control."

The documentation adds a cost detail the announcement leaves out. A gateway adds load balancers as existing ones fill and removes them only when they empty, but it "does not consolidate load balancers" and "does not move services between load balancers, so several partly filled load balancers can remain after services leave." Each one is billed.

Commenter jregovic noted that more than 25 services means more than one load balancer. An AWS respondent answered that "multiple ALBs are handled by the gateway itself - so it’s not something that you need to worry about." The gateway does handle them. It does not pack them.

ECS also "does not repair changes made outside it." Modify or delete a managed resource and traffic "can stop," with later deployments, gateway updates, and cleanup operations liable to fail.

The envelope is specific. Twenty-five services share one load balancer, against a default maxAlbCount of 10 and a documented ceiling of 200 per gateway. AWS warns that "if maxAlbCount is reached and no ALB has available capacity, the deployment fails." Listeners serve HTTPS on port 443 only; services must use awsvpc networking in the same VPC and account, and Express Mode services are excluded.

The thread’s most upvoted comment dismissed the launch as "a promotion project," and several commenters asked why AWS Elastic Beanstalk did not already cover the ground, one pointing at its Cluster Mode release last month. Commenter dmcnaughton1 offered the other side, saying a current ECS migration was early enough to adopt it.

main wrapper for authors section

About the Author

section title

main wrapper for each author

#### Steef-Jan Wiggers

Show more

Show less

#### This content is in the Cloud topic

##### Related Topics:

  • Development
  • Architecture & Design
  • DevOps
  • Cloud
  • Containers
  • AWS
  • Networking
  • Related Editorial
  • Related Sponsors
  • Related Sponsor November 19, 2026, 12 PM EST Scaling OpenTelemetry: Managing Collectors, Configuration, and Cost Presented by: David Iparraguirre - Senior Product Marketing Manager at Datadog, and Jessica Yang - Product Manager at Datadog

The InfoQ Newsletter

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.