-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to generate long-living pre-signed URL #8551
Comments
Hi @fade2black, thanks for reaching out. Could you be more specific about how you're trying to access the object once you've created the URL, and how you're using AWS CLI in this process? Thanks! |
@RyanFitzSimmonsAK Thank you for a quick reply. 😀 |
Lately I've left two comments regarding |
@fade2black, your comments in this thread are not acceptable behavior in this community. You must follow the guidelines outlined in our Code of Conduct in order to participate in this repository. Please consider this your final warning on this. You've filed this issue against the AWS CLI, but you are describing actions taken in the AWS Console (website). In order for the folks that work on the CLI to help you, you'll need to tell us how you're using the CLI. That's what we meant when we asked for reproduction steps in our issue template. If you can't reproduce this with CLI commands, we will be unable to help you here. I tried following your reproduction steps: in a private S3 bucket, create a presigned URL for 7 hours. The URL is copied to my clipboard, and I am able to access the object using that URL. Please help us understand what's breaking for you. |
@kellertk |
You're not wrong in that it would be better if we can respond to issues more quickly. Unfortunately, I'm not able to go back in time and answer your question on Feb 27. Your feedback on issue responsiveness has been noted, but the best we can do is try and help you right now. Please help me help you. You've described in your report that you are unable to click through the AWS console and create a working presigned URL for an object in S3. I just tried this a few moments ago and was able to download my object without problems, even from a bucket with public access disabled. I can't seem to reproduce the behavior you're seeing, which is why we need more detail from you.
|
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. 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 or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Describe the bug
I have a pdf file object in my private s3 bucket. Then I go to
Object Actions
and thenShare with a presigned URL
.Then I choose
Hours
and enter 7 (meaning 7 hours) and it automatically copies the URL into my clipboard.Expected Behavior
To be available at least for one hour.
Current Behavior
When I try to access the object (from browser) using the presigned URL it says that the token is expired.
Reproduction Steps
NA
Possible Solution
No response
Additional Information/Context
No response
CLI version used
aws-cli/2.13.3 Python/3.11.4
Environment details (OS name and version, etc.)
MacOS
The text was updated successfully, but these errors were encountered: