Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS CloudFormation now supports blue/green deployments for Amazon ECS

aws.amazon.com

Post reply on HN
Print view View original

11–20 of 80 posts

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#11

Post by Androider »

sandGorgon wrote: post #5
ciguy wrote: post #2

The ECS default deployment model is quite frankly a disaster. I've written many Python/Go scripts over the years to wrangle it into a sensible form for CI/CD. Good to see that they're working on it, but I don't know why they don't fix the underlying paradigm instead of making it Cloudformation exclusive.

Exactly this - I think internally there is a tussle on what is the strategic way forward. There are so many - Elastic Beanstalk, ECS, EKS, ECS-on-Fargate, EKS-on-Fargate..and of course the huge marketing push for Serverless. They could have the sensible way out and built EKS as the foundation of everything - makes total sense given the massive ecosystem around kubernetes. ECS and Fargate should be killed off. https:/…

CDK8S doesn't replace Elastic Beanstalk, because the folks using EB are going to continue to use EB. If it ain't broke...

ECS predates EKS, and is better integrated than EKS with their other services. If you want a painless container experience on AWS, ECS for Fargate is what'll you'll want to use today. So both existing folks who use ECS today as well as new customers are going to keep using ECS.

Folks who like K8, perhaps from prior experience, are going to use EKS despite it having some rough corners.

See, Amazon is perfectly happy to support everything under the sun as long as there are paying users. See their database offering for very much the same strategy, and it would be silly to say that they should drop DB x since they now offer DB y.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#12

Post by harpratap »

sandGorgon wrote: post #5
ciguy wrote: post #2

The ECS default deployment model is quite frankly a disaster. I've written many Python/Go scripts over the years to wrangle it into a sensible form for CI/CD. Good to see that they're working on it, but I don't know why they don't fix the underlying paradigm instead of making it Cloudformation exclusive.

Exactly this - I think internally there is a tussle on what is the strategic way forward. There are so many - Elastic Beanstalk, ECS, EKS, ECS-on-Fargate, EKS-on-Fargate..and of course the huge marketing push for Serverless. They could have the sensible way out and built EKS as the foundation of everything - makes total sense given the massive ecosystem around kubernetes. ECS and Fargate should be killed off. https:/…

I think it is a good strategy for AWS to invest in all kind of different solutions for Container technology and see which one wins. Betting on just one horse might end up being too high of a risk. Google has GKE, Cloud Run, Anthos and directly run containers on Compute Engine

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#13

Post by x3n0ph3n3 »

grubbypaw wrote: post #9

I've never understood CloudFormation's lag time in supporting new service functionality. This launched nearly 3 years ago. https://aws.amazon.com/blogs/compute/bluegreen-deployments-w...

Because while "ready" for new features includes API support, it does not include CloudFormation support. The problem is entirely AWS politics and culture.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#15

Post by harpratap »

solidasparagus wrote: post #10
sandGorgon wrote: post #5

Earlier quoted context omitted.

Exactly this - I think internally there is a tussle on what is the strategic way forward. There are so many - Elastic Beanstalk, ECS, EKS, ECS-on-Fargate, EKS-on-Fargate..and of course the huge marketing push for Serverless. They could have the sensible way out and built EKS as the foundation of everything - makes total sense given the massive ecosystem around kubernetes. ECS and Fargate should be killed off. https:/…

k8s is not for everyone. It has a high administration and complexity burden. It would be a mistake to make k8s a requirement for core AWS services. Fargate is a low-level compute platform - it is parallel to ec2 and lambda. It does not compete with kubernetes (as can be seen by the eks-on-fargate offering). There is probably some tension between ECS and k8s - AWS built a container orchestration platform based on what…

Vanilla K8s is not meant to be directly used by everyone. Watch https://www.youtube.com/watch?v=ZqQTEdHVaCw for insight on how K8s team expect the project to move forward. Frameworks like OpenDeis and Knative are meant to be used by developers.

IMO K8s will become akin to Linux Kernel. Almost no one uses bare mainline Linux kernels, you choose a distro based on your needs. Companies like RedHat and Canonical will pop up and provide their own packaged "distros" of K8s and you will choose which philosophy best suits your needs.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#16

Post by jcims »

x3n0ph3n3 wrote: post #13
grubbypaw wrote: post #9

I've never understood CloudFormation's lag time in supporting new service functionality. This launched nearly 3 years ago. https://aws.amazon.com/blogs/compute/bluegreen-deployments-w...

Because while "ready" for new features includes API support, it does not include CloudFormation support. The problem is entirely AWS politics and culture.

Who builds the cloudformation support? I could understand not baking it in on an initial feature release but it should be there ’soon’.

Same with Config.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#17

Post by snypox »

bdcravens wrote: post #7
ciguy wrote: post #2

The ECS default deployment model is quite frankly a disaster. I've written many Python/Go scripts over the years to wrangle it into a sensible form for CI/CD. Good to see that they're working on it, but I don't know why they don't fix the underlying paradigm instead of making it Cloudformation exclusive.

We haven't had any problems, but our workload is mostly async background work. Our CI pushes master when it passes, running a simple script to push to ECR with a git SHA tag, update the task to use the latest image, and then update the service to the latest task definition. It takes 2 lines of bash to update the task definition, and 2 lines to run the AWS commands.

Really? At the last company we had like a 200 lines PowerShell script for all of that.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#18

Post by phamilton »

It looks like this uses a new, not yet documented, top level attribute in a template: Hook.

At least, I haven't found any documentation for it other than the template they say to copy in the linked user guide for this feature. Definitely not supported in CDK.

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#19

Post by tybit »

sandGorgon wrote: post #5
ciguy wrote: post #2

The ECS default deployment model is quite frankly a disaster. I've written many Python/Go scripts over the years to wrangle it into a sensible form for CI/CD. Good to see that they're working on it, but I don't know why they don't fix the underlying paradigm instead of making it Cloudformation exclusive.

Exactly this - I think internally there is a tussle on what is the strategic way forward. There are so many - Elastic Beanstalk, ECS, EKS, ECS-on-Fargate, EKS-on-Fargate..and of course the huge marketing push for Serverless. They could have the sensible way out and built EKS as the foundation of everything - makes total sense given the massive ecosystem around kubernetes. ECS and Fargate should be killed off. https:/…

AWS doesn’t turn off barely used services, ECS has lots of happy customers that don’t want to deal with Kubernetes.

Same goes for Fargate, except that it’s now offered by EKS to, what possible reason would they have too turn it off?

Re: AWS CloudFormation now supports blue/green deployments for Amazon ECS

#20

Post by sandGorgon »

tybit wrote: post #19
sandGorgon wrote: post #5

Earlier quoted context omitted.

Exactly this - I think internally there is a tussle on what is the strategic way forward. There are so many - Elastic Beanstalk, ECS, EKS, ECS-on-Fargate, EKS-on-Fargate..and of course the huge marketing push for Serverless. They could have the sensible way out and built EKS as the foundation of everything - makes total sense given the massive ecosystem around kubernetes. ECS and Fargate should be killed off. https:/…

AWS doesn’t turn off barely used services, ECS has lots of happy customers that don’t want to deal with Kubernetes. Same goes for Fargate, except that it’s now offered by EKS to, what possible reason would they have too turn it off?

CDK8S will actually abstract away the complexity of kubernetes. I don't think you will find the complexity any worse than ECS
Post reply on HN