Skip to content

Allow any S3 verb when creating pre-signed URL#8864

Closed
cartermckinnon wants to merge 1 commit intoaws:v2from
cartermckinnon:v2
Closed

Allow any S3 verb when creating pre-signed URL#8864
cartermckinnon wants to merge 1 commit intoaws:v2from
cartermckinnon:v2

Conversation

@cartermckinnon
Copy link
Copy Markdown

@cartermckinnon cartermckinnon commented Aug 13, 2024

Description of changes:

Adds the ability create pre-signed S3 URL's for PUT/DELETE/HEAD/etc.

Example:

PRESIGNED_URL=$(aws s3 presign s3://my-bucket/foo.txt --verb put)
curl --upload-file foo.txt $PRESIGNED_URL

PRESIGNED_URL=$(aws s3 presign s3://my-bucket/foo.txt --verb delete)
curl -X DELETE $PRESIGNED_URL

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@cartermckinnon cartermckinnon changed the title Allow any S3 verb when creating pre-signed URL [WIP] Allow any S3 verb when creating pre-signed URL Aug 13, 2024
@cartermckinnon cartermckinnon changed the title [WIP] Allow any S3 verb when creating pre-signed URL Allow any S3 verb when creating pre-signed URL Aug 13, 2024
@cartermckinnon
Copy link
Copy Markdown
Author

The couple of PR checks that failed look like flakes to me 🤷

@huangyxi
Copy link
Copy Markdown

huangyxi commented Jul 2, 2025

Thanks for your contribution!
I feel that --method (#9181) is slightly more appropriate than alternatives like --verb, --client-method (#3979) or presign-put (#3050, #6993), as this action has been referred to as a "method" in the HTTP specifications, from RFC1945: HTTP/1.0 in 1996 to RFC9110: HTTP Semantics in 2022.
That said, I'm happy with any naming choice — just hoping someone with write permissions can merge this feature soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants