AZURE DATA LAKE PULL IN. AMAZON S3 OUT. NO SCRIPTS.

Move files from Azure Data Lake Gen2 to your S3 bucket

DocEvent polls a directory in your Azure Data Lake Storage Gen2 filesystem on a schedule and delivers each new file into your Amazon S3 or S3-compatible bucket. ADLS-to-S3 transfer with completed-file detection, no scripts and a full audit trail.
From
Azure Data Lake Pull
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 Azure Data Lake Pull to Amazon S3 routing works

Source

Azure Data Lake

DocEvent checks a folder in your Azure Data Lake Storage Gen2 filesystem on a schedule and collects new files. Requires a storage account with hierarchical namespace (HNS) enabled.
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 Azure Data Lake Pull

Scheduled polling of an Azure Data Lake Storage Gen2 filesystem using the storage account name and access key. Requires a storage account with the hierarchical namespace (HNS) enabled; flat (non-HNS) Blob storage accounts are not supported by this source. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
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 Azure Data Lake Pull Amazon S3 channel.
  • Bridge ADLS analytics output into an S3-based platform
  • Feed AWS workloads from an Azure data engineering pipeline
  • Migrate a hierarchical-namespace account to S3 while both stay live
  • Cross-cloud delivery on a schedule - no transfer tooling to run
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Azure Data Lake Pull or Amazon S3 side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Azure Data Lake
Scheduled polling of an Azure Data Lake Storage Gen2 filesystem using the storage account name and access key. Requires a storage account with the hierarchical namespace (HNS) enabled; flat (non-HNS) Blob storage accounts are not supported by this source. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks a folder in your Azure Data Lake Storage Gen2 filesystem on a schedule and collects new files. Requires a storage account with hierarchical namespace (HNS) enabled.
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

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

Get started for free