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.

Sign up for GitHub

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

Jump to bottom

The correct documentation to use to create a pre-signed Dynamodb http request #298

Closed
mutuelinvestor opened this issue Jun 29, 2015 · 2 comments
Closed

The correct documentation to use to create a pre-signed Dynamodb http request #298

mutuelinvestor opened this issue Jun 29, 2015 · 2 comments
Labels
guidance Question that needs advice or information.

Comments

@mutuelinvestor
Copy link

I'm trying to use the Dynamodb API to access information via http. I successfully used the HMAC function to create the signature, but I'm have difficulty creating the actual request. My hope is to use a pre-signed get request for Dynamodb and I was hoping someone could point me to the correct documentation.

I've read several different alternatives and it is a bit confusing.

  1. http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html
  2. http://docs.aws.amazon.com/general/latest/gr/sigv4-add-signature-to-request.html
  3. http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/MakingHTTPReests.html

Thanks for you input.
@jasdel
Copy link
Contributor

jasdel commented Jun 29, 2015

Hi @mutuelinvestor are you use the the SDK to create pre-signed URLS? If so the Request.Presign() method will return the pre-signed URL. If you're still encountering problem you might be running into #94

If you are looking to pre-sign the URL yourself the documents linked are a good resource to start with.

@jasdel jasdel added guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jun 29, 2015
@jasdel
Copy link
Contributor

jasdel commented Aug 5, 2015

Hi @mutuelinvestor going to close this issue, Please reopen or get back to us if you're still having issues with your requests.

@jasdel jasdel closed this as completed Aug 5, 2015
@diehlaws diehlaws removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jan 30, 2019
skotambkar pushed a commit to skotambkar/aws-sdk-go that referenced this issue May 20, 2021
@jasdel
Refactoring SDK's code generation patterns (aws#298)
e6b1343 
Updates the SDK's code generation pattern with several improvements to improve discoverability, and consistency in client naming.

* Standardizing of the service model's ServiceID for the name of the
service client's package.

* Adds an operation `Response` type that is in addition from the
operation's `Output` parameters. This prevents collisions between SDK
response metadata, marshaling methods, and modeled output parameters.

* Refactor service client package's client name to be named Client
instead of the service's short name. Removes the stuttering of client
package and type, (e.g. s3.S3 becomes s3.Client)

* Fix service endpoint lookups use the the service's modeled EndpointID
instead of inconsistent service name.

* Generate API operations into their own file instead of all operations
and parameter types being generated into a single file. This improves
readability of individual source files for documentation reference.
Non-input/output types are still generated into a single file. This change also fixes several occurrences of incorrectly generated API operation input/output type names.

* Removes aws/endpoints Service identifiers from endpoint list. These
were not actually service identifiers, but EndpointsID. In addition the
values modeled by the services were unstable, and could change causing
breaking changes in the SDK's aws/endpoints package. The service
client package's `EndpointsID` const should be used instead.

* Move Paginate method from the initialized Request type into its own
construct via the New<RequestType>Paginator function to create the
request paginator. (e.g. req.Paginate becomes NewListObjectsPaginator(req))

Fix aws#294 aws#282 aws#275
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
guidance Question that needs advice or information.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mutuelinvestor @jasdel @diehlaws