Oracle Cloud (OCI) Integration

FTP & SFTP to Oracle Cloud (OCI)

Feed FTP, SFTP, and HTTP uploads into Oracle Cloud Object Storage in the region you run, and let lifecycle rules retire old objects.

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

The file transfer bridge built for Oracle Cloud (OCI)

Rilavek sits between your senders and Oracle Cloud (OCI), adding the protocols and access patterns your bucket does not expose on its own.

SFTP & FTP to Oracle Cloud (OCI)

Connect legacy hardware, partner systems, and internal tools to Oracle Cloud (OCI) without changing firmware or running a gateway server.

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

Oracle Cloud (OCI)

Why Rilavek

Why Rilavek + Oracle Cloud (OCI)

A protocol bridge, not a storage competitor. Your Oracle Cloud (OCI) 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 Oracle Cloud (OCI), 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. Enterprise Object Storage

    OCI combines S3-compatible access with regional tenancy controls and native lifecycle policies for long-term archives.

  4. One Upload, Several Buckets

    Send the same file to Oracle Cloud (OCI) 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 Oracle Cloud (OCI) workloads

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

High-volume footage review

Stream or download large archives directly from Object Storage.

Enterprise archive

Keep long-term objects in OCI with lifecycle rules and S3-compatible access.

Legacy application ingest

Let FTP-only applications write into Object Storage without custom middleware.

Setup

How it works

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

  1. 1

    Connect your Oracle Cloud (OCI) bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Format: https://<namespace>.compat.objectstorage.<region>.oraclecloud.com (find your Object Storage Namespace under Tenancy Details in the OCI console).

    bucket

    access key

    secret key

    OCI Secret Keys
  2. 2

    Create a pipe

    Choose Oracle Cloud (OCI) 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 Oracle Cloud (OCI).

    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

Oracle Cloud (OCI) integration questions

Protocol, credential, and setup answers for sending files into Oracle Cloud (OCI).

How does OCI handle large downloads?

Objects stay available for direct download or streaming, and OCI's regional tenancy model keeps access controls close to the data.

How do I get S3 credentials for OCI?

Generate a Customer Secret Key under your OCI user profile. The generated access key and secret key work as standard S3 credentials.

What endpoint format does OCI use?

Use https://<namespace>.compat.objectstorage.<region>.oraclecloud.com, where <namespace> is your tenancy's Object Storage namespace.

Does Rilavek store files before sending them to Oracle Cloud (OCI)?

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

Which upload protocols can write to Oracle Cloud (OCI)?

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 Oracle Cloud (OCI) and another destination at the same time?

Yes. A pipe can have Oracle Cloud (OCI) 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 Oracle Cloud (OCI)?

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