https://github.com/aws/aws-sdk-go

aws aws-sdk go

Last synced: about 1 month ago

Repository metadata:

AWS SDK for the Go programming language.


Owner metadata:


Committers metadata

Last synced: about 2 months ago

Total Commits: 4,615
Total Committers: 316
Avg Commits per committer: 14.604
Development Distribution Score (DDS): 0.753

Commits in past year: 231
Committers in past year: 13
Avg Commits per committer in past year: 17.769
Development Distribution Score (DDS) in past year: 0.199

Name Email Commits
aws-sdk-go-automation 4****n 1141
Jason Del Ponte d****j@g****m 1049
Loren Segal l****l@a****m 413
xibz i****g@g****m 383
Coda Hale c****a@s****m 262
awssdkgo a****o@a****m 217
awssdkgo a****o@a****m 168
Sean McGrail m****s@a****m 81
Baron Von Ben Powell p****e@a****m 79
awssdkgo a****o@a****m 70
awssdkgo a****o@a****m 68
Jason Del Ponte 9****l 43
Shantanu Kotambkar 5****r 38
Jason Del Ponte j****l@a****m 25
Luc Talatinian l****x@a****m 24
Tianyi Wang w****y@a****m 20
Alex Diehl a****s@g****m 20
Eddy Ilangovan e****i@a****m 13
Luc Talatinian 1****s 10
Eren Yeager 9****t 10
Bob Potter b****r@g****m 10
Loren Segal l****l@s****a 10
Chris Broglie c****e@z****m 8
John Jeffery j****y@s****u 8
JordonPhillips p****n@a****m 8
Nick Craig-Wood n****k@c****m 8
awssdkgo a****o@a****m 8
Isaiah Vita 8****a 8
TANABE Ken-ichi n****n@t****g 7
Aaron Todd a****d 6
and 286 more...

Issue and Pull Request metadata

Last synced: about 1 month ago


Package metadata

go: github.com/aws/aws-sdk-go

Package sdk is the official AWS SDK for the Go programming language. The AWS SDK for Go provides APIs and utilities that developers can use to build Go applications that use AWS services, such as Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Simple Storage Service (Amazon S3). The SDK removes the complexity of coding directly against a web service interface. It hides a lot of the lower-level plumbing, such as authentication, request retries, and error handling. The SDK also includes helpful utilities on top of the AWS APIs that add additional capabilities and functionality. For example, the Amazon S3 Download and Upload Manager will automatically split up large objects into multiple parts and transfer them concurrently. See the s3manager package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/s3/s3manager/ Checkout the Getting Started Guide and API Reference Docs detailed the SDK's components and details on each AWS client the SDK supports. The Getting Started Guide provides examples and detailed description of how to get setup with the SDK. https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/welcome.html The API Reference Docs include a detailed breakdown of the SDK's components such as utilities and AWS clients. Use this as a reference of the Go types included with the SDK, such as AWS clients, API operations, and API parameters. https://docs.aws.amazon.com/sdk-for-go/api/ The SDK is composed of two main components, SDK core, and service clients. The SDK core packages are all available under the aws package at the root of the SDK. Each client for a supported AWS service is available within its own package under the service folder at the root of the SDK. aws - SDK core, provides common shared types such as Config, Logger, and utilities to make working with API parameters easier. awserr - Provides the error interface that the SDK will use for all errors that occur in the SDK's processing. This includes service API response errors as well. The Error type is made up of a code and message. Cast the SDK's returned error type to awserr.Error and call the Code method to compare returned error to specific error codes. See the package's documentation for additional values that can be extracted such as RequestId. credentials - Provides the types and built in credentials providers the SDK will use to retrieve AWS credentials to make API requests with. Nested under this folder are also additional credentials providers such as stscreds for assuming IAM roles, and ec2rolecreds for EC2 Instance roles. endpoints - Provides the AWS Regions and Endpoints metadata for the SDK. Use this to lookup AWS service endpoint information such as which services are in a region, and what regions a service is in. Constants are also provided for all region identifiers, e.g UsWest2RegionID for "us-west-2". session - Provides initial default configuration, and load configuration from external sources such as environment and shared credentials file. request - Provides the API request sending, and retry logic for the SDK. This package also includes utilities for defining your own request retryer, and configuring how the SDK processes the request. service - Clients for AWS services. All services supported by the SDK are available under this folder. The SDK includes the Go types and utilities you can use to make requests to AWS service APIs. Within the service folder at the root of the SDK you'll find a package for each AWS service the SDK supports. All service clients follows a common pattern of creation and usage. When creating a client for an AWS service you'll first need to have a Session value constructed. The Session provides shared configuration that can be shared between your service clients. When service clients are created you can pass in additional configuration via the aws.Config type to override configuration provided by in the Session to create service client instances with custom configuration. Once the service's client is created you can use it to make API requests the AWS service. These clients are safe to use concurrently. In the AWS SDK for Go, you can configure settings for service clients, such as the log level and maximum number of retries. Most settings are optional; however, for each service client, you must specify a region and your credentials. The SDK uses these values to send requests to the correct AWS region and sign requests with the correct credentials. You can specify these values as part of a session or as environment variables. See the SDK's configuration guide for more information. https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html See the session package documentation for more information on how to use Session with the SDK. https://docs.aws.amazon.com/sdk-for-go/api/aws/session/ See the Config type in the aws package for more information on configuration options. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config When using the SDK you'll generally need your AWS credentials to authenticate with AWS services. The SDK supports multiple methods of supporting these credentials. By default the SDK will source credentials automatically from its default credential chain. See the session package for more information on this chain, and how to configure it. The common items in the credential chain are the following: Environment Credentials - Set of environment variables that are useful when sub processes are created for specific roles. Shared Credentials file (~/.aws/credentials) - This file stores your credentials based on a profile name and is useful for local development. EC2 Instance Role Credentials - Use EC2 Instance Role to assign credentials to application running on an EC2 instance. This removes the need to manage credential files in production. Credentials can be configured in code as well by setting the Config's Credentials value to a custom provider or using one of the providers included with the SDK to bypass the default credential chain and use a custom one. This is helpful when you want to instruct the SDK to only use a specific set of credentials or providers. This example creates a credential provider for assuming an IAM role, "myRoleARN" and configures the S3 service client to use that role for API requests. See the credentials package documentation for more information on credential providers included with the SDK, and how to customize the SDK's usage of credentials. https://docs.aws.amazon.com/sdk-for-go/api/aws/credentials The SDK has support for the shared configuration file (~/.aws/config). This support can be enabled by setting the environment variable, "AWS_SDK_LOAD_CONFIG=1", or enabling the feature in code when creating a Session via the Option's SharedConfigState parameter. In addition to the credentials you'll need to specify the region the SDK will use to make AWS API requests to. In the SDK you can specify the region either with an environment variable, or directly in code when a Session or service client is created. The last value specified in code wins if the region is specified multiple ways. To set the region via the environment variable set the "AWS_REGION" to the region you want to the SDK to use. Using this method to set the region will allow you to run your application in multiple regions without needing additional code in the application to select the region. The endpoints package includes constants for all regions the SDK knows. The values are all suffixed with RegionID. These values are helpful, because they reduce the need to type the region string manually. To set the region on a Session use the aws package's Config struct parameter Region to the AWS region you want the service clients created from the session to use. This is helpful when you want to create multiple service clients, and all of the clients make API requests to the same region. See the endpoints package for the AWS Regions and Endpoints metadata. https://docs.aws.amazon.com/sdk-for-go/api/aws/endpoints/ In addition to setting the region when creating a Session you can also set the region on a per service client bases. This overrides the region of a Session. This is helpful when you want to create service clients in specific regions different from the Session's region. See the Config type in the aws package for more information and additional options such as setting the Endpoint, and other service client configuration options. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config Once the client is created you can make an API request to the service. Each API method takes a input parameter, and returns the service response and an error. The SDK provides methods for making the API call in multiple ways. In this list we'll use the S3 ListObjects API as an example for the different ways of making API requests. ListObjects - Base API operation that will make the API request to the service. ListObjectsRequest - API methods suffixed with Request will construct the API request, but not send it. This is also helpful when you want to get a presigned URL for a request, and share the presigned URL instead of your application making the request directly. ListObjectsPages - Same as the base API operation, but uses a callback to automatically handle pagination of the API's response. ListObjectsWithContext - Same as base API operation, but adds support for the Context pattern. This is helpful for controlling the canceling of in flight requests. See the Go standard library context package for more information. This method also takes request package's Option functional options as the variadic argument for modifying how the request will be made, or extracting information from the raw HTTP response. ListObjectsPagesWithContext - same as ListObjectsPages, but adds support for the Context pattern. Similar to ListObjectsWithContext this method also takes the request package's Option function option types as the variadic argument. In addition to the API operations the SDK also includes several higher level methods that abstract checking for and waiting for an AWS resource to be in a desired state. In this list we'll use WaitUntilBucketExists to demonstrate the different forms of waiters. WaitUntilBucketExists. - Method to make API request to query an AWS service for a resource's state. Will return successfully when that state is accomplished. WaitUntilBucketExistsWithContext - Same as WaitUntilBucketExists, but adds support for the Context pattern. In addition these methods take request package's WaiterOptions to configure the waiter, and how underlying request will be made by the SDK. The API method will document which error codes the service might return for the operation. These errors will also be available as const strings prefixed with "ErrCode" in the service client's package. If there are no errors listed in the API's SDK documentation you'll need to consult the AWS service's API documentation for the errors that could be returned. Pagination helper methods are suffixed with "Pages", and provide the functionality needed to round trip API page requests. Pagination methods take a callback function that will be called for each page of the API's response. Waiter helper methods provide the functionality to wait for an AWS resource state. These methods abstract the logic needed to to check the state of an AWS resource, and wait until that resource is in a desired state. The waiter will block until the resource is in the state that is desired, an error occurs, or the waiter times out. If a resource times out the error code returned will be request.WaiterResourceNotReadyErrorCode. This example shows a complete working Go file which will upload a file to S3 and use the Context pattern to implement timeout logic that will cancel the request if it takes too long. This example highlights how to use sessions, create a service client, make a request, handle the error, and process the response.

go: github.com/aws/aws-Sdk-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/aws/aws-Sdk-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.49.15 (published 12 months ago)
  • Last Synced: 2024-10-29T20:47:37.432Z (about 2 months ago)
  • Versions: 1,825
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent repos count: 1.622%
    • Average: 4.057%
    • Dependent packages count: 6.492%
go: github.com/aws/Aws-sdk-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/aws/Aws-sdk-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.49.15 (published 12 months ago)
  • Last Synced: 2024-10-29T20:47:31.985Z (about 2 months ago)
  • Versions: 1,775
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent repos count: 1.622%
    • Average: 4.057%
    • Dependent packages count: 6.492%
go: github.com/aws/aws-sdk-go/private/protocol/query

Package query provides serialization of AWS query requests, and responses.

go: github.com/aws/aws-sdk-go/aws/awsutil

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/awsutil#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:19.639Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/aws/auth/bearer

go: github.com/aws/aws-sdk-go/service/secretsmanager

Package secretsmanager provides the client and types for making API requests to AWS Secrets Manager. Amazon Web Services Secrets Manager provides a service to enable you to store, manage, and retrieve, secrets. This guide provides descriptions of the Secrets Manager API. For more information about using this service, see the Amazon Web Services Secrets Manager User Guide (https://docs.aws.amazon.com/secretsmanager/latest/userguide/introduction.html). This version of the Secrets Manager API Reference documents the Secrets Manager API version 2017-10-17. For a list of endpoints, see Amazon Web Services Secrets Manager endpoints (https://docs.aws.amazon.com/secretsmanager/latest/userguide/asm_access.html#endpoints). We welcome your feedback. Send your comments to [email protected] (mailto:[email protected]), or post your feedback and questions in the Amazon Web Services Secrets Manager Discussion Forum (http://forums.aws.amazon.com/forum.jspa?forumID=296). For more information about the Amazon Web Services Discussion Forums, see Forums Help (http://forums.aws.amazon.com/help.jspa). Amazon Web Services Secrets Manager supports Amazon Web Services CloudTrail, a service that records Amazon Web Services API calls for your Amazon Web Services account and delivers log files to an Amazon S3 bucket. By using information that's collected by Amazon Web Services CloudTrail, you can determine the requests successfully made to Secrets Manager, who made the request, when it was made, and so on. For more about Amazon Web Services Secrets Manager and support for Amazon Web Services CloudTrail, see Logging Amazon Web Services Secrets Manager Events with Amazon Web Services CloudTrail (https://docs.aws.amazon.com/secretsmanager/latest/userguide/monitoring.html#monitoring_cloudtrail) in the Amazon Web Services Secrets Manager User Guide. To learn more about CloudTrail, including enabling it and find your log files, see the Amazon Web Services CloudTrail User Guide (https://docs.aws.amazon.com/awscloudtrail/latest/userguide/what_is_cloud_trail_top_level.html). See https://docs.aws.amazon.com/goto/WebAPI/secretsmanager-2017-10-17 for more information on this service. See secretsmanager package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/secretsmanager/ To contact AWS Secrets Manager with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Secrets Manager client SecretsManager for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/secretsmanager/#New

go: github.com/aws/aws-sdk-go/aws/credentials/stscreds

Package stscreds are credential Providers to retrieve STS AWS credentials. STS provides multiple ways to retrieve credentials which can be used when making future AWS service API operation calls. The SDK will ensure that per instance of credentials.Credentials all requests to refresh the credentials will be synchronized. But, the SDK is unable to ensure synchronous usage of the AssumeRoleProvider if the value is shared between multiple Credentials, Sessions or service clients. To assume an IAM role using STS with the SDK you can create a new Credentials with the SDKs's stscreds package. To assume an IAM role with a MFA token you can either specify a MFA token code directly or provide a function to prompt the user each time the credentials need to refresh the role's credentials. Specifying the TokenCode should be used for short lived operations that will not need to be refreshed, and when you do not want to have direct control over the user provides their MFA token. With TokenCode the AssumeRoleProvider will be not be able to refresh the role's credentials. To assume an IAM role with MFA for longer running tasks where the credentials may need to be refreshed setting the TokenProvider field of AssumeRoleProvider will allow the credential provider to prompt for new MFA token code when the role's credentials need to be refreshed. The StdinTokenProvider function is available to prompt on stdin to retrieve the MFA token code from the user. You can also implement custom prompts by satisfing the TokenProvider function signature. Using StdinTokenProvider with multiple AssumeRoleProviders, or Credentials will have undesirable results as the StdinTokenProvider will not be synchronized. A single Credentials with an AssumeRoleProvider can be shared safely.

go: github.com/aws/aws-sdk-go/service/sfn

Package sfn provides the client and types for making API requests to AWS Step Functions. Step Functions coordinates the components of distributed applications and microservices using visual workflows. You can use Step Functions to build applications from individual components, each of which performs a discrete function, or task, allowing you to scale and change applications quickly. Step Functions provides a console that helps visualize the components of your application as a series of steps. Step Functions automatically triggers and tracks each step, and retries steps when there are errors, so your application executes predictably and in the right order every time. Step Functions logs the state of each step, so you can quickly diagnose and debug any issues. Step Functions manages operations and underlying infrastructure to ensure your application is available at any scale. You can run tasks on Amazon Web Services, your own servers, or any system that has access to Amazon Web Services. You can access and use Step Functions using the console, the Amazon Web Services SDKs, or an HTTP API. For more information about Step Functions, see the Step Functions Developer Guide (https://docs.aws.amazon.com/step-functions/latest/dg/welcome.html) . If you use the Step Functions API actions using Amazon Web Services SDK integrations, make sure the API actions are in camel case and parameter names are in Pascal case. For example, you could use Step Functions API action startSyncExecution and specify its parameter as StateMachineArn. See https://docs.aws.amazon.com/goto/WebAPI/states-2016-11-23 for more information on this service. See sfn package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/sfn/ To contact AWS Step Functions with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Step Functions client SFN for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/sfn/#New

go: github.com/aws/aws-sdk-go/service/ssooidc

Package ssooidc provides the client and types for making API requests to AWS SSO OIDC. IAM Identity Center OpenID Connect (OIDC) is a web service that enables a client (such as CLI or a native application) to register with IAM Identity Center. The service also enables the client to fetch the user’s access token upon successful authentication and authorization with IAM Identity Center. IAM Identity Center uses the sso and identitystore API namespaces. Before you begin using this guide, we recommend that you first review the following important information about how the IAM Identity Center OIDC service works. The IAM Identity Center OIDC service currently implements only the portions of the OAuth 2.0 Device Authorization Grant standard (https://tools.ietf.org/html/rfc8628 (https://tools.ietf.org/html/rfc8628)) that are necessary to enable single sign-on authentication with the CLI. With older versions of the CLI, the service only emits OIDC access tokens, so to obtain a new token, users must explicitly re-authenticate. To access the OIDC flow that supports token refresh and doesn’t require re-authentication, update to the latest CLI version (1.27.10 for CLI V1 and 2.9.0 for CLI V2) with support for OIDC token refresh and configurable IAM Identity Center session durations. For more information, see Configure Amazon Web Services access portal session duration (https://docs.aws.amazon.com/singlesignon/latest/userguide/configure-user-session.html). The access tokens provided by this service grant access to all Amazon Web Services account entitlements assigned to an IAM Identity Center user, not just a particular application. The documentation in this guide does not describe the mechanism to convert the access token into Amazon Web Services Auth (“sigv4”) credentials for use with IAM-protected Amazon Web Services service endpoints. For more information, see GetRoleCredentials (https://docs.aws.amazon.com/singlesignon/latest/PortalAPIReference/API_GetRoleCredentials.html) in the IAM Identity Center Portal API Reference Guide. For general information about IAM Identity Center, see What is IAM Identity Center? (https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the IAM Identity Center User Guide. See https://docs.aws.amazon.com/goto/WebAPI/sso-oidc-2019-06-10 for more information on this service. See ssooidc package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/ssooidc/ To contact AWS SSO OIDC with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS SSO OIDC client SSOOIDC for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/ssooidc/#New

go: github.com/aws/aws-sdk-go/aws/credentials

Package credentials provides credential retrieval and management The Credentials is the primary method of getting access to and managing credentials Values. Using dependency injection retrieval of the credential values is handled by a object which satisfies the Provider interface. By default the Credentials.Get() will cache the successful result of a Provider's Retrieve() until Provider.IsExpired() returns true. At which point Credentials will call Provider's Retrieve() to get new credential Value. The Provider is responsible for determining when credentials Value have expired. It is also important to note that Credentials will always call Retrieve the first time Credentials.Get() is called. Example of using the environment variable credentials. Example of forcing credentials to expire and be refreshed on the next Get(). This may be helpful to proactively expire credentials and refresh them sooner than they would naturally expire on their own. Each Provider built into this package also provides a helper method to generate a Credentials pointer setup with the provider. To use a custom Provider just create a type which satisfies the Provider interface and pass it to the NewCredentials method.

go: github.com/aws/aws-sdk-go/internal/shareddefaults

go: github.com/aws/aws-sdk-go/private/protocol/eventstream/eventstreamapi

go: github.com/aws/aws-sdk-go/aws/awserr

Package awserr represents API error interface accessors for the SDK.

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/awserr#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:28.505Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/private/protocol

go: github.com/aws/aws-sdk-go/aws/crr

go: github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds

go: github.com/aws/aws-sdk-go/aws/client/metadata

go: github.com/aws/aws-sdk-go/internal/sync/singleflight

Package singleflight provides a duplicate function call suppression mechanism.

go: github.com/aws/aws-sdk-go/internal/sdkrand

go: github.com/aws/aws-sdk-go/aws/signer/v4

Package v4 implements signing for AWS V4 signer Provides request signing for request that need to be signed with AWS V4 Signatures. Generally using the signer outside of the SDK should not require any additional logic when using Go v1.5 or higher. The signer does this by taking advantage of the URL.EscapedPath method. If your request URI requires additional escaping you may need to use the URL.Opaque to define what the raw URI should be sent to the service as. The signer will first check the URL.Opaque field, and use its value if set. The signer does require the URL.Opaque field to be set in the form of: The leading "//" and hostname are required or the URL.Opaque escaping will not work correctly. If URL.Opaque is not set the signer will fallback to the URL.EscapedPath() method and using the returned value. If you're using Go v1.4 you must set URL.Opaque if the URI path needs escaping. If URL.Opaque is not set with Go v1.5 the signer will fallback to URL.Path. AWS v4 signature validation requires that the canonical string's URI path element must be the URI escaped form of the HTTP request's path. http://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html The Go HTTP client will perform escaping automatically on the request. Some of these escaping may cause signature validation errors because the HTTP request differs from the URI path or query that the signature was generated. https://golang.org/pkg/net/url/#URL.EscapedPath Because of this, it is recommended that when using the signer outside of the SDK that explicitly escaping the request prior to being signed is preferable, and will help prevent signature validation errors. This can be done by setting the URL.Opaque or URL.RawPath. The SDK will use URL.Opaque first and then call URL.EscapedPath() if Opaque is not set. If signing a request intended for HTTP2 server, and you're using Go 1.6.2 through 1.7.4 you should use the URL.RawPath as the pre-escaped form of the request URL. https://github.com/golang/go/issues/16847 points to a bug in Go pre 1.8 that fails to make HTTP2 requests using absolute URL in the HTTP message. URL.Opaque generally will force Go to make requests with absolute URL. URL.RawPath does not do this, but RawPath must be a valid escaping of Path or url.EscapedPath will ignore the RawPath escaping. Test `TestStandaloneSign` provides a complete example of using the signer outside of the SDK and pre-escaping the URI path.

go: github.com/aws/aws-sdk-go/aws/client

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/client#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:34.877Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/aws/request

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/request#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:37.749Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/internal/sdkmath

go: github.com/aws/aws-sdk-go/aws/session

Package session provides configuration for the SDK's service clients. Sessions can be shared across service clients that share the same base configuration. Sessions are safe to use concurrently as long as the Session is not being modified. Sessions should be cached when possible, because creating a new Session will load all configuration values from the environment, and config files each time the Session is created. Sharing the Session value across all of your service clients will ensure the configuration is loaded the fewest number of times possible. By default NewSession will only load credentials from the shared credentials file (~/.aws/credentials). If the AWS_SDK_LOAD_CONFIG environment variable is set to a truthy value the Session will be created from the configuration values from the shared config (~/.aws/config) and shared credentials (~/.aws/credentials) files. Using the NewSessionWithOptions with SharedConfigState set to SharedConfigEnable will create the session as if the AWS_SDK_LOAD_CONFIG environment variable was set. The Session will attempt to load configuration and credentials from the environment, configuration files, and other credential sources. The order configuration is loaded in is: The Environment variables for credentials will have precedence over shared config even if SharedConfig is enabled. To override this behavior, and use shared config credentials instead specify the session.Options.Profile, (e.g. when using credential_source=Environment to assume a role). Creating a Session without additional options will load credentials region, and profile loaded from the environment and shared config automatically. See, "Environment Variables" section for information on environment variables used by Session. When creating Sessions optional aws.Config values can be passed in that will override the default, or loaded, config values the Session is being created with. This allows you to provide additional, or case based, configuration as needed. Use NewSessionWithOptions to provide additional configuration driving how the Session's configuration will be loaded. Such as, specifying shared config profile, or override the shared config state, (AWS_SDK_LOAD_CONFIG). You can add handlers to a session to decorate API operation, (e.g. adding HTTP headers). All clients that use the Session receive a copy of the Session's handlers. For example, the following request handler added to the Session logs every requests made. By default the SDK will only load the shared credentials file's (~/.aws/credentials) credentials values, and all other config is provided by the environment variables, SDK defaults, and user provided aws.Config values. If the AWS_SDK_LOAD_CONFIG environment variable is set, or SharedConfigEnable option is used to create the Session the full shared config values will be loaded. This includes credentials, region, and support for assume role. In addition the Session will load its configuration from both the shared config file (~/.aws/config) and shared credentials file (~/.aws/credentials). Both files have the same format. If both config files are present the configuration from both files will be read. The Session will be created from configuration values from the shared credentials file (~/.aws/credentials) over those in the shared config file (~/.aws/config). Credentials are the values the SDK uses to authenticating requests with AWS Services. When specified in a file, both aws_access_key_id and aws_secret_access_key must be provided together in the same file to be considered valid. They will be ignored if both are not present. aws_session_token is an optional field that can be provided in addition to the other two fields. The role_arn field allows you to configure the SDK to assume an IAM role using a set of credentials from another source. Such as when paired with static credentials, "profile_source", "credential_process", or "credential_source" fields. If "role_arn" is provided, a source of credentials must also be specified, such as "source_profile", "credential_source", or "credential_process". The SDK supports assuming a role with MFA token. If "mfa_serial" is set, you must also set the Session Option.AssumeRoleTokenProvider. The Session will fail to load if the AssumeRoleTokenProvider is not specified. To setup Assume Role outside of a session see the stscreds.AssumeRoleProvider documentation. When a Session is created several environment variables can be set to adjust how the SDK functions, and what configuration data it loads when creating Sessions. All environment values are optional, but some values like credentials require multiple of the values to set or the partial values will be ignored. All environment variable values are strings unless otherwise noted. Environment configuration values. If set both Access Key ID and Secret Access Key must be provided. Session Token and optionally also be provided, but is not required. Region value will instruct the SDK where to make service API requests to. If is not provided in the environment the region must be provided before a service client request is made. Profile name the SDK should load use when loading shared config from the configuration files. If not provided "default" will be used as the profile name. SDK load config instructs the SDK to load the shared config in addition to shared credentials. This also expands the configuration loaded so the shared credentials will have parity with the shared config file. This also enables Region and Profile support for the AWS_DEFAULT_REGION and AWS_DEFAULT_PROFILE env values as well. Shared credentials file path can be set to instruct the SDK to use an alternative file for the shared credentials. If not set the file will be loaded from $HOME/.aws/credentials on Linux/Unix based systems, and %USERPROFILE%\.aws\credentials on Windows. Shared config file path can be set to instruct the SDK to use an alternative file for the shared config. If not set the file will be loaded from $HOME/.aws/config on Linux/Unix based systems, and %USERPROFILE%\.aws\config on Windows. Path to a custom Credentials Authority (CA) bundle PEM file that the SDK will use instead of the default system's root CA bundle. Use this only if you want to replace the CA bundle the SDK uses for TLS requests. Enabling this option will attempt to merge the Transport into the SDK's HTTP client. If the client's Transport is not a http.Transport an error will be returned. If the Transport's TLS config is set this option will cause the SDK to overwrite the Transport's TLS config's RootCAs value. If the CA bundle file contains multiple certificates all of them will be loaded. The Session option CustomCABundle is also available when creating sessions to also enable this feature. CustomCABundle session option field has priority over the AWS_CA_BUNDLE environment variable, and will be used if both are set. Setting a custom HTTPClient in the aws.Config options will override this setting. To use this option and custom HTTP client, the HTTP client needs to be provided when creating the session. Not the service client. The SDK supports the environment and session option being configured with Client TLS certificates that are sent as a part of the client's TLS handshake for client authentication. If used, both Cert and Key values are required. If one is missing, or either fail to load the contents of the file an error will be returned. HTTP Client's Transport concrete implementation must be a http.Transport or creating the session will fail. This can also be configured via the session.Options ClientTLSCert and ClientTLSKey. The endpoint of the EC2 IMDS client can be configured via the environment variable, AWS_EC2_METADATA_SERVICE_ENDPOINT when creating the client with a Session. See Options.EC2IMDSEndpoint for more details. If using an URL with an IPv6 address literal, the IPv6 address component must be enclosed in square brackets. The custom EC2 IMDS endpoint can also be specified via the Session options. The SDK can be configured to resolve an endpoint with certain capabilities such as FIPS and DualStack. You can configure a FIPS endpoint using an environment variable, shared config ($HOME/.aws/config), or programmatically. To configure a FIPS endpoint set the environment variable set the AWS_USE_FIPS_ENDPOINT to true or false to enable or disable FIPS endpoint resolution. To configure a FIPS endpoint using shared config, set use_fips_endpoint to true or false to enable or disable FIPS endpoint resolution. To configure a FIPS endpoint programmatically You can configure a DualStack endpoint using an environment variable, shared config ($HOME/.aws/config), or programmatically. To configure a DualStack endpoint set the environment variable set the AWS_USE_DUALSTACK_ENDPOINT to true or false to enable or disable DualStack endpoint resolution. To configure a DualStack endpoint using shared config, set use_dualstack_endpoint to true or false to enable or disable DualStack endpoint resolution. To configure a DualStack endpoint programmatically

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/session#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:38.670Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/service/sso/ssoiface

Package ssoiface provides an interface to enable mocking the AWS Single Sign-On service client for testing your code. It is important to note that this interface will have breaking changes when the service model is updated and adds new API operations, paginators, and waiters.

go: github.com/aws/aws-sdk-go/service/dynamodb/expression

Package expression provides types and functions to create Amazon DynamoDB Expression strings, ExpressionAttributeNames maps, and ExpressionAttributeValues maps. The package represents the various DynamoDB Expressions as structs named accordingly. For example, ConditionBuilder represents a DynamoDB Condition Expression, an UpdateBuilder represents a DynamoDB Update Expression, and so on. The following example shows a sample ConditionExpression and how to build an equilvalent ConditionBuilder In order to retrieve the formatted DynamoDB Expression strings, call the getter methods on the Expression struct. To create the Expression struct, call the Build() method on the Builder struct. Because some input structs, such as QueryInput, can have multiple DynamoDB Expressions, multiple structs representing various DynamoDB Expressions can be added to the Builder struct. The following example shows a generic usage of the whole package. The ExpressionAttributeNames and ExpressionAttributeValues member of the input struct must always be assigned when using the Expression struct because all item attribute names and values are aliased. That means that if the ExpressionAttributeNames and ExpressionAttributeValues member is not assigned with the corresponding Names() and Values() methods, the DynamoDB operation will run into a logic error.

go: github.com/aws/aws-sdk-go/internal/ini

Package ini is an LL(1) parser for configuration files. Below is the BNF that describes this parser

go: github.com/aws/aws-sdk-go/private/protocol/rest

Package rest provides RESTful serialization of AWS requests and responses.

go: github.com/aws/aws-sdk-go/aws/credentials/endpointcreds

Package endpointcreds provides support for retrieving credentials from an arbitrary HTTP endpoint. The credentials endpoint Provider can receive both static and refreshable credentials that will expire. Credentials are static when an "Expiration" value is not provided in the endpoint's response. Static credentials will never expire once they have been retrieved. The format of the static credentials response: Refreshable credentials will expire within the "ExpiryWindow" of the Expiration value in the response. The format of the refreshable credentials response: Errors should be returned in the following format and only returned with 400 or 500 HTTP status codes.

go: github.com/aws/aws-sdk-go/service/xray

Package xray provides the client and types for making API requests to AWS X-Ray. Amazon Web Services X-Ray provides APIs for managing debug traces and retrieving service maps and other data created by processing those traces. See https://docs.aws.amazon.com/goto/WebAPI/xray-2016-04-12 for more information on this service. See xray package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/xray/ To contact AWS X-Ray with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS X-Ray client XRay for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/xray/#New

go: github.com/aws/aws-sdk-go/private/protocol/json/jsonutil

Package jsonutil provides JSON serialization of AWS requests and responses.

go: github.com/aws/aws-sdk-go/service/sso

Package sso provides the client and types for making API requests to AWS Single Sign-On. AWS IAM Identity Center (successor to AWS Single Sign-On) Portal is a web service that makes it easy for you to assign user access to IAM Identity Center resources such as the AWS access portal. Users can get AWS account applications and roles assigned to them and get federated into the application. Although AWS Single Sign-On was renamed, the sso and identitystore API namespaces will continue to retain their original name for backward compatibility purposes. For more information, see IAM Identity Center rename (https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html#renamed). This reference guide describes the IAM Identity Center Portal operations that you can call programatically and includes detailed information on data types and errors. AWS provides SDKs that consist of libraries and sample code for various programming languages and platforms, such as Java, Ruby, .Net, iOS, or Android. The SDKs provide a convenient way to create programmatic access to IAM Identity Center and other AWS services. For more information about the AWS SDKs, including how to download and install them, see Tools for Amazon Web Services (http://aws.amazon.com/tools/). See https://docs.aws.amazon.com/goto/WebAPI/sso-2019-06-10 for more information on this service. See sso package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/sso/ To contact AWS Single Sign-On with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Single Sign-On client SSO for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/sso/#New

go: github.com/aws/aws-sdk-go/private/protocol/restjson

Package restjson provides RESTful JSON serialization of AWS requests and responses.

go: github.com/aws/aws-sdk-go/private/protocol/xml/xmlutil

Package xmlutil provides XML serialization of AWS requests and responses.

go: github.com/aws/aws-sdk-go/internal/strings

go: github.com/aws/aws-sdk-go/aws/ec2metadata

Package ec2metadata provides the client for making API calls to the EC2 Metadata service. This package's client can be disabled completely by setting the environment variable "AWS_EC2_METADATA_DISABLED=true". This environment variable set to true instructs the SDK to disable the EC2 Metadata client. The client cannot be used while the environment variable is set to true, (case insensitive). The endpoint of the EC2 IMDS client can be configured via the environment variable, AWS_EC2_METADATA_SERVICE_ENDPOINT when creating the client with a Session. See aws/session#Options.EC2IMDSEndpoint for more details.

go: github.com/aws/aws-sdk-go/aws/defaults

Package defaults is a collection of helpers to retrieve the SDK's default configuration and handlers. Generally this package shouldn't be used directly, but session.Session instead. This package is useful when you need to reset the defaults of a session or service client to the SDK defaults before setting additional parameters.

go: github.com/aws/aws-sdk-go/internal/sdkio

go: github.com/aws/aws-sdk-go/aws/endpoints

Package endpoints provides the types and functionality for defining regions and endpoints, as well as querying those definitions. The SDK's Regions and Endpoints metadata is code generated into the endpoints package, and is accessible via the DefaultResolver function. This function returns a endpoint Resolver will search the metadata and build an associated endpoint if one is found. The default resolver will search all partitions known by the SDK. e.g AWS Standard (aws), AWS China (aws-cn), and AWS GovCloud (US) (aws-us-gov). . Casting the Resolver returned by DefaultResolver to a EnumPartitions interface will allow you to get access to the list of underlying Partitions with the Partitions method. This is helpful if you want to limit the SDK's endpoint resolving to a single partition, or enumerate regions, services, and endpoints in the partition. The endpoints package also gives you the ability to use your own logic how endpoints are resolved. This is a great way to define a custom endpoint for select services, without passing that logic down through your code. If a type implements the Resolver interface it can be used to resolve endpoints. To use this with the SDK's Session and Config set the value of the type to the EndpointsResolver field of aws.Config when initializing the session, or service client. In addition the ResolverFunc is a wrapper for a func matching the signature of Resolver.EndpointFor, converting it to a type that satisfies the Resolver interface.

go: github.com/aws/aws-sdk-go/private/protocol/query/queryutil

go: github.com/aws/aws-sdk-go/private/protocol/eventstream

go: github.com/aws/aws-sdk-go/aws/csm

Package csm provides the Client Side Monitoring (CSM) client which enables sending metrics via UDP connection to the CSM agent. This package provides control options, and configuration for the CSM client. The client can be controlled manually, or automatically via the SDK's Session configuration. The CSM client can be enabled automatically via SDK's Session configuration. The SDK's session configuration enables the CSM client if the AWS_CSM_PORT environment variable is set to a non-empty value. The configuration options for the CSM client via the SDK's session configuration are: AWS_CSM_PORT=<port number> The port number the CSM agent will receive metrics on. AWS_CSM_HOST=<hostname or ip> The hostname, or IP address the CSM agent will receive metrics on. Without port number. The CSM client can be started, paused, and resumed manually. The Start function will enable the CSM client to publish metrics to the CSM agent. It is safe to call Start concurrently, but if Start is called additional times with different ClientID or address it will panic. When controlling the CSM client manually, you must also inject its request handlers into the SDK's Session configuration for the SDK's API clients to publish metrics. Once the CSM client has been enabled the Get function will return a Reporter value that you can use to pause and resume the metrics published to the CSM agent. If Get function is called before the reporter is enabled with the Start function or via SDK's Session configuration nil will be returned. The Pause method can be called to stop the CSM client publishing metrics to the CSM agent. The Continue method will resume metric publishing.

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/csm#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:07.764Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/service/sts

Package sts provides the client and types for making API requests to AWS Security Token Service. Security Token Service (STS) enables you to request temporary, limited-privilege credentials for users. This guide provides descriptions of the STS API. For more information about using this service, see Temporary Security Credentials (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html). See https://docs.aws.amazon.com/goto/WebAPI/sts-2011-06-15 for more information on this service. See sts package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/sts/ To contact AWS Security Token Service with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Security Token Service client STS for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/sts/#New

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/service/sts#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:45:09.539Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/aws/credentials/processcreds

Package processcreds is a credential Provider to retrieve `credential_process` credentials. WARNING: The following describes a method of sourcing credentials from an external process. This can potentially be dangerous, so proceed with caution. Other credential providers should be preferred if at all possible. If using this option, you should make sure that the config file is as locked down as possible using security best practices for your operating system. You can use credentials from a `credential_process` in a variety of ways. One way is to setup your shared config file, located in the default location, with the `credential_process` key and the command you want to be called. You also need to set the AWS_SDK_LOAD_CONFIG environment variable (e.g., `export AWS_SDK_LOAD_CONFIG=1`) to use the shared config file. Creating a new session will use the credential process to retrieve credentials. NOTE: If there are credentials in the profile you are using, the credential process will not be used. Another way to use the `credential_process` method is by using `credentials.NewCredentials()` and providing a command to be executed to retrieve credentials: You can set a non-default timeout for the `credential_process` with another constructor, `credentials.NewCredentialsTimeout()`, providing the timeout. To set a one minute timeout: If you need more control, you can set any configurable options in the credentials using one or more option functions. For example, you can set a two minute timeout, a credential duration of 60 minutes, and a maximum stdout buffer size of 2k. You can also use your own `exec.Cmd`:

go: github.com/aws/aws-sdk-go/aws/credentials/ssocreds

Package ssocreds provides a credential provider for retrieving temporary AWS credentials using an SSO access token. IMPORTANT: The provider in this package does not initiate or perform the AWS SSO login flow. The SDK provider expects that you have already performed the SSO login flow using AWS CLI using the "aws sso login" command, or by some other mechanism. The provider must find a valid non-expired access token for the AWS SSO user portal URL in ~/.aws/sso/cache. If a cached token is not found, it is expired, or the file is malformed an error will be returned. You can use configure AWS SSO credentials from the AWS shared configuration file by providing the specifying the required keys in the profile: For example, the following defines a profile "devsso" and specifies the AWS SSO parameters that defines the target account, role, sign-on portal, and the region where the user portal is located. Note: all SSO arguments must be provided, or an error will be returned. Using the config module, you can load the AWS SDK shared configuration, and specify that this profile be used to retrieve credentials. For example: You can programmatically construct the AWS SSO Provider in your application, and provide the necessary information to load and retrieve temporary credentials using an access token from ~/.aws/sso/cache. Configuring the AWS CLI to use AWS Single Sign-On: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html AWS Single Sign-On User Guide: https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html

go: github.com/aws/aws-sdk-go/service/lambda

Package lambda provides the client and types for making API requests to AWS Lambda. Lambda is a compute service that lets you run code without provisioning or managing servers. Lambda runs your code on a high-availability compute infrastructure and performs all of the administration of the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring and logging. With Lambda, you can run code for virtually any type of application or backend service. For more information about the Lambda service, see What is Lambda (https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) in the Lambda Developer Guide. The Lambda API Reference provides information about each of the API methods, including details about the parameters in each API request and response. You can use Software Development Kits (SDKs), Integrated Development Environment (IDE) Toolkits, and command line tools to access the API. For installation instructions, see Tools for Amazon Web Services (http://aws.amazon.com/tools/). For a list of Region-specific endpoints that Lambda supports, see Lambda endpoints and quotas (https://docs.aws.amazon.com/general/latest/gr/lambda-service.html/) in the Amazon Web Services General Reference.. When making the API calls, you will need to authenticate your request by providing a signature. Lambda supports signature version 4. For more information, see Signature Version 4 signing process (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) in the Amazon Web Services General Reference.. Because Amazon Web Services SDKs use the CA certificates from your computer, changes to the certificates on the Amazon Web Services servers can cause connection failures when you attempt to use an SDK. You can prevent these failures by keeping your computer's CA certificates and operating system up-to-date. If you encounter this issue in a corporate environment and do not manage your own computer, you might need to ask an administrator to assist with the update process. The following list shows minimum operating system and Java versions: Microsoft Windows versions that have updates from January 2005 or later installed contain at least one of the required CAs in their trust list. Mac OS X 10.4 with Java for Mac OS X 10.4 Release 5 (February 2007), Mac OS X 10.5 (October 2007), and later versions contain at least one of the required CAs in their trust list. Red Hat Enterprise Linux 5 (March 2007), 6, and 7 and CentOS 5, 6, and 7 all contain at least one of the required CAs in their default trusted CA list. Java 1.4.2_12 (May 2006), 5 Update 2 (March 2005), and all later versions, including Java 6 (December 2006), 7, and 8, contain at least one of the required CAs in their default trusted CA list. When accessing the Lambda management console or Lambda API endpoints, whether through browsers or programmatically, you will need to ensure your client machines support any of the following CAs: Amazon Root CA 1 Starfield Services Root Certificate Authority - G2 Starfield Class 2 Certification Authority Root certificates from the first two authorities are available from Amazon trust services (https://www.amazontrust.com/repository/), but keeping your computer up-to-date is the more straightforward solution. To learn more about ACM-provided certificates, see Amazon Web Services Certificate Manager FAQs. (http://aws.amazon.com/certificate-manager/faqs/#certificates) See https://docs.aws.amazon.com/goto/WebAPI/lambda-2015-03-31 for more information on this service. See lambda package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/lambda/ To contact AWS Lambda with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Lambda client Lambda for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/lambda/#New

go: github.com/aws/aws-sdk-go/aws

Package aws provides the core SDK's utilities and shared types. Use this package's utilities to simplify setting and reading API operations parameters. This package includes a helper conversion utility for each scalar type the SDK's API use. These utilities make getting a pointer of the scalar, and dereferencing a pointer easier. Each conversion utility comes in two forms. Value to Pointer and Pointer to Value. The Pointer to value will safely dereference the pointer and return its value. If the pointer was nil, the scalar's zero value will be returned. The value to pointer functions will be named after the scalar type. So get a *string from a string value use the "String" function. This makes it easy to to get pointer of a literal string value, because getting the address of a literal requires assigning the value to a variable first. In addition to scalars the aws package also includes conversion utilities for map and slice for commonly types used in API parameters. The map and slice conversion functions use similar naming pattern as the scalar conversion functions. The SDK will use the http.DefaultClient if a HTTP client is not provided to the SDK's Session, or service client constructor. This means that if the http.DefaultClient is modified by other components of your application the modifications will be picked up by the SDK as well. In some cases this might be intended, but it is a better practice to create a custom HTTP Client to share explicitly through your application. You can configure the SDK to use the custom HTTP Client by setting the HTTPClient value of the SDK's Config type when creating a Session or service client. Package aws provides core functionality for making requests to AWS services.

  • Homepage: https://github.com/aws/aws-sdk-go
  • Documentation: https://pkg.go.dev/github.com/aws/aws-sdk-go/aws#section-documentation
  • Licenses: Apache-2.0
  • Latest release:
  • Last Synced: 2024-11-11T02:44:58.869Z (about 1 month ago)
  • Versions: 0
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Docker Downloads: 9
  • Rankings:
    • Dependent packages count: 6.151%
    • Average: 6.357%
    • Dependent repos count: 6.563%
go: github.com/aws/aws-sdk-go/private/protocol/jsonrpc

Package jsonrpc provides JSON RPC utilities for serialization of AWS requests and responses.

go: github.com/aws/aws-sdk-go/service/sts/stsiface

Package stsiface provides an interface to enable mocking the AWS Security Token Service service client for testing your code. It is important to note that this interface will have breaking changes when the service model is updated and adds new API operations, paginators, and waiters.

go: github.com/aws/aws-sdk-go/service/dynamodb

Package dynamodb provides the client and types for making API requests to Amazon DynamoDB. Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. DynamoDB lets you offload the administrative burdens of operating and scaling a distributed database, so that you don't have to worry about hardware provisioning, setup and configuration, replication, software patching, or cluster scaling. With DynamoDB, you can create database tables that can store and retrieve any amount of data, and serve any level of request traffic. You can scale up or scale down your tables' throughput capacity without downtime or performance degradation, and use the Amazon Web Services Management Console to monitor resource utilization and performance metrics. DynamoDB automatically spreads the data and traffic for your tables over a sufficient number of servers to handle your throughput and storage requirements, while maintaining consistent and fast performance. All of your data is stored on solid state disks (SSDs) and automatically replicated across multiple Availability Zones in an Amazon Web Services Region, providing built-in high availability and data durability. See https://docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10 for more information on this service. See dynamodb package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/ To contact Amazon DynamoDB with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the Amazon DynamoDB client DynamoDB for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/#New Utility helpers to marshal and unmarshal AttributeValue to and from Go types can be found in the dynamodbattribute sub package. This package provides specialized functions for the common ways of working with AttributeValues. Such as map[string]*AttributeValue, []*AttributeValue, and directly with *AttributeValue. This is helpful for marshaling Go types for API operations such as PutItem, and unmarshaling Query and Scan APIs' responses. See the dynamodbattribute package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/dynamodbattribute/ The expression package provides utility types and functions to build DynamoDB expression for type safe construction of API ExpressionAttributeNames, and ExpressionAttribute Values. The package represents the various DynamoDB Expressions as structs named accordingly. For example, ConditionBuilder represents a DynamoDB Condition Expression, an UpdateBuilder represents a DynamoDB Update Expression, and so on. See the expression package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/dynamodb/expression/

go: github.com/aws/aws-sdk-go/aws/corehandlers

DO NOT EDIT

go: github.com/aws/aws-sdk-go/internal/sdkuri

go: github.com/aws/aws-sdk-go/service/dynamodb/dynamodbattribute

Package dynamodbattribute provides marshaling and unmarshaling utilities to convert between Go types and dynamodb.AttributeValues. These utilities allow you to marshal slices, maps, structs, and scalar values to and from dynamodb.AttributeValue. These are useful when marshaling Go value tyes to dynamodb.AttributeValue for DynamoDB requests, or unmarshaling the dynamodb.AttributeValue back into a Go value type. To marshal a Go type to a dynamodbAttributeValue you can use the Marshal functions in the dynamodbattribute package. There are specialized versions of these functions for collections of Attributevalue, such as maps and lists. The following example uses MarshalMap to convert the Record Go type to a dynamodb.AttributeValue type and use the value to make a PutItem API request. To unmarshal a dynamodb.AttributeValue to a Go type you can use the Unmarshal functions in the dynamodbattribute package. There are specialized versions of these functions for collections of Attributevalue, such as maps and lists. The following example will unmarshal the DynamoDB's Scan API operation. The Items returned by the operation will be unmarshaled into the slice of Records Go type. The ConvertTo, ConvertToList, ConvertToMap, ConvertFrom, ConvertFromMap and ConvertFromList methods have been deprecated. The Marshal and Unmarshal functions should be used instead. The ConvertTo|From marshallers do not support BinarySet, NumberSet, nor StringSets, and will incorrectly marshal binary data fields in structs as base64 strings. The Marshal and Unmarshal functions correct this behavior, and removes the reliance on encoding.json. `json` struct tags are still supported. In addition support for a new struct tag `dynamodbav` was added. Support for the json.Marshaler and json.Unmarshaler interfaces have been removed and replaced with dynamodbattribute.Marshaler and dynamodbattribute.Unmarshaler interfaces. The Unmarshal functions are backwards compatible with data marshalled by ConvertTo*, but the reverse is not true: objects marshalled using Marshal are not necessarily usable by ConvertFrom*. This backward compatibility is intended to assist with incremental upgrading of data following a switch away from the Convert* family of functions. `time.Time` is marshaled as RFC3339 format.

go: github.com/AWS/aws-sdk-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/AWS/aws-sdk-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.49.15 (published 12 months ago)
  • Last Synced: 2024-11-11T02:44:52.203Z (about 1 month ago)
  • Versions: 1,862
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent packages count: 6.999%
    • Average: 8.173%
    • Dependent repos count: 9.346%
go: github.com/Aws/Aws-sdk-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/Aws/Aws-sdk-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.49.15 (published 12 months ago)
  • Last Synced: 2024-10-29T20:47:04.125Z (about 2 months ago)
  • Versions: 1,825
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent packages count: 6.999%
    • Average: 8.173%
    • Dependent repos count: 9.346%
go: github.com/Aws/aws-sdk-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/Aws/aws-sdk-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.49.15 (published 12 months ago)
  • Last Synced: 2024-10-29T16:39:43.195Z (about 2 months ago)
  • Versions: 1,862
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent packages count: 6.999%
    • Average: 8.173%
    • Dependent repos count: 9.346%
go: github.com/aws/aws-SDK-go

  • Homepage:
  • Documentation: https://pkg.go.dev/github.com/aws/aws-SDK-go#section-documentation
  • Licenses: apache-2.0
  • Latest release: v1.51.13 (published 9 months ago)
  • Last Synced: 2024-11-11T02:44:50.473Z (about 1 month ago)
  • Versions: 1,862
  • Dependent Packages: 0
  • Dependent Repositories: 0
  • Rankings:
    • Dependent packages count: 6.999%
    • Average: 8.173%
    • Dependent repos count: 9.346%

Dependencies

.github/workflows/closed-issue-message.yml actions
  • aws-actions/closed-issue-message v1 composite
.github/workflows/go.yml actions
  • actions/checkout v2 composite
  • actions/setup-go v2 composite
.github/workflows/stale_issues.yml actions
  • aws-actions/stale-issue-cleanup v4 composite
Gopkg.lock go
  • github.com/jmespath/go-jmespath c2b33e84
Gopkg.toml go
  • github.com/jmespath/go-jmespath *
go.mod go
  • github.com/jmespath/go-jmespath v0.4.0
  • github.com/pkg/errors v0.9.1
  • golang.org/x/net v0.1.0
go.sum go
  • github.com/davecgh/go-spew v1.1.0
  • github.com/jmespath/go-jmespath v0.4.0
  • github.com/jmespath/go-jmespath/internal/testify v1.5.1
  • github.com/pkg/errors v0.9.1
  • github.com/pmezard/go-difflib v1.0.0
  • github.com/stretchr/objx v0.1.0
  • github.com/yuin/goldmark v1.4.13
  • golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2
  • golang.org/x/crypto v0.0.0-20210921155107-089bfa567519
  • golang.org/x/mod v0.6.0-dev.0.20220419223038-86c51ed26bb4
  • golang.org/x/net v0.0.0-20190620200207-3b0461eec859
  • golang.org/x/net v0.0.0-20210226172049-e18ecbb05110
  • golang.org/x/net v0.0.0-20220722155237-a158d28d115b
  • golang.org/x/net v0.1.0
  • golang.org/x/sync v0.0.0-20190423024810-112230192c58
  • golang.org/x/sync v0.0.0-20220722155255-886fb9371eb4
  • golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a
  • golang.org/x/sys v0.0.0-20201119102817-f84b799fce68
  • golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1
  • golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a
  • golang.org/x/sys v0.0.0-20220722155257-8c9f86f7a55f
  • golang.org/x/sys v0.1.0
  • golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1
  • golang.org/x/term v0.0.0-20210927222741-03fcf44c2211
  • golang.org/x/term v0.1.0
  • golang.org/x/text v0.3.0
  • golang.org/x/text v0.3.3
  • golang.org/x/text v0.3.7
  • golang.org/x/text v0.4.0
  • golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e
  • golang.org/x/tools v0.0.0-20191119224855-298f0cb1881e
  • golang.org/x/tools v0.1.12
  • golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7
  • gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405
  • gopkg.in/yaml.v2 v2.2.8