When you are deploying to ECS with CodeDeploy you can create your installation scripts using bash scripts, when it's with Fargate you have to use Lambda functions.
You can run Fargate Tasks and Services on EKS.
Fargate being serverless containers means that it has cold starts, so this might be a problem for most people, but being serverless you don't have to do any right sizing.
With ECS you still have to right-size your EC2 instances so have the needed capacity to deploy both the old and new containers when you want to do an in-place deployment.
You can do blue/green with ECS and that is where you create a cluster every time, I don't really like this method since you have slow deploys.
It is possible to SSH into a Fargate running service, but it's quite the pain and generally not recommended.
I did a comparison talk which also includes AWS Lambda last year at the AWS Toronto Summit. lol
When you are deploying to ECS with CodeDeploy you can create your installation scripts using bash scripts, when it's with Fargate you have to use Lambda functions.
You can run Fargate Tasks and Services on EKS.
Fargate being serverless containers means that it has cold starts, so this might be a problem for most people, but being serverless you don't have to do any right sizing.
With ECS you still have to right-size your EC2 instances so have the needed capacity to deploy both the old and new containers when you want to do an in-place deployment.
You can do blue/green with ECS and that is where you create a cluster every time, I don't really like this method since you have slow deploys.
It is possible to SSH into a Fargate running service, but it's quite the pain and generally not recommended.
I did a comparison talk which also includes AWS Lambda last year at the AWS Toronto Summit. lol
Thanks Andrew, very interesting talk! 💡