FTP & SFTP to IDrive e2
Send files from legacy hardware, cameras, and applications straight to IDrive e2, using the region closest to your devices.
- Instant access
- No migration required
- No infrastructure to run
The file transfer bridge built for IDrive e2
Rilavek sits between your senders and IDrive e2, adding the protocols and access patterns your bucket does not expose on its own.
SFTP & FTP to IDrive e2
Connect legacy hardware, partner systems, and internal tools to IDrive e2 without changing firmware or running a gateway server.
Explore SFTP ingestSource
Cameras, devices, partners
Protocol
SFTP · FTP · FTPS
Destination
IDrive e2
Resumable uploads to IDrive e2
Accept large files from browsers, APIs, and server-side clients over the Tus protocol, with pause and resume built in.
Explore resumable uploadsSource
Browsers, APIs, servers
Protocol
HTTP (Tus) over HTTPS
Destination
IDrive e2
Partner drop folders in IDrive e2
Issue scoped SFTP or FTPS credentials so vendors and customers can deliver files into a bucket you control.
Explore partner exchangeSource
Vendors, customers
Protocol
SFTP · FTPS
Destination
IDrive e2
Replication beyond IDrive e2
Replicate each upload to IDrive e2 and a secondary store in the same request, without a second upload or copy job.
Explore replicationSource
Any sender
Protocol
Inline fan-out
Destination
IDrive e2
Why Rilavek + IDrive e2
A protocol bridge, not a storage competitor. Your IDrive e2 bucket stays the system of record.
Files Go Straight to Your Bucket
Nothing is staged or stored on our side. Uploads stream from the sender into IDrive e2, and retries are held in memory rather than on disk.
Every Protocol, One Bucket
Enable FTP, explicit FTPS, SFTP on port 2222, and resumable Tus uploads over HTTPS on the same pipe, with no gateway to operate.
Regional S3 Endpoints
IDrive e2 exposes regional S3 endpoints and per-key permissions, so each pipe can be scoped to a specific bucket.
One Upload, Several Buckets
Send the same file to IDrive e2 and any secondary stores in a single request. For each secondary, choose whether a failure should fail the whole upload or let it continue.
Common IDrive e2 workloads
The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.
Bulk video archive
Store large surveillance or media archives in a dedicated bucket with lifecycle retention.
Device and camera ingest
Point FTP-only cameras and industrial devices at an e2 bucket without changing firmware.
Nightly backups
Send scheduled server and database backups directly to e2 with no staging disk.
How it works
From bucket to first file in three steps. No servers, agents, or local staging disk.
- 1
Connect your IDrive e2 bucket
Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Found on your Buckets or Access Keys page in the IDrive e2 console (e.g. https://<subdomain>.idrivee2-<region>.com).
IDrive e2 Keysbucket
access key
secret key
- 2
Create a pipe
Choose IDrive e2 as the primary Data Store, then enable FTP, FTPS, SFTP, or resumable HTTP uploads for that pipe.
Pipe setup guideftp
ftps
sftp
tus
- 3
Point your senders at Rilavek
Use ftp.rilavek.com for FTP/FTPS or the SFTP host and port 2222 from your pipe settings. Every file streams straight into IDrive e2.
FTP sender docsftp: ftp.rilavek.com
sftp: sftp.rilavek.com:2222
Secure by design
File transfer is the part of the stack you should not have to rebuild to trust.
- Transport
Encrypted protocols
FTPS uses explicit TLS, SFTP uses SSH, and HTTP uploads use HTTPS. Plain FTP is available for legacy devices only.
- Storage
No temporary storage layer
Files stream through memory only. Rilavek never writes uploads to disk, even during retries.
- Access
Scoped credentials
Connect each destination with a bucket-scoped key or app password instead of an account-wide master key.
IDrive e2 integration questions
Protocol, credential, and setup answers for sending files into IDrive e2.
How does IDrive e2 handle large archives?
IDrive e2 supports S3-compatible buckets plus native lifecycle rules configured in the e2 console, so large archives can be organized by bucket and pruned automatically.
Does IDrive e2 work with standard S3 tooling?
For object operations, yes: IDrive e2 exposes an S3-compatible API, so existing SDKs, CLI tools, and backup software work alongside Rilavek's FTP and SFTP endpoints. Lifecycle rules are configured in the IDrive e2 console rather than through the S3 lifecycle API.
What endpoint do I use for IDrive e2?
Use your account's regional endpoint, https://<account_id>.idrivee2-<region>.com, and create an Access Key scoped to the target bucket.
Does Rilavek store files before sending them to IDrive e2?
No. Rilavek streams each upload directly from the sender to your IDrive e2 bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.
Which upload protocols can write to IDrive e2?
FTP, explicit FTPS, SFTP on port 2222, and resumable HTTP uploads over the Tus protocol. Protocols are enabled and disabled individually per pipe.
Can one upload go to IDrive e2 and another destination at the same time?
Yes. A pipe can have IDrive e2 as its primary Data Store plus one or more secondary stores. Replication happens inline as the file streams. For each secondary, you configure whether a transient error should fail the whole upload or be ignored so the transfer continues.
Do I need to change my application or device?
Only the destination host. Point FTP/FTPS at ftp.rilavek.com or SFTP at the host and port shown in your pipe settings, and keep using your existing client or firmware.
How do I test the integration before rolling it out?
Connect the bucket, create a pipe, and send a test file from your existing client. The dashboard shows delivery status and the resulting object key, so you can confirm the path before pointing production senders at Rilavek.
Is data encrypted in transit?
FTPS uses explicit TLS, SFTP uses SSH, and HTTP uploads use HTTPS. Plain FTP is available for legacy hardware that cannot negotiate encryption, but it should be limited to trusted networks.
Other storage integrations
The same protocol bridge works with every supported object store.

Cloudflare R2
Object storage built for read-heavy workloads

Backblaze B2
Durable object storage for write-heavy archives

Wasabi Hot Cloud
Hot cloud storage for active data

DigitalOcean Spaces
Object storage with a built-in CDN

AWS S3
Enterprise S3 with Glacier archiving

Filebase
Decentralized object storage behind a standard S3 API

Scaleway
EU-hosted object storage for data residency

STRG
EU and US regions with no minimum retention
Ready to send files to IDrive e2?
Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.