Get started
HTTP UPLOAD IN. AMAZON S3 OUT. NO SCRIPTS.

Accept HTTP uploads and store every file in your S3 bucket

Accept file uploads via HTTP POST and have each one delivered into your Amazon S3 or S3-compatible bucket - Cloudflare R2, MinIO, Backblaze B2, Wasabi and more. An upload API for your bucket with no presigned-URL code, no SDK, and a full audit trail.
From
HTTP Upload
To
Amazon S3
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.

How HTTP Upload to Amazon S3 routing works

Source

HTTP Upload

Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination

Amazon S3

Files are delivered into your Amazon S3 or S3-compatible bucket - Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
1

File arrives via HTTP Upload

REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
2

Channel routes it

DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3

Delivered to Amazon S3

Delivery into any bucket that speaks the S3 API - Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Authenticate with an access key, or on Amazon S3 let DocEvent assume an IAM role in your account so no long-lived credentials change hands. Configurable key prefix, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows.

Common use cases

Real workflows that teams automate with a HTTP Upload → Amazon S3 channel.
  • Give partners or apps an HTTPS upload endpoint that lands in your bucket
  • Collect uploads from web forms and devices into S3 without presigned-URL code
  • Feed an S3 data lake from systems that can only POST over HTTPS
  • Deliver into S3-compatible stores too - Cloudflare R2, MinIO, B2, Wasabi
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the HTTP Upload or Amazon S3 side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
HTTP Upload
REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
Destination:
Amazon S3
Delivery into any bucket that speaks the S3 API - Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Authenticate with an access key, or on Amazon S3 let DocEvent assume an IAM role in your account so no long-lived credentials change hands. Configurable key prefix, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows.
Files are delivered into your Amazon S3 or S3-compatible bucket - Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages

Related channel integrations

Other destinations from HTTP Upload
Other sources to Amazon S3
View all 126 channel integrations

You focus on integration,
we'll focus on delivery.

Get started for free