DigitalOcean Spaces Integration

FTP & SFTP to DigitalOcean Spaces

Land uploads from cameras, devices, and applications in DigitalOcean Spaces, then serve them through the bundled CDN.

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

The file transfer bridge built for DigitalOcean Spaces

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

SFTP & FTP to DigitalOcean Spaces

Connect legacy hardware, partner systems, and internal tools to DigitalOcean Spaces without changing firmware or running a gateway server.

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

DigitalOcean Spaces

Why Rilavek

Why Rilavek + DigitalOcean Spaces

A protocol bridge, not a storage competitor. Your DigitalOcean Spaces 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 DigitalOcean Spaces, 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. Storage and CDN in One

    Spaces includes a built-in CDN, so files uploaded through Rilavek can be delivered from the edge without a separate service.

  4. One Upload, Several Buckets

    Send the same file to DigitalOcean Spaces 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 DigitalOcean Spaces workloads

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

Web and app assets

Accept uploads from browser apps and serve the resulting objects from the Spaces CDN.

Camera and device ingest

Replace a local FTP server with a Space that cameras can write to directly.

Backups and exports

Push periodic exports and backups into a Space without running an SFTP host.

Setup

How it works

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

  1. 1

    Connect your DigitalOcean Spaces bucket

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

    bucket

    access key

    secret key

    DigitalOcean Keys
  2. 2

    Create a pipe

    Choose DigitalOcean Spaces 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 DigitalOcean Spaces.

    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

DigitalOcean Spaces integration questions

Protocol, credential, and setup answers for sending files into DigitalOcean Spaces.

How does the Spaces CDN work with uploaded files?

Each Space has a CDN endpoint. Once Rilavek writes an object, serve it through the CDN endpoint for edge delivery; Rilavek keeps writing to the Space itself.

Does Spaces support S3 lifecycle rules?

Yes. Spaces is S3-compatible and supports bucket lifecycle rules for expiring or transitioning objects.

Which region should I choose?

Pick the region closest to your senders. Rilavek uses endpoints in the form https://<region>.digitaloceanspaces.com, such as nyc3 or fra1.

Does Rilavek store files before sending them to DigitalOcean Spaces?

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

Which upload protocols can write to DigitalOcean Spaces?

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 DigitalOcean Spaces and another destination at the same time?

Yes. A pipe can have DigitalOcean Spaces 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 DigitalOcean Spaces?

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