Fork me on GitHub
#aws
<
2021-05-29
>
indy09:05:06

Has anyone migrated from AWS EC2 + Kubernetes to AWS Fargate + Kubernetes? Any pros and cons of doing this? The goal is to reduce costs.

lukasz19:05:13

Best to check pricing but EC2 is always going to be cheaper than Fargate, but it involves more management and prep. We're running all workloads on ECS+Fargate, but not because of the direct cost, but because it cuts human cost required in managing everything.

kenny21:05:26

We switched from EKS to ECS Fargate. Far less overhead with Fargate.

futuro19:06:11

One potential con, depending on your workload, is that Fargate has more restrictive cpu/memory limits. So if you need more than 8 vCPUs per container, Fargate may be a bad fit.

futuro19:06:27

That said, the savings in time may allow you to rework your code to need less cpu.

kenny19:06:47

4 vcpu 🙂

futuro19:06:08

Haha, whoops! Thanks Kenny!

kenny19:06:52

It’s be great to have 8. When you said that I got excited since we’d love more vcpu per node.

lukasz19:06:48

I've recently run into this... but yes - refactoring code and fixing hotspots quickly addressed that

indy20:06:47

Thanks for the input, all. I think I’ll let the Fargate idea pass since we have been running with a decent setup of EKS + EC2 + Chef + Terraform and the cost savings might only be marginal if any.

kenny00:06:06

Yeah, the cost savings with Fargate typically comes by freeing up eng resources to work on product instead of infra.

lukasz13:06:55

Absolutely, I went from part time managing our EC2 fleet to not worrying about it at all, after we solidified our setup and created Terraform modules for everything