SFTP and FTP for your Amazon S3 bucket

Give partners and systems an SFTP, FTPS, FTP or SCP endpoint that reads and writes straight into your own S3 bucket. No server to run, no VPC to configure, and the files never live on our servers.
SFTPFTPSFTPSCP
Client
Partner or app
DocEvent
Simple FTP Service
S3
Your bucket
Files stream straight through to your own Amazon S3 bucket — nothing is stored on our servers.

How it works

1
Connect your S3 bucket
Create an IAM user with access to the bucket and paste its access key and secret into DocEvent. Scope the policy to a single bucket or a prefix if you want the endpoint limited to part of it.
2
Create a user for each partner
Add an SFTP/FTPS/FTP user per partner or system, with a password or an SSH key and its own home directory. Lock it down with per-service IP allow and deny rules if you want it pinned to known addresses.
3
Hand over the hostname
Give them the DocEvent hostname and credentials. Files land in your bucket as they are uploaded, and every connection and transfer is recorded in the audit log.Prefer your own domain? Point a CNAME at the endpoint and partners connect to something like sftp.yourcompany.com instead.

Built for Amazon S3

Any S3-compatible store too

The same connector works with Cloudflare R2, Backblaze B2, Wasabi, MinIO, IBM COS, NetApp StorageGRID, Ceph and Cloudian — anything that speaks the S3 API, using its own endpoint URL.

Your bucket policies still apply

Versioning, Object Lock, SSE-KMS encryption, lifecycle rules to Glacier and region pinning are all yours and keep working. DocEvent authenticates and transfers; S3 remains the system of record.

Cheaper than a protocol-hour

AWS Transfer Family bills roughly US$219 a month per enabled protocol before any traffic. DocEvent bills per user and starts free for up to five.

Common questions

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

Get started for free