aws-cf-templates VS artifact-manager-s3-plugin

I think any of the common proxy platforms would work, the example code just happens to be for HAProxy. Managing ECS isn't that hard once you get it stood up. https://github.com/widdix/aws-cf-templates widdix provides a ton of reference cloud formation templates that cover most aspects of running aws infrastructure. We run everything through cloud formation and it is self-scaling and self-healing. System manager can automate patch management as well.

https://www.stackery.io/registry/?repo=https://github.com/wi...

Finally, if you’re feeling nostalgic for winter, this example from Symphonia is a lab for benchmarking Lambda cold starts for Java runtimes so that you can better understand how they behave and plan configurations accordingly.

I see. The only option I'm aware of is https://github.com/jenkinsci/artifact-manager-s3-plugin (S3 API compatible).

So, yep done all this and completely agree. I set this all up with Terraform, Docker, and JCasC. However with our 80 person org and around 30 active repos (all with multibranch pipelines) ,200-300 builds a day; I'm seeing reboot times in the 15-20 minutes range (which hurts.) Also, if you don't drain the Jenkins instance prior to replacement then the currently running jobs fail; causing more issues (need to automate this anyone got a script?). Other complaints, plugins break ALL THE TIME so we really have to do some QA before sending a new Jenkins container out to prod. The S3 Artifact plugin doesn't do multipart uploads which limits the maximum size and performance on stash/archiveArtifact (patch here https://github.com/jenkinsci/artifact-manager-s3-plugin/pull/141; could still use a patch to stream the zip/tarball creation). The downstream build feature is really powerful but the blue ocean ui is iffy on it (sometimes it shows downstream builds; sometimes not). The ec2 plugin works but I've never gotten the spot-fleet plugin to work properly (specifically interested in being able to choose alternately sized instances based on spot price and availability). If you use spot-instances with the ec2 plugin; there's no clear way to retry the build (would love a tutorial or script that accomplishes the steps needed on this. i.e. trapping the signal coming from the OS and turning it into an exception in the pipeline). Overall, it's nice once you get here; but it's a metric ton of work... and there's still a bunch of problems. Really wish there was something easier to maintain and grow with a cloud first approach (i.e. rolling upgrades, object store support, fleet support).