Deliver S3 files into an on-premise folder automatically
When a file lands in Amazon S3, DocEvent delivers it into a folder on your own server. The Filerouter agent connects outbound over HTTPS — no inbound ports, no VPN — and writes each file to the directory you choose, with an end-to-end audit trail.
From
Amazon S3
To
Filerouter (on-premise)
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How Amazon S3 to Filerouter (on-premise) routing works
Source
Amazon S3
Files arrive when objects are uploaded or created in an Amazon S3 bucket.
DocEvent Channel
routes · retries · logs
Destination
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
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 Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a Amazon S3 → Filerouter (on-premise) channel.
- Land processed cloud output on the on-premise server that needs it
- Feed legacy applications that only read from a local directory with S3 data
- Distribute price lists, catalogues or configs from S3 to branch-office servers
- Give a partner S3-triggered delivery straight onto their own machine
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 Filerouter (on-premise) 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:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.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 Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob Pull → Filerouter (on-premise)
- Azure Data Lake Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)