SFTP to S3
Managed SFTP for your own S3 bucket
Your files stay in your bucket. Firepipe runs the SFTP layer. Connect S3 or an S3-compatible store, create per-user logins, and give people and systems a standard SFTP hostname without running an SFTP server.
Bring your own bucket · scoped storage access · standard SFTP
The short version
Firepipe is a managed SFTP gateway in front of storage you already use. SFTP clients connect to Firepipe, and file contents stream to or from your S3 bucket with no lasting copy kept by Firepipe. You manage users and transfers without standing up or patching an SFTP server.
How it works
Connect storage, add users, hand out the SFTP hostname.
Connect your bucket
For Amazon S3, Firepipe uses a scoped cross-account IAM role, so there is no AWS access key for us to store. For S3-compatible storage such as Cloudflare R2, you provide a scoped credential that you can revoke.
Create SFTP users
Create a password or SSH-key login for each person or system. Jail each user to the path prefix they should be able to see and use.
Transfer files
Users connect with a standard SFTP client. Firepipe translates the SFTP operations to your bucket while file contents remain stored at rest in your cloud account.
Why use Firepipe
Bring your own bucket
Keep S3 as the system of record instead of adding another storage service for SFTP. If you disconnect the bucket, Firepipe no longer has access to it.
Per-user access and audit logs
Give each login its own password or SSH public key and path prefix. Transfer logs show the user, operation, path, byte count, source IP, timestamp, and status, with filtering and CSV export.
Usage-based pricing
Firepipe meters transfer and does not add per-operation or per-listing fees. Your cloud provider still bills your S3 storage, requests, and egress separately.
Simple, metered pricing
Metered transfer. No per-operation or per-listing fees from Firepipe.
Early-access pricing, these starting tiers may change. Your own cloud usage is billed by your provider, directly to you.
Frequently asked questions
What does "SFTP to S3" mean?
Amazon S3 has an object-storage API, not an SFTP server. Firepipe sits in front of your bucket and presents a standard SFTP endpoint, then translates uploads, downloads, listings, and deletes to S3 operations.
Can I keep my files in my own S3 bucket?
Yes. The bucket remains in your AWS account or S3-compatible storage account. Firepipe uses it as the storage backend rather than moving the bucket into a Firepipe-owned storage system.
Does Firepipe support SSH keys and per-user access?
Yes. Each user can authenticate with a password or SSH public key and can be jailed to a path prefix. Revoking a credential also ends any live session.
How does Firepipe access S3?
For Amazon S3, you grant Firepipe a scoped cross-account IAM role limited to the bucket. Firepipe does not need a long-lived AWS access key. S3-compatible stores use a scoped credential that you can revoke.
What does it cost?
The free tier includes 5 GB of transfer per month and 5 users. Paid plans start at $19/mo and meter transfer, with no Firepipe per-operation or per-listing fees. Your cloud provider bills its own storage and egress separately. Firepipe pricing is early-access and may change.
Add SFTP to your S3 bucket
Connect an existing bucket, create SFTP users, and give them the Firepipe hostname.
Start free