Ask HN：帮助选择 AWS ECS 和 EKS
1 分•作者: pigradish•5 天前
大家好。我最近加入了一家正在从 Heroku 迁移到 AWS 的成熟公司。我是第二位 DevOps/SRE 类型的员工，另一位同事更偏向 IT 背景。他以及大约 20 人的开发团队，都没有任何云计算或 IaC 的经验。我们的工作负载几乎完全是无状态的 Web 服务，还有一些数据管道工作已经迁移到了 AWS Lambda。
我的直觉告诉我 ECS 是更适合这个团队的选择——它更简单，无需运维维护，除了人们需要学习的 AWS 基础知识外，几乎没有额外的抽象。在我加入之前聘请的咨询团队正在力推 EKS，但我并不认为其改进的开发者体验值得我们团队承担增加的复杂性和运维负担。他们的论点是，开发人员可以有效地被隔离在 Kubernetes 集群中，因此集群本身的维护工作量的增加，可以通过减少围绕自定义 IAM 权限设置、多个 AWS 账户（我们只需要在集群内使用命名空间）等方面的开销来抵消。
非常感谢任何想法或建议。
查看原文
Hello everyone. I was recently hired at an established company that is in the process of migrating to AWS from Heroku. I am the second devops/SRE like employee, the other person has more of an IT background. He, along with the 20ish person dev team, have no experience with anything cloud or IaC. Our workloads are almost entirely stateless web services, with some data pipeline work that has already been moved to AWS lambda.<p>My gut is telling me ECS is the better choice for this team - simpler, no operational maintenance, almost no additional abstractions beyond the AWS primitives people will need to learn anyway. A consulting team hired before I was brought in are pushing EKS, but I’m not convinced that the improved devex is worth the increase in complexity and operational burden for our team. Their argument is that developers can be effectively quarantined within k8s, so the increase in maintenance on the cluster itself is offset by the reduction in work around custom IAM permissioning, multiple AWS accounts (we’d just use namespaces within the cluster), etc.<p>Any thoughts or input would be greatly appreciated.