> Imagine trying to figure out ECS, Fargate, Lambda, ACM, CloudWatch logs, alarms and metrics? In case anyone is curious, we went that route. - ECS + Fargate

> Imagine trying to figure out ECS, Fargate, Lambda, ACM, CloudWatch logs, alarms and metrics? In case anyone is curious, we went that route. - ECS + Fargate + CDK took one of us two (8h/day) weeks for the initial setup. We've sprinkled a few more days here and there since then. - Cloudwatch logs are "setup-free" (your containers' logs get sent there by default when using CDK constructs). - ACM... we don't use directly. CDK will easily setup TLS-enabled (with AWS-emitted certificates) ALB (Application Load Balancer(s)) for you. - Lambdas we don't use much. - Metrics & Alarms are easy to set up but they generally suck. The custom language for computed metrics is clumsy and quite limited. The anomaly detection sucks. And it is expensive even by cloud standards (don't create metrics and alarms willy-nilly or you'll feel it in the next invoice). - Our application code doesn't know much about AWS (we do use libraries for S3 and SES, but these are just easy to swap adapters). - We ended up with ~3k lines of CDK definitions in typescript. These are very easy to read, and only moderately hard to write (you do need to look up the docs). However, I can say without a doubt that it's been the easiest infrastructure definition/description language that I've ever used. I don't have enough experience with K8s to know whether that route would have been better or worse, but I can say this route hasn't been a pain point for us.