Backup Hikvision 8-Channel 4K NVR (DS-7608NI) to AWS S3
Network Video Recorder offsite disaster backup directly to S3/R2 object storage. Follow our step-by-step setup guide below to replicate NVR channel footage directly to AWS S3 via FTP/S with Rilavek as the pipe — securing your footage offsite against on-prem hardware theft or disk failure.
Your Hikvision DS-7608NI-I2/8P replicates channel footage offsite in real time directly to AWS S3. Even if the physical NVR unit or local hard drives are stolen, damaged, or seized, your video archive remains safe in the cloud.
Retain multi-channel Hikvision DS-7608NI-I2/8P recordings in AWS S3 beyond local drive capacity. 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 Hikvision DS-7608NI-I2/8P NVR and writes them directly to AWS S3 via multipart S3 PUTs with zero intermediate server caching.
How to Backup Hikvision 8-Channel 4K NVR (DS-7608NI) to AWS S3
Follow these 6 steps to provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your NVR 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 replicate multi-channel NVR recordings 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 an NVR Sender in Rilavek
Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Hikvision 8-Channel 4K NVR (DS-7608NI) 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 NVR 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 NVR recordings 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 NVR multi-channel video push routines.
Inputs
Enable inputs to receive data.
FTP Ingress
Endpoint enabled. Connect using your Sender credentials.
Example: nvr_ds7608nii28p@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 Hikvision 8-Channel 4K NVR (DS-7608NI)) 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-hikvision-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 NetHDD / FTP Offsite Replication in Hikvision 8-Channel 4K NVR (DS-7608NI) Firmware
Open your NVR's web configuration page or local GUI in your browser at its local LAN IP address and complete the steps below:
Step 5AConfigure FTP Streaming Credentials
Click Configuration > Network > Advanced > NetHDD / FTP.
Enter your Rilavek Ingestion Pipe parameters as indicated by the red annotations below.
nvr_ds7608nii28p@p_cctv9x (SenderUsername@PipeID created in Step 3 & 4).AWS S3 bucket.Step 5BConfigure Motion Detection (Area Settings)
Click Configuration > Event > Basic Event > Motion Detection.
To stream motion-triggered events instead of continuous 24/7 recording (saving cloud storage and bandwidth), configure your detection area and target filters as indicated by the red annotations below.
Step 5CConfigure Linkage Method (Upload to FTP)
Click Configuration > Event > Basic Event > Motion Detection > Linkage Method.
Check "Upload to FTP/Memory Card/..." so motion video clips stream to Rilavek as indicated by the red annotations below.
ftp.rilavek.com so they stream to AWS S3.Hikvision Firmware Notes & Best Practices
Model-specific nuances, recommended settings, and verified workarounds for the DS-7608NI-I2/8P
When streaming from an NVR, all 8 channels stream to the same FTP pipe. Channels can overwrite files if not segregated.
Verify Ingestion
Click Test in your NVR'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 |
|---|---|---|---|---|
hikvision/ds-7608ni-i2/2026-09-10/ch01_143000.mp4 | nvr_ds7608nii28p | 18.4 MB | Sep 10, 14:30 | Success |
hikvision/ds-7608ni-i2/2026-09-10/ch01_142500.mp4 | nvr_ds7608nii28p | 21.2 MB | Sep 10, 14:25 | Success |
hikvision/ds-7608ni-i2/2026-09-10/ch01_142000.mp4 | nvr_ds7608nii28p | 19.7 MB | Sep 10, 14:20 | Success |
Common questions
How does the Hikvision 8-Channel 4K NVR (DS-7608NI) backup recordings to AWS S3?
The Hikvision 8-Channel 4K NVR (DS-7608NI) uses its native FTP / NetHDD client to upload multi-channel recordings directly to Rilavek on port 21. Rilavek pipes footage directly into your AWS S3 bucket with zero disk writes, giving you a secure, automated offsite copy of your surveillance archive.
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?
The DS-7608NI-I2/8P continues recording footage to its internal hard drives locally and resumes offsite FTP replication to AWS S3 once connectivity is restored.
Backup Hikvision 8-Channel 4K NVR (DS-7608NI) 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.