Closed trivikr closed 4 years ago
In v2, we accept expires
param - number in seconds after which presigned URL should expire
Some history in v3:
expires
was initially added as Date|string|number https://github.com/aws/aws-sdk-js-v3/pull/28expires
was renamed to expiration
without changing the type https://github.com/aws/aws-sdk-js-v3/pull/36The S3 operations except both Date/time for Expires
parameter though
SDKs that accept expires in seconds for presign API:
SDKs which accept dates for presigned URLs:
Renaming the param to expiresIn
just like CLI/python/Ruby so that it's self-explanatory
Is your feature request related to a problem? Please describe.
Describe the solution you'd like Allow SDK customer just to pass number in seconds after which the presigned URL should expire.
signingDate
, then they just passexpires
seconds after which the URL should expire.signingDate
, then they just passexpires
seconds after which URL should expire.In both the cases, customer doesn't have to compute
expiration
Date|string|numberDescribe alternatives you've considered Compute expiration Date|string|number, and pass while calling presign API
Update: param name will be changed to
expiresIn
as per findings in https://github.com/aws/aws-sdk-js-v3/issues/1035#issuecomment-602816992