AWS SDK for Go v2

To use the AWS SDK for Go v2, initialize your project with Go modules and retrieve the necessary dependencies using go get.

Note: The v2 SDK requires a minimum version of Go 1.24.

$ mkdir ~/helloaws
$ cd ~/helloaws
$ go mod init helloaws
$ go get github.com/aws/aws-sdk-go-v2/aws
$ go get github.com/aws/aws-sdk-go-v2/config
$ go get github.com/aws/aws-sdk-go-v2/service/dynamodb

To build the S3 uploader performance utility, use the go test command with the integration and perftest build tags. This generates a test binary named uploader.test.

go test -tags "integration perftest" -c -o uploader.test ./manager/internal/integration/performance/uploader

To supplement auto-generated protocol tests with hand-written Go source files, place your files in the manual/ directory. You must mirror the target path relative to internal/protocoltest/.

For example, if you want a test file to be located at internal/protocoltest/jsonrpc10/my_test.go, you should place your file at:

manual/jsonrpc10/my_test.go

No changes to the build scripts are required, as the copyManualFiles task automatically copies the entire manual/ directory tree into the target destination, overlaying the generated output.

The protocol test generation process uses hand-written Go source files to supplement auto-generated tests with cases that cannot be expressed via Smithy protocol test traits. To add a manual file, you must mirror the target path relative to internal/protocoltest/ within the manual/ directory.

For example, if you want a file to be located at internal/protocoltest/jsonrpc10/my_test.go, you must place it at: manual/jsonrpc10/my_test.go.

No changes to the build scripts are required as the copyManualFiles task automatically copies the entire manual/ directory tree and overlays it onto the generated output.

To build the S3 downloader performance utility, use the go test command with the integration and perftest build tags. This compiles the utility into a test binary.

go test -tags "integration perftest" -c -o download.test ./manager/internal/integration/download

For support and community interaction:

• Questions/Discussions: Use GitHub Discussions.
• Bug Reports: Open a GitHub Issue. When reporting bugs, include your AWS SDK for Go version, Go language version, and OS.
• AWS Support: Open a support ticket with AWS Support for service-related issues.
• Service Issues: For general issues regarding AWS services (not the SDK itself), use the Amazon Web Services Discussion Forums.

The protocol test generation build is driven by Gradle. To execute the full task chain—including Smithy build generation, SDK building, cleaning old tests, and copying both generated and manual files—run the following command from the parent directory:

./gradlew :protocol-test-codegen:build

The protocol test generation process is managed via Gradle. To execute the full build chain—which includes generating Smithy builds, producing Go client code, cleaning the target directory, and overlaying manual files—run the following command from the parent directory:

./gradlew :protocol-test-codegen:build

This process ensures that internal/protocoltest/ is populated with both auto-generated protocol tests and any hand-written manual files provided in the manual/ directory.

Use NewGetUsagePlanKeysPaginator to iterate through all pages of usage plan keys. The paginator handles the Position token management automatically.

Paginator Options

• Limit: The maximum number of results per page (Default: 25, Max: 500).
• StopOnDuplicateToken: If set to true, pagination stops if the service returns a token identical to the previous one.

Use the ListCodeSigningConfigsPaginator to automatically iterate through all pages of code signing configurations.

To use the paginator:

1. Call NewListCodeSigningConfigsPaginator with your client and input parameters.
2. Use HasMorePages() to check if more results are available.
3. Use NextPage(ctx) to retrieve the next batch of results.

You can configure the paginator using ListCodeSigningConfigsPaginatorOptions:

• Limit (int32): The maximum number of items to return per page.
• StopOnDuplicateToken (bool): If true, pagination stops if the service returns a token that matches the most recent token provided.

You can initialize an AppConfigData client in two ways:

1. From an existing AWS Config: Use NewFromConfig to create a client using a pre-configured aws.Config object. This is the recommended approach for most applications.
2. With custom options: Use New to provide a specific Options struct and additional functional options to configure behavior like custom endpoints, middleware, or retry logic.

Note that Options() returns a copy of the client configuration to prevent accidental mutations of the client's internal state.