aws-sdk-ruby icon indicating copy to clipboard operation
aws-sdk-ruby copied to clipboard

Unsigned request option

Open wjordan opened this issue 8 years ago • 9 comments

The AWS CLI has a --no-sign-request option which I've found useful for anonymously downloading S3 objects with public-read ACLs, and I'd like to see a similar feature added to the Ruby SDK.

Although it's currently possible to pass an S3 object's #public_url to open or another Ruby HTTP client, I'd like to be able to leverage the AWS SDK's existing functionality for optimized downloading, file integrity verification and network-error retries, but without requiring credentials to be provided when not necessary.

wjordan avatar Apr 01 '16 00:04 wjordan

This is something I've been considering adding to the SDK recently. I'm still considering what the mechanism would be to allow for unauthenticated requests.

trevorrowe avatar Apr 01 '16 00:04 trevorrowe

Added to feature request backlog.

awood45 avatar Jun 03 '16 17:06 awood45

@awood45 is this still in the request backlog ?

Techbrunch avatar Jan 01 '18 15:01 Techbrunch

Reopening - deprecating usage of Feature Requests backlog markdown file.

mullermp avatar Oct 21 '19 22:10 mullermp

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

github-actions[bot] avatar Oct 21 '20 00:10 github-actions[bot]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

github-actions[bot] avatar Oct 22 '21 00:10 github-actions[bot]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

github-actions[bot] avatar Oct 23 '22 00:10 github-actions[bot]

Hey @mullermp, is this still in the feature backlog?

yashdave31 avatar Mar 19 '24 10:03 yashdave31

Yes, but it's not prioritized. I think that there is a workaround however. The Clients support an undocumented unsigned_operations key. I can't guarantee the backwards compatibility for it going forward (like in a new major version), but you can do something like this:

Aws::S3::Client.new(unsigned_operations: [:get_object]).get_object(bucket: 'bucket', key: 'test')

In the future we are trying to do pluggable signers, and in a case like this, it would be an AnonymousSigner object but that is a long term goal.

mullermp avatar Mar 19 '24 13:03 mullermp