SFTP / FTPS SERVER IN. AMAZON S3 OUT. NO SCRIPTS.

Give partners an SFTP server that lands files in your S3 bucket

DocEvent hosts an SFTP, SCP and FTPS server for you: partners upload to it with their own login and every completed upload is delivered into your Amazon S3 or S3-compatible bucket. Hosted SFTP-to-S3 ingestion with per-user credentials, an IP firewall, retries and a full audit trail - no server to run.
From
SFTP / FTPS Server
To
Amazon S3
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 SFTP / FTPS Server to Amazon S3 routing works

Source

SFTP / FTPS Server

DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
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 SFTP / FTPS Server

A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
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, Hetzner Object 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 SFTP / FTPS Server Amazon S3 channel.
  • Receive partner or customer deliveries over SFTP into S3 with no server to run
  • Replace a self-managed SFTP box or EC2 gateway in front of S3
  • Land uploads in S3-compatible stores too - Cloudflare R2, MinIO, B2, Wasabi
  • Give every sender their own login and IP allowlist, and audit every file
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or Amazon S3 side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
Destination:
Amazon S3
Delivery into any bucket that speaks the S3 API - Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage, Hetzner Object 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