S3 pre-signed URLs can be used to easily and reliably implement file download and upload in web and mobile applications. This article explores S3 pre-signed URLs in great detail, illustrating the pros and cons and the various different ways of using them. Rich of code examples and illustrations

Henrique Leite

GitHub

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Implementing reliable and scalable file upload and download workflows can be challenging, especially with serverless architectures due to size and time constraints. AWS S3 pre-signed URLs offer a solution by allowing temporary access to specific S3 objects without needing permanent credentials. These URLs can be used for various use cases, such as user uploads, large file downloads, and secure file sharing. The article explains different types of pre-signed URLs (GET, PUT, POST), their limitations, and security considerations. Code examples for generating pre-signed URLs using the AWS JavaScript SDK are also provided.

The illustrated guide to S3 pre-signed URLs

How to create pre-signed URLs with the JavaScript SDK

CORS and using pre-signed URLs in the browser