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

Replicate S3 files to another bucket - any account, any provider

When an object lands in your Amazon S3 bucket, DocEvent delivers a copy into another S3 or S3-compatible bucket - a different account, a different provider (Cloudflare R2, MinIO, Backblaze B2, Wasabi), or a partner's bucket entirely. No replication rules, no Lambda, full audit trail.
From
Amazon S3
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 Amazon S3 to Amazon S3 routing works

Source

Amazon S3

Files arrive when objects are uploaded or created in an Amazon S3 bucket.
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 Amazon S3

Triggered by S3 object-created events delivered via SNS. Supports all S3-compatible storage.
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 Amazon S3 → Amazon S3 channel.
  • Copy objects between AWS accounts without cross-account bucket policies
  • Mirror an Amazon S3 bucket into Cloudflare R2, Wasabi, Backblaze B2 or MinIO
  • Hand a partner event-driven delivery straight into their own bucket
  • Migrate object storage providers while both buckets stay live
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Amazon S3 or Amazon S3 side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Amazon S3
Triggered by S3 object-created events delivered via SNS. Supports all S3-compatible storage.
Files arrive when objects are uploaded or created in an Amazon S3 bucket.
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 Amazon S3
Other sources to Amazon S3
View all 126 channel integrations

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

Get started for free