4 ms·

Does this mean ECS is going away? It’s sort of strange that they have two managed-container-deployment products.

jedberg 8y ago
Most likely yes. They've seen the writing on the wall, that K8s has won. It will probably just be a slow deprecation like they did with Simple DB.
- hb3b 8y ago
  It wasn't a particularly friendly service for developers, anyway.
  - k__ 8y ago
    Isn't ECS the AWS optimized version and EKS the more basic stuff?
    - scribu 8y ago
      No, ECS is a homegrown container orchestration service that has no relationship with Kubernetes. EKS is the optimized-for-AWS version of Kubernetes. There’s also AWS Fargate, which is a more managed version of ECS.
      - thramp 8y ago
        There were public presentations where Fargate would have an EKS deployment option. (Disclaimer: I work for Amazon, but don't have inside knowledge of the AWS Containers Organization's plans.)
      - k__ 8y ago
        ECS was specifically created to work good with AWS. How can EKS be better for AWS customers?
        ec109685 8y ago
        Because the open source kubernetes components have thousands of developers contributing to the code, as well a whole ecosystem of components built to kubernetes’ api.
    - gtaylor 8y ago
      ECS is their entirely custom container orchestrator. EKS is just hosted Kubernetes with AWS integrations.
      - k__ 8y ago
        Yes. ECS is better integrated into AWS. EKS is just what everyone uses plugged into AWS. Can't understand how this should be better.
        outworlder 8y ago
        Try both, you'll understand.
bdcravens 8y ago
It probably won’t go away. They didn’t eliminate Cloud Search when they started offering managed Elastic Search, or SQS when they started offering managed Active MQ. However AWS will likely put resources into EKS vs ECS.
peterwwillis 8y ago
The use and functionality you get from ECS and EKS can be quite different. ECS is tightly AWS-integrated, EKS is designed to be cloud-independent. You can pick between ECS and EKS based on your needs and use Fargate as the interface to either.
NathanKP 8y ago
No ECS is definitely not going away. Having multiple ways of doing something is not strange for Amazon, in fact its what you should expect from Amazon. Just look at how many different database options there are! ECS will remain as the free option that is great for small workloads, and companies that are going all in on AWS. It has the tightest integrations with other AWS services. EKS is a good option for companies that don't mind spending a little more to run the open source version so that they have portability or a consistent environment between their on-premise and the cloud. While EKS does integrate with other AWS services it has to do so through plugins and controllers that aren't quite as tightly coupled, since EKS is just the same open source Kubernetes that you can run anywhere.
auslander 8y ago
Why strange? Customers asked, AWS provided :) To me, simpler is better in many ways. I'll stick to using ECS till I hit something ECS cannot provide. I'm yet to hear what could it be.

Most likely yes. They've seen the writing on the wall, that K8s has won. It will probably just be a slow deprecation like they did with Simple DB.

hb3b 8y ago
It wasn't a particularly friendly service for developers, anyway.
- k__ 8y ago
  Isn't ECS the AWS optimized version and EKS the more basic stuff?
  - scribu 8y ago
    No, ECS is a homegrown container orchestration service that has no relationship with Kubernetes. EKS is the optimized-for-AWS version of Kubernetes. There’s also AWS Fargate, which is a more managed version of ECS.
    - thramp 8y ago
      There were public presentations where Fargate would have an EKS deployment option. (Disclaimer: I work for Amazon, but don't have inside knowledge of the AWS Containers Organization's plans.)
    - k__ 8y ago
      ECS was specifically created to work good with AWS. How can EKS be better for AWS customers?
      - ec109685 8y ago
        Because the open source kubernetes components have thousands of developers contributing to the code, as well a whole ecosystem of components built to kubernetes’ api.
  - gtaylor 8y ago
    ECS is their entirely custom container orchestrator. EKS is just hosted Kubernetes with AWS integrations.
    - k__ 8y ago
      Yes. ECS is better integrated into AWS. EKS is just what everyone uses plugged into AWS. Can't understand how this should be better.
      - outworlder 8y ago
        Try both, you'll understand.

bdcravens 8y ago

It probably won’t go away. They didn’t eliminate Cloud Search when they started offering managed Elastic Search, or SQS when they started offering managed Active MQ. However AWS will likely put resources into EKS vs ECS.

peterwwillis 8y ago

The use and functionality you get from ECS and EKS can be quite different. ECS is tightly AWS-integrated, EKS is designed to be cloud-independent. You can pick between ECS and EKS based on your needs and use Fargate as the interface to either.

NathanKP 8y ago

No ECS is definitely not going away. Having multiple ways of doing something is not strange for Amazon, in fact its what you should expect from Amazon. Just look at how many different database options there are! ECS will remain as the free option that is great for small workloads, and companies that are going all in on AWS. It has the tightest integrations with other AWS services. EKS is a good option for companies that don't mind spending a little more to run the open source version so that they have portability or a consistent environment between their on-premise and the cloud. While EKS does integrate with other AWS services it has to do so through plugins and controllers that aren't quite as tightly coupled, since EKS is just the same open source Kubernetes that you can run anywhere.

auslander 8y ago

Why strange? Customers asked, AWS provided :) To me, simpler is better in many ways. I'll stick to using ECS till I hit something ECS cannot provide. I'm yet to hear what could it be.