You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
S3 presign cli allow url generated more than 7 days (--expires-in greater than 604800) #5464
Describe the bug
aws s3 presign --expires-in 604801 will allow url to be generated. But when view the url, S3 will said that url is not valid as it's expiring in more than 7 days.
Error message:
X-Amz-Expires must be less than a week (in seconds); that is, the given X-Amz-Expires must be less than 604800 seconds
SDK version number
aws --version
aws-cli/2.0.17 Python/3.7.4 Darwin/19.6.0 botocore/2.0.0dev21
Hi @kienpham2000, this maximum time limit is specific to S3 presigned URLs with the SigV4 signing method. Previously (SigV2) a presigned URL could be valid indefinitely. I'm going to mark this as a documentation issue to note the maximum value in the client documentation that is also present in the S3 documentation.
Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. Because it has been longer than one year since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
kdaily commentedon Aug 12, 2020
Looking into this, thanks!
kdaily commentedon Aug 13, 2020
Hi @kienpham2000, this maximum time limit is specific to S3 presigned URLs with the SigV4 signing method. Previously (SigV2) a presigned URL could be valid indefinitely. I'm going to mark this as a documentation issue to note the maximum value in the client documentation that is also present in the S3 documentation.
kpx-dev commentedon Aug 13, 2020
Thanks @kdaily , didn't know that :).
github-actions commentedon Aug 13, 2021
Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. Because it has been longer than one year since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.
tim-finnigan commentedon Nov 19, 2021
Closing this as the PR mentioned above was merged.
github-actions commentedon Nov 19, 2021
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.