Stream Dahua TiOC 2.0 4K Active Deterrence Turret to Any S3-Compatible Cloud
Three-in-One 4K Camera with Full Color, AI Smart Detection, and FTP Cloud Backup. Follow our step-by-step setup guide below to stream footage directly to any cloud via FTP/S with Rilavek as the pipe — zero on-prem NVR required.
Your Dahua IPC-HDW3849H-AS-PV uploads footage offsite in real time. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.
Store Dahua IPC-HDW3849H-AS-PV recordings 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 Dahua IPC-HDW3849H-AS-PV and writes them directly into multipart S3 PUTs with zero disk writes.
How to Stream Dahua TiOC 2.0 4K Active Deterrence Turret to S3-Compatible Cloud Storage
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.
Obtain Your Cloud Storage Bucket & API Credentials
Rilavek bridges your Dahua cameras and NVRs directly into any S3-compatible cloud or self-hosted bucket. To begin, you need an S3 bucket name, your provider's regional endpoint, and an Access Key / Secret Key pair with read/write permissions.
Need Provider-Specific Instructions?
Click any provider for exact dashboard steps:
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 Dahua TiOC 2.0 4K Active Deterrence Turret 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_ipchdw3849haspv@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 Dahua TiOC 2.0 4K Active Deterrence Turret) 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 S3-Compatible Cloud Storage bucket (cctv-dahua-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 Dahua TiOC 2.0 4K Active Deterrence Turret 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 Setting > Storage > Destination > FTP.
Enter your Rilavek Ingestion Pipe parameters as indicated by the red annotations below.
cam_ipchdw3849haspv@p_cctv9x (SenderUsername@PipeID).Step 5BConfigure Upload Schedule (Snapshot & Record Schedule)
Click Setting > Storage > Schedule.
Select the Snapshot or Record tab, then ensure your schedule grid has Yellow (Motion) or Green (General) time blocks configured so the camera uploads footage during active periods.
Dahua IP cameras only upload files during times marked on the schedule matrix. Highlight periods in Yellow (Motion) for motion-triggered snapshot/clip upload to save S3 storage and ingress fees.
Step 5CEnable FTP Destination in Storage Path (Linkage Routing)
Click Setting > Storage > Destination > Path.
Check the "FTP" checkboxes under Scheduled and Motion Detection for Record and Snapshot. In Dahua firmware, FTP storage must be explicitly activated in this Path table for files to upload to Rilavek.
| Event Type | Scheduled | Motion Detection |
|---|---|---|
| FTP |
| Event Type | Scheduled | Motion Detection |
|---|---|---|
| FTP |
In Dahua IP camera firmware, you must check the "FTP" boxes under Scheduled and Motion Detection in this Path destination matrix. If these boxes remain unchecked, the camera will record events locally to SD card/NVR storage, but will never forward snapshots or video clips to your Rilavek FTP Ingestion Gateway even if the credentials under the FTP tab test 100% successfully.
Dahua Firmware Notes & Best Practices
Model-specific nuances, recommended settings, and verified workarounds for the IPC-HDW3849H-AS-PV
Dahua separates Snapshot FTP from Video Record FTP under different sub-menus. Configuring one does not automatically enable the other.
Dahua only uploads files when the Storage > Schedule timeline is marked in Green (General) or Yellow (Motion).
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 S3-Compatible Cloud Storage.
| FILE | SENDER | SIZE | DATE | STATE |
|---|---|---|---|---|
dahua/ipc-hdw3849h-as-pv/2026-09-10/ch01_143000.mp4 | cam_ipchdw3849haspv | 18.4 MB | Sep 10, 14:30 | Success |
dahua/ipc-hdw3849h-as-pv/2026-09-10/ch01_142500.mp4 | cam_ipchdw3849haspv | 21.2 MB | Sep 10, 14:25 | Success |
dahua/ipc-hdw3849h-as-pv/2026-09-10/ch01_142000.mp4 | cam_ipchdw3849haspv | 19.7 MB | Sep 10, 14:20 | Success |
Common questions
Does the Dahua TiOC 2.0 4K Active Deterrence Turret require an on-site NVR to stream to cloud storage?
No. The Dahua TiOC 2.0 4K Active Deterrence Turret has built-in FTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your S3 bucket without requiring an on-prem NVR or dedicated PC.
Which cloud storage providers work with IPC-HDW3849H-AS-PV?
Rilavek supports any provider with an S3-compatible API, including Cloudflare R2, Backblaze B2, AWS S3, Wasabi, IDrive e2, and self-hosted MinIO or RustFS instances.
How does video retention work?
You define retention policies (such as 30, 60, or 90 days) directly on your S3 bucket using lifecycle expiration rules. Your recordings are under your 100% control with zero vendor lock-in.
Stream Dahua TiOC 2.0 4K Active Deterrence Turret to S3 Cloud Storage
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.