Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 client for v3 authentication complient Go SDK #547

Closed
raunak-agarwal-flipkart opened this issue Feb 8, 2016 · 4 comments
Closed

S3 client for v3 authentication complient Go SDK #547

raunak-agarwal-flipkart opened this issue Feb 8, 2016 · 4 comments
Assignees
Labels
guidance Question that needs advice or information.

Comments

@raunak-agarwal-flipkart
Copy link

I need to implement Go client for s3 which is v3 authentication compliant. While going through the previous releases, I didn't find any particular mention of v3 authentication. Can somebody point to the relevant release and a sample Go client for the same.

@jasdel
Copy link
Contributor

jasdel commented Feb 8, 2016

Hi @raunak-agarwal-flipkart thanks for contacting us. The SDK does not implement the v3 authentication method. In general the SDK only supports v4, with the exception of v2 for SimpleDB.

The best references to the V3 authentication i could find is implementations in the AWS SDK for Ruby. There are the ruby signing implementations for HTTP and HTTPS protocols.

@jasdel jasdel added guidance Question that needs advice or information. closing-soon This issue will automatically close in 4 days unless further comments are made. labels Feb 8, 2016
@jasdel
Copy link
Contributor

jasdel commented Feb 16, 2016

@raunak-agarwal-flipkart Going to close this issue, please let us know if you still have any additional questions about this issue, or feedback.

@jasdel jasdel closed this as completed Feb 16, 2016
@Rauk
Copy link

Rauk commented Feb 21, 2016

@jasdel
Is there any other SDK for Go using v2? Sorry for the inactivity though.

@jasdel
Copy link
Contributor

jasdel commented Feb 23, 2016

Hi @Rauk the AWS SDK for Go is capable of using v2 signature for services and regions which support it, but v4 is prefered and will work in all AWS regions. Is there an AWS service you need to use V2 signing with, but unable to use v4? The signers are in the private/signers package path. If you would like to use a service with v2 you can modify the Sign request handler list to use the v2 signer instead.

Or are you looking for a standalone v2 request signer? The both SDK's signers are specific to the SDK's request structure.

@diehlaws diehlaws removed the closing-soon This issue will automatically close in 4 days unless further comments are made. label Oct 29, 2018
skotambkar pushed a commit to skotambkar/aws-sdk-go that referenced this issue May 20, 2021
…this (aws#547)

Updates the SDK's master branch to not depend on the Smithy prototype. This in development prototype and experiments are moved to the feature/SmithyAPIClient feature branch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance Question that needs advice or information.
Projects
None yet
Development

No branches or pull requests

4 participants