Skip to main content

AWS: The Video Star

Or; How to Stream Video within Network Confines (And prevent piracy).



How it’s Delivered 
Content ————> Consumer
  • Compression happens.
  • Packaging happens based upon protocols.
  • How does it adapt to the variation in network speeds?


What’s it made of.
  • Over the Top Workflow
  1. The livestream from the stadium.
  2. Ingested
  3. Encoded
  4. Passed to origin server that sends it out.
  5. Someone requests it from the server.
  6. Packaging service formats it appropriately.
(Hub and spoke of origin servers to edge servers)

Consumer side of OTT 
  • Request goes to a Content Delivery Network that requests the content.
  • Said content is optimized for the network and device.

  • Adaptive Bitrate Streaming
    • When the network is unstable.
    • You can switch between bitrates at segmentation points.
    • Weak connection, smallest bitrate, stronger - Higher.

  • Adaptive streaming formats
    • Apple HTTPS Live Streaming for iOS
    • MPEG-DASH (Dynamic Adaptive Streaming over HTTPS)
    • Microsoft Smooth
    • Adobe HTTP Adaptive Streaming


  • Just in Time Packaging 
    • Based upon the device making the request.

  • Manifest manipulation.
    • Penalization with ads and time-shifted TV.
  - Manifests also lists the versions of a particular compressed source.

  • CDN
    • Content delivery network stores video in the most bandwidth efficient way in locations closest to the customers.
    • Have multiple edge locations across regions.

  • DRM Access Rights 
    • Restrict access to video not everyone should be able to see.
    • Encoder requests Key from Key Server, which authenticates it and gives a key.
    • Encoder encrypts key.
    • Player/Client requests key 
    • Key server gives decryption key to Player/Client.
    • P/C decrypts encoder file.




Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory