aws-sdk-go-v2 VS aws-lambda-go

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

You can follow this documentation and use the Lambda function template repo here.

The entire solution is built using Go - this includes the Lambda function (using aws-lambda-go library) as well as the complete solution deployment using AWS CDK.

Now, to work with Lambda using go, we have to change the code a little bit and use this official aws tool.

AWS Lambda GitHub Repository - The official GitHub repository for AWS Lambda. It includes examples, guides, and resources specifically for working with Lambda in Go.

You will be using the Go programming language for the business logic (thanks to aws-lambda-go library) as well as the infrastructure component (Go bindings for AWS CDK) to deploy the solution.

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.

The Lambda function is written using the aws-lambda-go library and you will use the Infrastructure-Is-Code paradigm to deploy the solution with AWS CDK (thanks to the Go bindings for AWS CDK)

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.

Now that you have everything you need, let’s create a new project using Go modules for your function. For example, let’s name the module lambda-time. In a new, empty directory, initialize the Go module, and install the AWS Lambda for Go library: