Amazon ECS vs. Kubernetes: Which should you use on AWS? (techtarget.com)

Amazon ECS vs. Kubernetes: Which should you use on AWS?

Amazon ECS 与 Kubernetes：您应该在 AWS 上使用哪个？

如何在 AWS 上进行容器编排？ 在为您的工作负载选择应用程序架构之前，了解有关 ECS、EKS、DIY Kubernetes 和 Fargate 的基础知识。

IT teams have several options for running containerized applications on AWS. Some organizations will opt for Kubernetes, the de facto choice for container orchestration, while others will want to use AWS' proprietary orchestration service instead.

IT 团队有多种选择在 AWS 上运行容器化应用程序。 一些组织将选择 Kubernetes，这是容器编排的实际选择，而其他组织则希望使用 AWS 的专有编排服务。

IT teams also have the choice of controlling the underlying virtual machines themselves or leaving those management tasks to Amazon. Deciding which approach to take will depend on several factors, so let's explore your options for deploying containers on AWS.

IT 团队还可以选择自己控制底层虚拟机或将这些管理任务留给亚马逊。 决定采用哪种方法将取决于几个因素，因此让我们探索在 AWS 上部署容器的选项。

在 AWS 上部署容器的方法

There are four main deployment strategies for containerized applications on AWS.

AWS 上的容器化应用程序有四种主要部署策略。

1. Kubernetes on Amazon EC2. If you want to run Kubernetes on AWS without using Amazon's managed container services, you create the necessary Amazon EC2 instances, then install a Kubernetes distribution of your choosing. With this approach, Amazon provides only the virtual machines to host your Kubernetes nodes. Users are responsible for provisioning the VMs, along with setting up and managing Kubernetes.

Amazon EC2 上的 Kubernetes。 如果您想在 AWS 上运行 Kubernetes 而不使用 Amazon 的托管容器服务，您可以创建必要的 Amazon EC2 实例，然后安装您选择的 Kubernetes 发行版。 通过这种方法，Amazon 仅提供虚拟机来托管您的 Kubernetes 节点。 用户负责配置 VM，以及设置和管理 Kubernetes。

2. Amazon Elastic Kubernetes Service (EKS) on Amazon EC2. With Amazon EKS, a managed Kubernetes service, Amazon provides both a Kubernetes management plane and infrastructure to host your cluster. With this option, you don't need to set up Kubernetes, install management or monitoring tools or provision your own nodes. You will, however, still need to perform some management tasks, such as upgrading to newer versions of Kubernetes when available.

Amazon EC2 上的 Amazon Elastic Kubernetes Service (EKS)。 借助托管 Kubernetes 服务 Amazon EKS，Amazon 提供了 Kubernetes 管理平面和基础设施来托管您的集群。 使用此选项，您无需设置 Kubernetes、安装管理或监控工具或配置您自己的节点。 但是，您仍然需要执行一些管理任务，例如在可用时升级到新版本的 Kubernetes。

3. Amazon Elastic Container Service (ECS) on Amazon EC2. Amazon ECS is similar to EKS, but it relies on a proprietary control plane instead of Kubernetes. You are responsible for provisioning the host infrastructure, but ECS handles container orchestration.

Amazon EC2 上的 Amazon Elastic Container Service (ECS)。 Amazon ECS 类似于 EKS，但它依赖于专有控制平面而不是 Kubernetes。 您负责配置主机基础设施，但 ECS 处理容器编排。

4. AWS Fargate. AWS handles infrastructure provisioning and management of Fargate, whether you're using ECS or EKS. You simply load your containers and run them -- or you can configure the conditions that should trigger them to run.

AWS Fargate。 无论您使用的是 ECS 还是 EKS，AWS 都会处理 Fargate 的基础设施预置和管理。 您只需加载容器并运行它们——或者您可以配置触发它们运行的条件。

To decide which approach is best, you first need to choose whether you want to use ECS or Kubernetes.

要决定哪种方法最好，您首先需要选择是要使用 ECS 还是 Kubernetes。

ECS integrates better with other Amazon cloud services because it's native to the platform. But you can't extend it into other clouds or move hosted workloads directly to another location, except for an on-premises installation of AWS Outposts. Still, containers are fairly portable, so it doesn't require a tremendous effort to move to a different platform.

ECS 可以更好地与其他 Amazon 云服务集成，因为它是平台的原生。 但您无法将其扩展到其他云或将托管工作负载直接移动到其他位置，除非在本地安装 AWS Outposts。 尽管如此，容器还是相当便携的，因此不需要付出巨大的努力就可以迁移到不同的平台。

In contrast, Kubernetes is an open source platform that is available on all of the major public clouds and can also run on premises beyond AWS' software. There is also a large and dynamic ecosystem surrounding Kubernetes. With Kubernetes, you can take advantage of a variety of add-ons and extensions. These extra features are not available from ECS.

相比之下，Kubernetes 是一个开源平台，可以在所有主要的公共云上使用，也可以在 AWS 软件之外的本地运行。 Kubernetes 周围还有一个庞大而动态的生态系统。 借助 Kubernetes，您可以利用各种附加组件和扩展。 ECS 不提供这些额外功能。

If you choose to run Kubernetes on AWS, EKS is probably the best approach in most cases. EKS is much easier to set up and reduces the management burden considerably. EKS can also run on Outposts, in case you need any workloads on premises.

如果您选择在 AWS 上运行 Kubernetes，在大多数情况下，EKS 可能是最好的方法。 EKS 更容易设置并大大减少了管理负担。 EKS 还可以在 Outposts 上运行，以防您需要任何本地工作负载。

That said, users have more control if they run generic Kubernetes on EC2 instances; they can pick whichever Kubernetes distribution and tooling they wish. With EKS, users are limited to the configurations and tooling built into the platform.

也就是说，如果用户在 EC2 实例上运行通用 Kubernetes，他们将拥有更多控制权； 他们可以选择他们想要的任何 Kubernetes 发行版和工具。 使用 EKS，用户仅限于平台内置的配置和工具。

If you decide to use one of AWS' managed container services, you'll need to choose between Fargate and EC2.

如果您决定使用 AWS 的托管容器服务之一，则需要在 Fargate 和 EC2 之间进行选择。

In general, cost is the main factor to consider here. Fargate pricing is generally higher, but you only pay for the time that your containers actually run. With EC2, you pay whenever your instances are turned on, even if they are not hosting any active workloads.

一般来说，成本是这里要考虑的主要因素。 Fargate 定价通常较高，但您只需为容器实际运行的时间付费。 使用 EC2，只要您的实例打开，您就需要付费，即使它们没有托管任何活动的工作负载。

Thus, Fargate will likely be more cost-effective if you have containers that run sporadically or experience unpredictable periods of high demand. EC2 is a better option for predictable, consistent workloads.

因此，如果您的容器偶尔运行或经历不可预测的高需求期，Fargate 可能会更合算。 对于可预测的、一致的工作负载，EC2 是更好的选择。

ECS or EKS on EC2 also requires somewhat more management on users' part because they are responsible for at least some infrastructure management. With Fargate, AWS fully manages the host servers.

EC2 上的 ECS 或 EKS 还需要用户方面的更多管理，因为他们至少负责一些基础设施管理。 借助 Fargate，AWS 可以完全管理主机服务器。