AMAZON S3 IN. DOCEVENT AGENT (ON-PREM) OUT. NO SCRIPTS.
Deliver S3 files into a folder on your own machine
When a file lands in Amazon S3, the DocEvent Agent saves it into a folder on your own machine. The agent connects outbound over TLS — no inbound ports, no VPN — and you pick the delivery folder from the web console. Every file acknowledged and audited.
From
Amazon S3
To
DocEvent Agent (on-prem)
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
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 DocEvent Agent (on-prem) routing works
Source
Amazon S3
Files arrive when objects are uploaded or created in an Amazon S3 bucket.
DocEvent Channel
routes · retries · logs
Destination
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a Amazon S3 → DocEvent Agent (on-prem) channel.
- Land processed cloud output on the machine that needs it
- Feed legacy applications that only read local directories with S3 data
- Distribute price lists, catalogues or configs from S3 to branch-office machines
- Pick the delivery folder remotely from the web console
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 sources to DocEvent Agent (on-prem)
- SFTP / FTPS Server → DocEvent Agent (on-prem)
- HTTP Upload → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- AS2 → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- GCS Blob Pull → DocEvent Agent (on-prem)
- Azure Blob Pull → DocEvent Agent (on-prem)
- Azure Files Pull → DocEvent Agent (on-prem)
- SharePoint → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)