microshift VS aws-sdk-go-v2

Another good option is Microshift: https://github.com/openshift/microshift

RPM RHEL derivatives I recommend: https://microshift.io

If you are moving to edge you can try microshift (https://microshift.io/). There is also option to run a single node ocp (https://docs.openshift.com/container-platform/4.9/installing/installing_sno/install-sno-installing-sno.html).

There is also microshift. https://microshift.io/

I use one snap, but not on Fedora, instead with RHEL. It is the only way to use Microk8s, which is a quite full-featured distribution of Kubernetes that has a small footprint. Red Hat recently came out with an early offering called MicroShift, but it's not really ready yet. When it can satisfy my needs, you'll bet I'm switching.

This is an open source project from the start (as most things red hat creates), you can find the coffee here: https://github.com/redhat-et/microshift

GitHub - redhat-et/microshift: A small form factor OpenShift/Kubernetes optimized for edge computing

It turns out that the AWS SDK for go, aws-sdk-go-v2, released some breaking changes that are unrelated to S3 Express One Zone. You can read more about these changes here.

AWS S3 official documentation AWS S3 official examples

assume_role_with_mfa is a handy small MFA GUI tool from Cristian Magherusan-Stanciu designed to be used as credential_proces for AWS CLI configuration profiles. This is a workaround for the official AWS MFA setup, that works for the CLI but does not work for the Go SDK, as reported at aws-sdk-go-v2/#2356.

In this blog post, you will be using the aws-lambda-go library along with the AWS Go SDK v2 for an application that will process records from an Amazon SNS topic and store them in a DynamoDB table.

This blog post is for folks interested in learning how to use Golang and AWS Lambda to build a serverless solution. You will be using the aws-lambda-go library along with the AWS Go SDK v2 for an application that will process records from an Amazon Kinesis data stream and store them in a DynamoDB table. But that's not all! You will also use Go bindings for AWS CDK to implement "Infrastructure-as-code" for the entire solution and deploy it with the AWS CDK CLI.

The trouble with importing modules from within the same repository is that Go modules won't be able to work out where to download them from. The require directives I mentioned are used extensively by aws-sdk-go-v2 if you're interested in an example.

You may prefer https://github.com/aws/aws-sdk-go-v2 .

I ran into it by switching from aws-sdk-go to aws-sdk-go-v2 and the binary jumped from 27Mb to 66Mb [1]

Granted fully featured app will likely use all of the module's code so it's not a factor.

[1] https://github.com/aws/aws-sdk-go-v2/discussions/1532