artifact-manager-s3-plugin VS aws-doc-sdk-examples

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).

So I did some more research and I found the awsdocs/aws-doc-sdk-examples repo. This repository used a testtools module. So I started an experiment to see how I could use this module. I refactored the code as followed:

I know lambdas can run max for 15 minutes, but they don't, the most they've ran is 11 minutes and something top, but never 15 minutes, it's the read time that's timing out, and it's timing out because the response from the lambda function is not reaching the server, someone suggested me that I should look into java v2 so I'll be doing that, i'm totally lost

I am getting similar errors using their complete example from the documentation, using a console app.: https://github.com/awsdocs/aws-doc-sdk-examples/blob/main/dotnetv3/Cognito/Scenarios/Cognito_Basics/CognitoBasics.cs

GitHub - AWS SDK for Go Examples

I don't see any swift examples in the example code project - https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/swift/example_code

I've also tried to inject AmazonS3Client inside S3Service.java (AUtoWired), nothing changed also. I'm also following this link: https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/javav2/usecases/create_spring_stream_app Its from the AWS Docs, showing how to create a streaming video app.

I'm still beginner learning Go and have a project where I need to upload _docs_ to DB. So, I'd like to build rest api with Gin and use DynamoDB for backend. I have a working version using MongoDB but I wanted to do similar with DynamoDB. I followed this to get familiar with aws sdk for go. But I can't quite work out how to get it to work with Gin framework. Most of the references I find use AWS Lambda and API Gateway.

I am new to Golang and am referencing a code snippet from AWS that puzzles me: https://github.com/awsdocs/aws-doc-sdk-examples/blob/main/gov2/ssm/GetParameter/GetParameterv2.go