AMAZON S3 IN. AZURE BLOB OUT. NO SCRIPTS.
Replicate Amazon S3 files into Azure Blob Storage
When an object lands in your Amazon S3 bucket, DocEvent delivers a copy into your Azure Blob Storage container - standard or Data Lake Gen2 accounts alike. Event-driven S3-to-Azure replication with no AzCopy jobs, no scripts and a full audit trail.
From
Amazon S3
To
Azure Blob
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
GCSpush
Azure Blobpush
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 Azure Blob routing works
Source
Amazon S3
Files arrive when objects are uploaded or created in an Amazon S3 bucket.
DocEvent Channel
routes · retries · logs
Destination
Azure Blob
Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.
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 Azure Blob
Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.
Common use cases
Real workflows that teams automate with a Amazon S3 → Azure Blob channel.
- Mirror an S3 bucket into a Blob container for Azure-side workloads
- Hand an Azure-based partner delivery straight into their container
- Migrate from AWS to Azure while both stores stay live
- Keep a cross-cloud copy of critical objects as they arrive
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 Azure Blob 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:
Azure Blob
Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.
Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.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 sources to Azure Blob
- HTTP Upload → Azure Blob
- Email → Azure Blob
- AS2 → Azure Blob
- Filerouter (on-premise) → Azure Blob
- FTP Pull → Azure Blob
- SFTP Pull → Azure Blob
- S3 Compatible (pull) → Azure Blob
- GCS Blob Pull → Azure Blob
- Azure Blob Pull → Azure Blob
- Azure Data Lake Pull → Azure Blob
- Azure Files Pull → Azure Blob
- SharePoint → Azure Blob
- DocEvent Agent (on-prem) → Azure Blob