Moving to AWS (?) – Part 5

Previous parts: 12, 3 and 4.

Today we got rid of our onsite security camera server! It was necessary to go to a t2.medium EC2 instance as the cameras server software consume too much CPU for anything smaller.

QoS was implemented to limit the camera streams to 6 Mbps outbound bandwidth, and to set them as a lower priority class. In practice this means that during the day when people are using the Internet at home the security camera feeds will not get in the way and slow down the connection. Similarly, we will not starve the feeds of all bandwidth, as we have a 4 Mbps minimum reservation, out of our 10 total available. (Google fiber when?) Outbound camera traffic speeds were between 4-6 Mbps during the day, and at night with the feed in black and white only we see around 1.5 Mbps for four cameras at 720p@20fps. Not too bad.

There is not much to the AWS configuration at this point. We just launched an instance in a new VPC, and added some firewall rules (network ACLs and security groups) to allow the inbound and outbound traffic for our IP cameras and to view the camera feeds on the server in AWS.

Still a few outstanding tasks in Trello before we can mark this task as completed:

Stay tuned for part 6 where we finish up our security server build and move on to migrating our web servers.