Wasabi Hot Cloud Integration

FTP & SFTP to Wasabi Hot Cloud

Point any FTP, SFTP, or HTTP source at Rilavek, and uploads arrive in Wasabi Hot Cloud already readable — no cold tier, no restore step.

  • Instant access
  • No migration required
  • No infrastructure to run
FTPSFTPHTTPSFTPSFTPFTPSFTPHTTPSFTPSFTP
CCTV
Camera
Browser
Server
Scripts
Wasabi Hot Cloud logo
Wasabi Hot Cloud
Rilavek LogoRilavek
Diagram showing FTP, FTPS, SFTP, and HTTPS uploads flowing through Rilavek into Wasabi Hot Cloud.
Capabilities

The file transfer bridge built for Wasabi Hot Cloud

Rilavek sits between your senders and Wasabi Hot Cloud, adding the protocols and access patterns your bucket does not expose on its own.

SFTP & FTP to Wasabi Hot Cloud

Connect legacy hardware, partner systems, and internal tools to Wasabi Hot Cloud without changing firmware or running a gateway server.

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

Wasabi Hot Cloud

Why Rilavek

Why Rilavek + Wasabi Hot Cloud

A protocol bridge, not a storage competitor. Your Wasabi Hot Cloud bucket stays the system of record.

  1. Files Go Straight to Your Bucket

    Nothing is staged or stored on our side. Uploads stream from the sender into Wasabi Hot Cloud, and retries are held in memory rather than on disk.

  2. 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.

  3. Hot Storage with Minimum Retention

    Wasabi is designed for active data and applies a minimum storage duration, which aligns with standard 90-day surveillance and compliance windows.

  4. One Upload, Several Buckets

    Send the same file to Wasabi Hot Cloud and any secondary stores in a single request. For each secondary, choose whether a failure should fail the whole upload or let it continue.

Scenarios

Common Wasabi Hot Cloud workloads

The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.

90-day surveillance retention

Wasabi's minimum storage duration lines up with a standard 90-day CCTV retention window.

Media archive and review

Store large media libraries and let teams download or stream them directly from the bucket.

Hot backup target

Use Wasabi as an immediately available tier for nightly database and file-system backups.

Setup

How it works

From bucket to first file in three steps. No servers, agents, or local staging disk.

  1. 1

    Connect your Wasabi Hot Cloud bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint.

    bucket

    access key

    secret key

    Wasabi Keys
  2. 2

    Create a pipe

    Choose Wasabi Hot Cloud as the primary Data Store, then enable FTP, FTPS, SFTP, or resumable HTTP uploads for that pipe.

    ftp

    ftps

    sftp

    tus

    Pipe setup guide
  3. 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 Wasabi Hot Cloud.

    ftp: ftp.rilavek.com

    sftp: sftp.rilavek.com:2222

    FTP sender docs
Security

Secure by design

File transfer is the part of the stack you should not have to rebuild to trust.

Read the setup and security docs
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.

FAQ

Wasabi Hot Cloud integration questions

Protocol, credential, and setup answers for sending files into Wasabi Hot Cloud.

How does Wasabi handle downloads?

Wasabi keeps stored objects immediately available for download and streaming, which suits active review and media archive workflows.

Why does Wasabi suit 90-day retention?

Wasabi applies a minimum storage duration, typically 90 days, which matches a standard surveillance retention window. Deleting objects earlier may still count against the minimum period.

Can I use a shorter retention with Wasabi?

You can configure shorter lifecycle rules, but the minimum storage duration may still apply. For very short retention, a usage-based provider such as Cloudflare R2 or Backblaze B2 is usually a better fit.

Does Rilavek store files before sending them to Wasabi Hot Cloud?

No. Rilavek streams each upload directly from the sender to your Wasabi Hot Cloud bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.

Which upload protocols can write to Wasabi Hot Cloud?

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 Wasabi Hot Cloud and another destination at the same time?

Yes. A pipe can have Wasabi Hot Cloud 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.

Ready to send files to Wasabi Hot Cloud?

Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.