On the one hand, I'd really like to try out AWS Batch....
... but I look at the 45 steps listed on this page (I counted the <li> tags) and I just don't think I can summon up the energy to try and slog through them all https://docs.aws.amazon.com/batch/latest/userguide/getting-started-fargate.html
I know from past experience that every single one of those 45 steps includes a chance I'll make a mistake, and then I'll have to rewind back through all the previous steps to figure out what went wrong
Not to mention I'm not even sure if that's the right documentation page to get started on - they have "Getting Started - Amazon EC2" and "Getting Started - Fargate" and "AWS Batch on Amazon EKS", I want whichever version means I don't have to think about provisioning any servers, which I guess is the Fargate one?
@simon Batch has been working pretty well for us for a long time and didn't feel too hard to configure. You can be fairly flexible re instance sizes and where they're coming from if you want. Fargate also works well and comes up faster, but you're more limited in terms of CPU/RAM sizing etc., plus you need to handle cases where an attempt failed etc. (if you're launching them on demand).
