- Newest
- Most votes
- Most comments
Hi Deepti,
You can use presigned URLs to generate a URL that can be used to access your Amazon S3 buckets. When you create a presigned URL, you associate it with a specific action. You can share the URL, and anyone with access to it can perform the action embedded in the URL as if they were the original signing user. The URL will expire and no longer work when it reaches its expiration time.
For more information about this feature, please follow the link below: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html
Can have 2 options
- Use presigned url for uplod to S3 - https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html
- Use Cognito for user authentication, once authenticated pass the token to API gateway and then using that create a Lambda function to generate a unique URL for that user. The 2nd options is more secure and can access only user assigned objects.
Thanks for your help. I implemented presigned URLs and made the bucket private. It is working perfectly without exposing s3 resources. I believe this is exactly what I needed to do in this scenario. Once again thank you.
Relevant content
- asked 5 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago