Deploying VOS Cloud on AWS - Customer Prerequisites

  • 1
  • Question
  • Updated 1 month ago
  • Answered
  • (Edited)
VOS Cloud is an offering for Harmonic's on-premise customer. It supports multiple cloud infrastructures and Amazon Web Services (AWS), the customer's own account, is one of them. In this article, we present some required prerequisites for the AWS account to deploy VOS Cloud.

1. Setup IAM Role and Instance Profile for AWS 

VOS Cloud makes use of AWS IAM role and instance profile to obtain necessary permissions to operate inside a customer's AWS account. It is important to create the IAM role and instance profile before deploying VOS:

  • Install AWS CLI onLinux/MacOS
  • Configure AWSCLI with proper credential
  • Obtain the script create_vos_iam_role_and_instance_profile.sh from your local Harmonic Sales Engineer
  • Execute the script to create VOS role and instance profile
[customer@workstation  ~]# ./create_vos_iam_role_and_instance_profile.sh
2. Accept CentOS Image License Agreement at EC2 

VOS AMI is based from official CentOS 7 image published on AWS EC2. Before using the VOS AMI, the End User License Agreement (EULA) from CentOS must be accepted. This needs to be performed if you have never used a CentOS image before.

To do so, log into the AWS account. Go to the following link to choose the appropriate EC2 region on which the VOS Cloud will be launched. Follow the on-screen instruction:


3. Update EC2 Limits

AWS EC2 imposes limits on various resources to prevent accidental overuse. However the default limits may not be sufficient to deploy VOS on a customer's AWS account. Customers should be advised to update the following EC2 limits are higher than the desired values during deployment.

  • Running On-Demand EC2 instances (recommended minimum of 10 nodes of c4.8xlarge, or c3.8xlarge)
  • VPCs (recommended minimum of 5)
  • EC2-VPC Elastic IPs (recommended minimum of 5)
(Note: these limits are per region, an update of the limits is required in each region the VOS Cloud is deployed details on how to increase these limits can be found here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html)

4. Create EC2 Key Pair for VOS


An EC2 key pair is needed during VOS deployment. It is used to gain remote access into EC2 instances of VOS. An EC2 key pair for VOS Cloud must be created and used in the appropriate region, and if possible, share the PEM with Harmonic (in case further troubleshooting is needed). This key pair name is one of the parameters required when deploying VOS with the CloudFormation template. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html


5. Having S3 or EFS Storage for Time-Shift / Catch-Up and Start Over

When using the recording feature on VOS (time-shift / catch-up and Start over) on AWS, an S3 or EFS storage is required. The storage can be selected upon deployment of your cluster. You need to change the dimension of your storage to hold record buffer of equal to the duration of your Time-Shift / Catch-Up and Start Over for all the channels. 

6.  Elastic Load Balancer (ELB)

VOS Cloud will use AWS ELB to route traffic to the VOS compute nodes embedding the origin feature.

7.  Fully Qualified Domain Name for VOS Cloud

In order to access your VOS cloud instance with your domain name, you must have an FQDN ready which VOS Cloud will create a subdomain under it. VOS Cloud uses Amazon Route53 as its DNS service, so you may register a new domain in Route53 or migrate your existing domain to Route53:


8.  Route 53 Public Hosted Zone

VOS Cloud will use Route53 to setup all the required DNS names. You will need to setup a public hosted zone for your domain in Route53 for VOS Cloud to use:


9.  X509 Certificates

To access you VOS instance using you own domain name, you need to provide to Harmonic the X509 certificate of your domain name.
Photo of Jennifer Nguyen

Jennifer Nguyen, Alum

  • 382 Points 250 badge 2x thumb

Posted 12 months ago

  • 1
Photo of Azhar uddin

Azhar uddin

  • 60 Points
Nice blog. I understood the concept AWS very well. This blog is very informative. And it's very interesting topic. Visit to get more knowledge.