I wanted to stream and record my home security cameras to the cloud for three reasons: 1) if the NVR is stolen, I’ll have the footage stored remotely, 2) (more realistically) I want to increase the storage availability without having to add hard drives, and 3) I want to increase the ease-of-access for my recordings. There are a number of services that do this for you (such as Wowza) and you can also purchase systems that do this out-of-the-box. The downside to services like Wowza is cost — at least $50/month for a single channel streaming without any recording – and the out-of-the-box solutions are expensive and run on proprietary platforms that limit your use and access…plus it’s more fun to do it yourself and learn something.
The solution I arrived at was to use AWS Lightsail and S3. This gives me the low cost, ease of scale, and accessibility I desire. Due primarily to the transfer rate limits, Lightsail will only work for small, home setups but you could “upgrade” from Lightsail to EC2 to mitigate that. After all, Lightsail is just a pretty UI that takes away all the manual config work needed to setup an EC2 instance (in fact, Lightsail utilizes EC2 behind the scenes). If you prefer not to use Lightsail or EC2 at all, you could swap in a Raspberry Pi to do the grunt work locally and pass the files to S3. This would cut the monthly cost by ~$5 but comes with the maintenance of local hardware.
What we’re doing
In this guide, we’ll capture and RTSP stream from a Hikvision (which includes most Nightowl, LaView, and many more as they all use a branded form of Hikvision’s software) security camera NVR and save the files to AWS S3 by:
- Creating an AWS Lightsail instance
- Installing openRTSP (via LiveMedia-Utils package)
- Capturing the RTSP stream, save it locally to the Lightsail instance
- Installing the AWS PHP SDK and use it to sweep the video files from the Lightsail instance to S3
While the details below are specific to my setup, any RTSP stream (such as the NASA stream from the International Space Station) and any Linux server will work as well. Substitute as desired.
Step 1: Creating the Lightsail Instance
I’m going to use the $5/month LAMP w/PHP7 type so that we can have the 2TB of transfer. In my testing, this was sufficient for the number of cameras/channels I’m handling. You should do your own testing to determine whether this is right for you. Keep in mind that transfer is measured both in AND out and we’ll be transferring these files out to S3.
Although 100% optional, I’d recommend going ahead and assigning a static IP and setting up a connection in PuTTY. Otherwise, the web terminal window provided in the Lightsail UI will work – I find it a bit buggy, though.
Step 2: Install LiveMedia-Utils package
The LiveMedia-Utils package contains openRTSP which is the key to consuming and storing the feeds from our NVR. Once connected to our Lightsail instance, let’s:
sudo apt-get install livemedia-utils cd /usr/src sudo wget http://www.live555.com/liveMedia/public/live555-latest.tar.gz sudo tar -xzf live555-latest.tar.gz cd live sudo ./genMakefiles linux sudo make sudo make install
At this point, openRTSP should be ready to go.
Step 3: Capturing the RTSP steam
I want to keep my video files contained so let’s create a new directory for them:
mkdir /home/bitnami/recordings cd /home/bitnami/recordings
And now we’re ready to test! I’d recommend reviewing the list of options openRTSP offers before diving in. Here’s my set of options:
openRTSP -D 1 -c -B 10000000 -b 10000000 -4 -Q -F CAM1 -d 300 -P 300 -t -u <USERNAME> <PASSWORD> rtsp://<MYCAMIP>:554/Streaming/Channels/102
Some explanations:
-D 5 | Quit if nothing is received for 5 of more seconds
-c | Play continuously, even after –d timeframe
-B 10000000 | Input buffer of 10MB.
-b 10000000 | Output buffer of 10MB (to the .mp4 file)
-4 | Write in .mp4 format
-Q | Display QOS statistics on exit
-F CAM1 | Prefix the .mp4 files with “CAM1”
-d 300 | Run openRTSP for this many seconds – essentially, the length of your files.
-P 300 | Start a new file every 300 seconds – essential, the length of your individual files (so each 5 minute block of time will be a unique file)
-t | Use TCP instead of UDP
-u <> | My cam’s username, password, and the RTSP URL.
You can use tmux to let openRTSP command contiue to run in the backgound (otherwise, it’ll die when your close your terminal window). So:
tmux openRTSP -D 1 -c -B 10000000 -b 10000000 -4 -Q -F CAM2 -d 300 -P 300 -t -u <username> <password> <rtspURL>
Then press ctrl+b followed by d to hop out of tmux and you can close the terminal window.
You should see your video files start populating in the /home/bitnami/recordings directory now:
Step 4: Install the AWS PHP SDK and move recordings to S3
As S3 is cheaper and since we only have 40GB of storage with our Lightsail instance, I’m going to move my recordings from Lightsail to S3 using PHP.
Before proceeding, Install the AWS PHP SDK.
Now that the SDK is installed, we can create a simple script and cron to filter through the files in the /home/bitnami/recordings directory, determine their age, move the oldest S3, and delete the file from Lightsail. If my files are 5 minutes long, I’ll have my cron run every 5 minutes. Yes, there are more efficient ways of doing this but I’m okay with being scrappy in this situation.
I’d recommend taking a snapshot of your instance now that everything is setup, tested, and finalized. This enables you to tinker and try new things without worrying about having to repeat this process if you screw something up.
I’ll create a directory for my cron script and its log to live and then create my cron file:
mkdir /home/bitnami/cron cd /home/bitnami/cron sudo nano move.php
Here’s the script (move.php) I wrote to handle the directory list, sortation, movement to S3, and deletion from Lilghtsail:
<?php //Include AWS SDK require '/home/bitnami/vendor/autoload.php'; //Start S3 client $s3 = new Aws\S3\S3Client([ 'region' => 'us-west-2', 'version' => 'latest', 'credentials' => [ 'key' => '<iamkey>', //IAM user key 'secret' => '<iamsecret>', //IAM user secret ] ]); //Set timezone and get current time date_default_timezone_set('America/Los_Angeles'); $currentTime=strtotime("now"); //Get a list of all the items in the directory, ignoring those we don't want to mess with $files = array_diff(scandir("/home/bitnami/recordings",1), array('.', '..','.mp4','_cron_camsstorevideos.sh')); //Loop through those files foreach($files as $file){ $lastModified=date ("Y-m-d H:i:s", filemtime("/home/bitnami/recordings/$file"));//Separate out the "pretty" timestamp as we'll use it to rename our files. $lastModifiedEpoch=strtotime($lastModified);//Get the last modified time if($currentTime-$lastModifiedEpoch>30){ //If the difference between now and when the file was last modified is > 30 seconds (meaning it's finished writing to disk), take actions echo "\r\n Taking action! $file was last modified: " . date ("F d Y H:i:s", filemtime("/home/bitnami/recordings/$file")); //Save to S3 $result = $s3->putObject([ 'Bucket' => '<bucketname>', //the S3 bucket name you're using 'Key' => "CAM1VIDEO @ $lastModified.mp4", //The new filename/S3 key for our video (we'll use the last modified time for this) 'SourceFile' => "/home/bitnami/recordings/$file", //The source file for our video 'StorageClass' => 'ONEZONE_IA' //I'm using one zone, infrequent access (IA) storage for this because it's cheaper ]); //Delete file from lightsail unlink("/home/bitnami/recordings/$file"); } } ?>
That’s it! As long as you have the write policy applied to your bucket, you should be good to go:
The last thing I’ll do is set a crontab to run the move.php script every 5 minutes and log the output:
*/5 * * * * sudo php /home/bitnami/cron/move.php >> /home/bitnami/cron/move.log 2>&1
Awesome! Thank you very much, I’ll try it out =)
Thanks for your openRSTP command, I have tested out, there is an issue if you don’t specify the width and height and fram per seconds. I have to tweak those value to get what I need.
Glad you got things working. Pasting a snippet from the openRTSP manual in case someone else runs into similar issues:“, “-h ” and “-f ” options to specify the width and height (in pixels), and frame rate (per-second) of the corresponding video track. (If these options are omitted, then the values width=240 pixels; height=180 pixels; frame-rate=15 are used.)”
“If the session contains a video subsession, you should also use the “-w