Prevent long-term S3 presigned URL#7
Merged
SwaraGandhi merged 3 commits intoaws-samples:mainfrom Mar 31, 2025
Merged
Conversation
SwaraGandhi
approved these changes
Mar 31, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a service-specific control for Amazon S3.
A presigned URL uses security credentials to grant time-limited permission to download or upload S3 objects.
Customers typically use presigned URLs to share private objects with time-limited access.
The generation of a presigned URL is a client-side operation. This control, applied via RCPs, helps to set the maximum expected signature age for a presigned URL and prevents unexpectedly long-term presigned URLs.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.