Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
S3 : Hide Bucket name and Key path in the URL
See original GitHub issueWhen I use the method generate_presigned_url the resulting url contains my bucket name and path to the object and I am quite paranoid of exposing them!
Is there a way to generate a temp url that will not have the path and bucket name ?
PS: I also tried generate_url [boto] but in vain.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to hide AWS S3 Bucket URL with custom CNAME
Use the CloudFront name in Route53. Do not use CNAME, but rather use A type, and set it up as an Alias. For...
Read more >Virtual hosting of buckets - Amazon Simple Storage Service
For more information, see Customizing Amazon S3 URLs with CNAME records. This example uses the following: Bucket Name ‐ example.com. Key name ‐...
Read more >How to shorten and hide my access IDs for an AWS S3 URL
You can't hide the access ID's. If they're not there, you don't have access. If you want nicer URL's for S3 objects you...
Read more >How to Allow Public Access to an Amazon S3 Bucket & ...
1. From the bucket list, click on the bucket name again. Select the Permissions tab again, but this time go to the Bucket...
Read more >Mask the Long S3 URL
1. Log into your Amazon S3 account and navigate to the S3 dashboard · 2. Create a new bucket and name it. ·...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you Kylenap for your response.
I am worried about the privacy! with temp url anyone can know my bucket hierarchies which I don’t want to expose. Is there a way to generated a url with bucket name and path encrypted ?
Sounds good. However, I do not think even that would be possible to implement in general because the implementation must follow the S3 spec. According to the spec, we must sign with the actual name of the bucket and key name. If the S3 spec allowed for this, then we could add the ability to obfuscate the bucket/object in the generated presigned url but that is not possible as of now.