Chapter 128: Upload with a presigned URL

Core Idea

This article provides guidance for webapps wanting to allow users to upload videos and other assets. We recommend to generate a presigned URL server-side that allows a user to directly upload a file into your cloud storage without having to pass the file through your server.

Key Concepts

• Why use presigned URL?
• AWS Example
• Permissions
• Presigning URLs
• Next.js example code
• Performing the Uploading
• Using fetch()
• Tracking the upload progress

Code Examples

[
  {
    "AllowedHeaders": ["*"],
    "AllowedMethods": ["PUT"],
    "AllowedOrigins": ["*"],
    "ExposeHeaders": [],
    "MaxAgeSeconds": 3000
  }
]

• What it demonstrates: Usage pattern for Upload with a presigned URL from the official docs.

Key Takeaways

1. Understand why use presigned url? when working with Upload with a presigned URL.
2. Understand aws example when working with Upload with a presigned URL.
3. Understand permissions when working with Upload with a presigned URL.
4. Understand presigning urls when working with Upload with a presigned URL.
5. Understand next.js example code when working with Upload with a presigned URL.

Connects To

• Chromium Flags: related page in the Rendering & SSR section.
• Compare ssr: related page in the Rendering & SSR section.
• Dataset Render: related page in the Rendering & SSR section.