Stream Lorex 4K Nocturnal Smart IP Bullet (E892AB) to AWS S3
4K Color Night Vision smart bullet camera with offsite FTP event recording. Follow our step-by-step setup guide below to stream footage directly to AWS S3 via FTP/S with Rilavek as the pipe — zero on-prem NVR required.
Your Lorex E892AB uploads footage offsite in real time directly to AWS S3. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.
Store Lorex E892AB recordings in AWS S3 on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.
Rilavek ingests native FTP/S streams from your Lorex E892AB and writes them directly to AWS S3 via multipart S3 PUTs with zero disk writes.
How to Stream Lorex 4K Nocturnal Smart IP Bullet (E892AB) to AWS S3
Follow these 6 steps to provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your camera firmware settings, and establish automated S3 retention rules.
Set Up Your 
AWS S3 Bucket & Generate API Keys
Configure your target bucket and API credentials inside AWS S3 so Rilavek can stream motion clips and continuous video directly into your storage.
- In the AWS Management Console, open Amazon S3 and click Create bucket in your target region.
- Navigate to AWS IAM > Users > Create User (e.g.
rilavek-cctv-ingest). - Attach an inline IAM policy granting
s3:PutObject,s3:GetObject,s3:ListBucket, ands3:AbortMultipartUpload. - Open Security credentials > Create access key > select Application running outside AWS.
- Save your Access Key ID and Secret Access Key. Your endpoint is
https://s3.<region>.amazonaws.com.
Add Your Data Store in Rilavek
In your Rilavek dashboard, navigate to Data Stores > New Data Store, select your provider, and enter your S3 credentials. Rilavek verifies the connection with an automated write-probe before saving.
Add New Data Store
Create a Camera Sender in Rilavek
Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Lorex 4K Nocturnal Smart IP Bullet (E892AB) and generates a dedicated device-level password.
Create New Sender
Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.
Secure credentials will be automatically generated for this sender.
Sender Credentials
Create & Configure Your Ingestion Pipe in Rilavek
Go to Pipes in the sidebar and click Create Pipe. Configure the 4 core sections of your pipeline: General (Pipe ID), Inputs (FTP), Access Control (Sender permission), and Destinations (Data Store).
1General Settings (Pipe ID)
Every pipeline in Rilavek is assigned an immutable, globally unique Pipe ID (e.g. p_cctv9x). This ID acts as an isolated ingestion channel that segregates audit logs, real-time transfer metrics, and storage routing. It also forms the second half of your scoped camera FTP login username (username@p_cctv9x).
Pipe ID
Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.
2Inputs (FTP / FTPS Ingress)
The Inputs configuration defines how camera files enter Rilavek. Enabling the FTP Ingress input provides a persistent, high-availability ingestion server (ftp.rilavek.com) compatible with active and passive FTP modes, explicit TLS negotiation, and standard CCTV firmware video push routines.
Inputs
Enable inputs to receive data.
FTP Ingress
Endpoint enabled. Connect using your Sender credentials.
Example: cam_e892ab@p_cctv9x
Use the password configured for the specific Sender.
3Access Control (Sender Authorization)
Access Control prevents unauthorized uploads by enforcing a zero-trust boundary on the ingestion pipe. Only explicitly authorized Senders (such as Lorex 4K Nocturnal Smart IP Bullet (E892AB)) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.
Access Control
Restricts who can upload to this pipe.
Individual Senders
Grant or revoke pipe access for specific individual senders.
4Destinations (Target Cloud Storage Routing)
The Destinations section routes video clips to your target cloud storage provider. Linking your configured Data Store routes all received footage directly to your AWS S3 bucket (cctv-lorex-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.
Destinations
This is where we send your files to.
Configure FTP, Motion Detection & Linkage Method in Lorex 4K Nocturnal Smart IP Bullet (E892AB) Firmware
Open your camera's web configuration page in your browser at its local LAN IP address and complete the steps below:
Step 5AConfigure FTP Streaming Credentials
Click Main Menu > Storage > FTP.
Turn on the 'Enable' toggle switch, select FTP (port 21), and enter your Rilavek Ingestion Gateway server (ftp.rilavek.com), scoped username, device password, and target storage path as indicated below. (Note: Rilavek can handle SFTP as well if you prefer SSH-encrypted surveillance streaming).
cam_e892ab@p_cctv9x (SenderUsername@PipeID).Step 5BConfigure Upload Schedule (Record & Snapshot)
Click Main Menu > Storage > FTP.
Under the Record section, set File Size to 1 (Minutes). Select Event for motion-triggered video streaming or Continuous for 24/7 recording during Period 1 (00:00 - 24:00). Under Snapshot, configure your Picture Upload Interval (e.g. 2 sec) for image captures.
Step 5CTest Connection & Apply Settings (Linkage Verification)
Click Main Menu > Storage > FTP > Test & Apply.
Click 'Test' (1) to verify live FTP communication with your Rilavek Ingestion Gateway and S3 bucket (Rilavek can handle SFTP as well). Once the connection is confirmed, click 'Apply' (2) to commit your settings and activate cloud streaming.
Verify Ingestion
Click Test in your camera's FTP settings or trigger a test recording transfer. In your Rilavek dashboard, navigate to Pipes > your pipeline > Transfers tab to inspect incoming files as video clips stream into AWS S3.
| FILE | SENDER | SIZE | DATE | STATE |
|---|---|---|---|---|
lorex/e892ab/2026-09-10/ch01_143000.mp4 | cam_e892ab | 18.4 MB | Sep 10, 14:30 | Success |
lorex/e892ab/2026-09-10/ch01_142500.mp4 | cam_e892ab | 21.2 MB | Sep 10, 14:25 | Success |
lorex/e892ab/2026-09-10/ch01_142000.mp4 | cam_e892ab | 19.7 MB | Sep 10, 14:20 | Success |
Common questions
Does the Lorex 4K Nocturnal Smart IP Bullet (E892AB) require an on-site NVR to stream to AWS S3?
No. The Lorex 4K Nocturnal Smart IP Bullet (E892AB) has built-in FTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your AWS S3 bucket without requiring a local NVR or PC.
How does retention work on AWS S3?
You define exact retention policies (e.g. 30, 90, or 365 days) directly in your AWS S3 bucket using standard S3 Lifecycle expiration rules. Footage is never auto-overwritten by proprietary cloud caps.
What happens if my internet connection drops?
If your E892AB has a local MicroSD card installed, it records motion events locally and retries the FTP upload once connectivity is restored.
Stream Lorex 4K Nocturnal Smart IP Bullet (E892AB) to AWS S3
Create your free Rilavek ingestion pipe in seconds. No NVR hardware, no proprietary camera cloud subscriptions, and 100% data ownership in your private storage bucket.
Free plan includes 10GB of transfer. No credit card required.