AWS S3 Integration

FTP & SFTP to AWS S3

Point cameras, partners, and legacy apps at Rilavek over FTP, SFTP, or HTTP, and we stream each file into AWS S3 — without running an AWS Transfer Family endpoint.

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

The file transfer bridge built for AWS S3

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

SFTP & FTP to AWS S3

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

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

AWS S3

Why Rilavek

Why Rilavek + AWS S3

A protocol bridge, not a storage competitor. Your AWS S3 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 AWS S3, 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. Lifecycle Tiering to Glacier

    Keep hot files in S3 Standard and transition older objects to Glacier Instant Retrieval or Deep Archive with standard S3 Lifecycle rules.

  4. One Upload, Several Buckets

    Send the same file to AWS S3 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 AWS S3 workloads

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

Data lake ingestion

Land device and partner files in S3 for Athena, Glue, and downstream ETL.

Compliance archive

Tier older objects to Glacier while keeping the same bucket and IAM controls.

Legacy device bridge

Avoid an AWS Transfer Family endpoint and point FTP-only hardware at Rilavek.

Setup

How it works

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

  1. 1

    Connect your AWS S3 bucket

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

    bucket

    access key

    secret key

    Rilavek AWS Guide →
  2. 2

    Create a pipe

    Choose AWS S3 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 AWS S3.

    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

AWS S3 integration questions

Protocol, credential, and setup answers for sending files into AWS S3.

How do I avoid an AWS Transfer Family endpoint?

Point FTP and SFTP senders at Rilavek instead of provisioning a Transfer Family server. Rilavek streams into your S3 bucket using standard S3 writes.

Can I archive old files to Glacier automatically?

Yes. Add an S3 Lifecycle rule that transitions objects to Glacier Instant Retrieval or Deep Archive after your chosen number of days, then expires them at the end of retention.

Which AWS credentials does Rilavek need?

An IAM user or role with s3:PutObject scoped to the target bucket. The AWS permissions guide in the docs contains a minimal policy you can attach.

Does Rilavek store files before sending them to AWS S3?

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

Which upload protocols can write to AWS S3?

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

Yes. A pipe can have AWS S3 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 AWS S3?

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