aws-doc-sdk-examples VS goth

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

Also really easy to implement as there are libraries that do all the heavy lifting for you (https://github.com/markbates/goth is a great starting place IMHO)

In the package 'markbates/goth' that provides a client implementation of OAuth 2.0, the authors have defined the function CompleteUserAuth at the package level like this:

You can use oauth2. Just take e.g. a look at the dex documentation dex. Dex is not a library but a standalone federated oidc provider. Highly recommended. For libraries take a look at goth.

For the kind of websites I prefer to build -- server side rendered with HTMX/Alpine for the extra niceness -- Rust I think could be a very good fit. The main downside for my personal projects is the ecosystem. E.g., a good standard way to handle CSRF tokens, standardised oauth2 implementations (like https://github.com/markbates/goth in Go), things like that. I found myself having to write a lot of code that just exists in the Go ecosystem. The main downside for a business is that it's going to make it harder to hire, since Rust genuinely requires more skill. Yes, developers will make mistakes in Go, as it's far too easy to do things like access shared memory in dangerous ways. But on the flip side, it's a lot easier for them to deliver a feature. In a choice between shipping a feature that is buggy in hard to detect ways, vs not being able to deliver at all because you can't get developers, I think it's better to ship.