Post AaPbozMNlnhtwha6YS by ethanrosenthal@recsys.social
 (DIR) More posts by ethanrosenthal@recsys.social
 (DIR) Post #AaPS1kP7ggWRmgJBKq by simon@fedi.simonwillison.net
       2023-10-04T00:18:22Z
       
       0 likes, 0 repeats
       
       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
       
 (DIR) Post #AaPSOblnxHcdfMonuy by simon@fedi.simonwillison.net
       2023-10-04T00:19:43Z
       
       0 likes, 0 repeats
       
       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
       
 (DIR) Post #AaPSa5RXyGTYsiogC0 by simon@fedi.simonwillison.net
       2023-10-04T00:21:29Z
       
       0 likes, 0 repeats
       
       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?
       
 (DIR) Post #AaPTFmRwyjlC8Xt0D2 by scanner@apricot.social
       2023-10-04T00:32:10Z
       
       0 likes, 0 repeats
       
       @simon Heh.. well at least using batch is easier than trying to setup and use kubernetes...
       
 (DIR) Post #AaPTeohtiugiNRHeXQ by sankao@mas.to
       2023-10-04T00:36:29Z
       
       0 likes, 0 repeats
       
       @simon I have been using AWS Batch at work for a few years now, running about a hundred jobs a day, each job being a 2 hours task roughly. What I can say is that it works reliably in the end, but it took us a while getting there.
       
 (DIR) Post #AaPU6Q8ef5jmHtxgI4 by sankao@mas.to
       2023-10-04T00:41:02Z
       
       0 likes, 0 repeats
       
       @simon We use EC2, which does auto-provisioning. You only have to specify which type of instance it needs to spawn.
       
 (DIR) Post #AaPUJW5tpY0eWUuwjI by noamross@ecoevo.social
       2023-10-04T00:42:38Z
       
       0 likes, 0 repeats
       
       @simon After spending a lot of time on those docs and the equivalent elsewhere, I've concluded there's no such thing - just separation of APIs so someone else at your enterprise worries about provisioning servers.
       
 (DIR) Post #AaPUUxrwu6ihqpqpYe by dolmen@mamot.fr
       2023-10-04T00:43:38Z
       
       0 likes, 0 repeats
       
       @simon That's why infrastructure as code is a thing.
       
 (DIR) Post #AaPYARM2TzXr29OUwi by christiankothe@qoto.org
       2023-10-04T01:27:13Z
       
       0 likes, 0 repeats
       
       @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).
       
 (DIR) Post #AaPbozMNlnhtwha6YS by ethanrosenthal@recsys.social
       2023-10-04T02:06:35Z
       
       0 likes, 0 repeats
       
       @simon Batch is so frustratingly complicated, but there also are no real alternatives on AWS. I would love for someone to build a more developer friendly API around it (which is something you could say about most AWS services). If you do end up using it, heads up that Fargate doesn't support GPUs.
       
 (DIR) Post #AaPfzabeXlRyAx2BnM by smy20011@m.cmx.im
       2023-10-04T02:54:40Z
       
       0 likes, 0 repeats
       
       @simon Try that with llm?
       
 (DIR) Post #AaPnJJxyorG22Spjeq by lewiscowles1986@phpc.social
       2023-10-04T04:16:53Z
       
       0 likes, 0 repeats
       
       @simon all the replies about automating or eventually getting there, seem (to me) to be missing the point that a 45 step plan, is a particularly complex one, and maybe daddy big-bucks (AWS) should spend a bit more product time, bundling some of those choices into some named defaults, for those of us that don't want to go through 45 steps, to see if something makes sense for us.We're looking at Batch and Glue on a project I'm working on, and honestly, both got queued due to complexity vs impact
       
 (DIR) Post #AaPpKHO45uFsElcSMy by TobiasFrech@ijug.social
       2023-10-04T04:39:08Z
       
       0 likes, 0 repeats
       
       @simon I always found it of great value to have working examples. Perhaps starting with one of the two CloudFormation templates for Batch is of some value for you? https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/sample-templates-services-us-west-2.html#w4ab1c35c58c13b9
       
 (DIR) Post #AaQYc3j47ZX118IIk4 by mguterl@mastodon.social
       2023-10-04T13:05:29Z
       
       0 likes, 0 repeats
       
       @simon I haven't used Batch, but I recommend looking at the AWS CDK constructs for it. It's probably a lot easier than using the console to set it up.