Generating signed URLs should be done via `put` about s3-resource HOT 5 OPEN

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #131941803 Generating signed URLs should be done via put

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

from s3-resource.

+1 the expires_in portion would also benefit our team as we are running into the 24 hour expiration on signed URLs when re-triggering jobs that use a cached resource that has already passed the 24 hour expiration window.

from s3-resource.

That seems so... static. From my point of view the signature on the S3 url has nothing to do with the resource the url represents. I would rather see the cached resource expire and the signed url regenerated after a configurable time ( on resource get ).

from s3-resource.

The cached resource expiring would help us in one sense for immediate usages of the signed URLs.
However, many times we want to be able to download using that signed URL more than a day later for historical purposes, so we would need the expires_in portion.

from s3-resource.

@amilkh I think a combination of both would be desirable. But I don't know if cache expiration is even possible currently.

from s3-resource.