How to Create a Pipe & Route Transfers
A Pipe is the central routing engine of Rilavek. It links your incoming protocols (such as FTP or SFTP) to your target Data Stores and defines which Senders are authorized to transfer files.
Dashboard Overview
Real-time status of storage connections and pipelines.
Connect your Senders to your Data Store with ingress protocols.
Step 1: Create Your Pipe
In your Rilavek dashboard, select Pipes from the sidebar and click the New Pipe button in the top right.
| Field | Description | Example |
|---|---|---|
| Pipe Name | A clear label to identify the pipe and its routing purpose. | Production Ingress |
| Description | Optional context about the workflow, team, or systems using this pipe. | Daily Partner Feed |
Click Create Pipe. Rilavek provisions your pipeline workspace and redirects you directly to its dedicated management page.
Step 2: Enable Ingress Protocols (Inputs)
Under the Inputs card on your Pipe page, review your active protocols or click Add Input to enable protocols for your uploaders:
Essential for embedded hardware, network scanners, and legacy systems. Supports standard plaintext FTP and encrypted Explicit FTPS.
Modern SSH file transfer with firewall-friendly single-port architecture. Perfect for scripts, automated pipelines, and partner feeds.
Resumable web and API uploads using the open Tus standard. Reliable for browser upload widgets and mobile apps.
Step 3: Connect Primary Storage (Destinations)
Scroll down to the Destinations card. This is where you connect the target storage bucket you provisioned in Guide 01:
| Field | Description | Example |
|---|---|---|
| Select Datastore | Choose your connected cloud bucket provisioned in Guide 01. | Production S3 |
| Destination Path | An optional base path prefix inside the bucket where uploaded files land (defaults to root /). | /incoming |
| Sender Subfolder Isolation | Toggle whether files are automatically sorted into dedicated subdirectories named after the uploading sender. | Enabled |
Step 4: Authorize Senders (Access Control)
Pipes lock down ingress by default. Until you explicitly authorize an identity in the Access Control section, any upload attempt gets rejected right at authentication. You can grant access either to individual identities or to entire sender groups:
Select an individual sender from the dropdown, such as the identity you created in Guide 02 (e.g. Client 01).
Access effect: Grants upload access exclusively to that single identity. They authenticate using username@pipeId. If you ever need to revoke their access, removing them cuts off only that client without touching anyone else.
Best for: Dedicated partner drops, external contractors, or one-off clients needing tight, isolated access.
Switch to the Groups tab and pick a sender group from the dropdown (such as Field Cameras or Branch Offices).
Access effect: Every sender in the group instantly inherits access to this pipe. When field technicians add new devices to the group later on, those devices start uploading immediately with zero pipe updates needed.
Best for: Fleets of IoT hardware, security cameras, branch offices, or whole departments where managing access device by device doesn't scale.
Step 5: Retrieve Your Pipe Short ID
Look at the Pipe ID card near the top of your Pipe page. Rilavek assigns a unique short identifier (such as p_9k2a4):
Guide 04: Send First File
Push a test file over your protocol endpoint and verify instant zero-disk streaming into your bucket.