Amazon Web Services EC2 Helix Server

Amazon Web Services EC2 Helix Server 14.3.0 Tuesday, July 24, 2012 Copyright The information contained herein is the property of RealNetworks

Table of contents 1. Operating Systems...3 2. Summary of Steps...3 3. Important Key concepts:...3 4. Attaching EBS Storage to your Instance...4 5. Accessing the Helix Server AMI (Amazon Machine Image)...4 6. CentOS 5.8 AMI Instance...6 6.1. Connecting to the CentOS Instance...7 6.2. Attach and prepare an EBS volume...7 6.2.1. Format your volume...8 6.2.2. Mount the device:...8 6.3. Install Helix Server...8 7. Windows 2008 R2 AMI Instance...10 7.1. Connecting to the Windows Instance...14 7.2. Attach and prepare and EBS Volume...16 7.2.1. Mount and Format your drive...18 7.3. Install Helix Server...22 Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 2 of 23

Purpose of this document This is a QuickStart guide to to aide the user in installing and configuring the Helix Universal Server for use in the Amazon EC2 environment. It provides the reader with baseline knowledge of the requirements for running Helix Server in the AWS EC2 environment. The reader is expected to complement these instructions with the Amazon EC2 documentation. Complete documentation on Amazon EC2 can be found here: http://docs.amazonwebservices.com/awsec2/latest/gettingstartedguide/welcome.html AND http://docs.amazonwebservices.com/awsec2/latest/userguide/welcome.html The instructions below reference usage of the AWS Management Console UI only. 1. Operating Systems These instructions cover support for CentOS 5.8 and Windows Server 2008 R2-64 bits. It is assumed the reader has a basic knowledge of these operating systems. 2. Summary of Steps The following steps are required for CentOS and Windows. 1. Contact Helix sales to request an EC2 Helix Server License. Contact information is on our web site at: http://www.realnetworks.com/helix/ 2. Access the AWS AMI 3. Launch and Instance 4. Connect to the instance 5. Attach storage and Create a Volume 6. Install Helix Server 3. Important Key concepts: A default volume size of 10GB is attached to the Helix Server AMI root device when launched. This may vary depending on the AMI used. Any storage volume attached prior to instance launch will be deleted if or when the instance is terminated. The DeleteOnTermination flag is set to True by default. This concept applies to the root device. The root device, and any other volume attached prior to launching the instance, can be configured to persist via the command line tools and API. This documentation does not currently cover this option. To learn more about the command line tools please refer to the following: http://docs.amazonwebservices.com/awsec2/latest/userguide/setting- up- your- tools.html For now we will focus on attaching and preparing an EBS volume AFTER the instance has launched. In this scenario the volume DeleteOnTermination flag will be set to False by default. If the instance is terminated, the Helix Server volume can be easily reattached to any running instance. The steps below summarize the process described here: http://docs.amazonwebservices.com/awsec2/latest/userguide/amazonebs.html Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 3 of 23

4. Attaching EBS Storage to your Instance Before installing the Helix Server you will need to understand AWS EBS concepts. To familiarize yourself with AWS EBS please refer to the following documentation: http://docs.amazonwebservices.com/awsec2/latest/userguide/storage.html Since the Helix Server AMIs are EBS- backed, you should read: http://docs.amazonwebservices.com/awsec2/latest/userguide/rootdevicestorage.html 5. Accessing the Helix Server AMI (Amazon Machine Image) Note: the Helix Server AMIs referenced in the following documentation are offered as a courtesy. RealNetworks used the referenced AMIs during the Helix software certification process. However, they DO NOT currently have Helix Server pre- installed. You may choose to use these AMIs or any other CentOS or Windows 2008 based AMI of your choice. To access the Helix Server 14.3.x AMI, login to the Amazon Web Services management console: https://console.aws.amazon.com You will be presented with the AWS Management Console welcome screen. 9. Click on the EC2 tab. 10. On the right side pane, on the field Viewing: choose Public Images in the drop down menu and in the next field choose All Platforms. Type in Helix Server in the search field. You should see under the AMI ID column the following AMIs: Helix Server 14.3.x CentOS 5.8, ami- 4f6bb226 Helix Server 14.3.x WinServ2008_R2_64_Base_v3, ami- f0d37599 These are public AMIs available in the U.S. East region to anyone who has an AWS account. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 4 of 23

You may also use another CentOS 5.8 or Windows 2008 AMI of your choosing. The Helix Server 14.3.x AMI are EBS backed AMIs. It is recommended to use EBS backed AMIs rather than instance store- backed AMIs per the benefits outlined by Amazon. If you are outside the US East region please use another publically available CentOS 5.x or Windows Server 2008 R2 64 bit AMI. You can do this by selecting Public Images in the Viewing drop down menu and choosing the platform in the next field. Available regions include: US East, US West, South America (San Paulo), Asia Pacific (Tokyo), Asia Pacific (Singapore), EU West (Ireland). For additional information on Amazon AMIs please read the following: http://docs.amazonwebservices.com/awsec2/latest/userguide/concepts_bootfromebs.html http://docs.amazonwebservices.com/awsec2/latest/userguide/componentsamis.html Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 5 of 23

6. CentOS 5.8 AMI Instance To launch an instance from the Helix Server 14.3.x public AMI: 1. Login to the AWS Management Console as described above. 2. From the welcome screen, click the EC2 link. 3. In the Navigation pane under IMAGES click on AMIs. To use the referenced AMIs you must have your Region set to US East. Otherwise use a CentOS AMI of your choice. 4. In the Amazon Macine Images pane please click on the Viewing dropdown menu and select Public Images. Select CentOS as your Platform and type Helix Server in the search field. You should see the following AMI ID: Helix Server 14.3.x - CentOS 5.8 (ami- 4f6bb226) 5. Click Launch in the upper left (above the viewing drop down menu). The Request Instance Wizard will launch. The wizard is mostly self- explanatory. Wizard Options: Choose instance type and availability zone. Click on continue. Advanced Instance Options: choose defaults for kernel ID and RAM disk. Shutdown behavior: chose stop. If use choose terminate the instance will be deleted completely upon shutdown. Click on continue. A new window will open to give you a change to enter descriptive tag. Next to the Name tag under the value column, enter a descriptive name that will allow you to distinguish your instance, then click on continue. Choose a key pair. Amazon provides a key pair with a.pem extension which does not work from Windows clients. If you are using a Windows computer, you will need to convert the key using PuTTY. In the process of lunching the AMI, Amazon will provide you with additional information on how to do this. See section Connecting to your instance further below. Also, you will have to create new key pair per region. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 6 of 23

Choose a security group. Please see the complete list of ports required by Helix Server in Appendix A. You must open the relevant ports in your security group for the Helix Server functionality you wish to enable. Click Launch. On the window that opens, click on View your instances on the Instances page. You should see your instance with the name that you provide in the Name Tag. When the My Instances window opens, your instance may still be in the pending state. The instance should be available within 60 seconds. When pending changes to running in the state column you can connect to the instance. Label your instance under the Name column. 6.1. Connecting to the CentOS Instance 1. Click on instances in the left navigation pane. 2. You should see your instance running. If you did not label your instance, please label your instance under the Name column. 3. Click the checkbox next to your instance. 4. Next to the Launch Instance button, there is a drop down menu called to Instance Actions. From this menu, choose Connect. 5. A pop up window will open, offering choices to login to your instance with either an SSH Shell, PuTTy, or browser Java ssh. Follow the instructions for your preferred method. You will need the private key for the key pair you used to start the instance. Here is an example of the command line when connecting from a Linux shell: ssh -i <aws_key_pair_name>.pem root@ec2-23-20-83-3.compute-1.amazonaws.com Once logged in you will have root access to the CentOS server. 6.2. Attach and prepare an EBS volume You can follow this process anytime you need to add new volumes. 1. Once your instance is running, click on Volumes under the ELASTIC BLOCK STORE section of the AWS Management Console navigation pane. 2. Click the Create Volume button, and the Create Volume dialogue appears. 3. Fill out the requested fields. Note: your new volume must be created in the same Availability Zone as your instance. Since you are creating the volume from scratch choose the default no snapshot option next to Snapshots. 4. The volume should be made available immediately. 5. Click the checkbox next to your new volume. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 7 of 23

6. Choose Attach under the More drop down menu. 7. The Attach Volume dialog appears. Choose your instance next to Instances. If your instance does not appear, most likely you did not create the volume in the same Availability Zone. Accept the default for Device, which should be should be /dev/sdf for the Helix Server 14.3.x CentOS AMI. In some cases the device is not auto populated. In this case add the device manually. 8. Finally, if you are not using the US East AMI (Helix Server 14.3.x - CentOS 5.8) your device label may be different. Knowledge of Linux devices and drivers is required. Please reference the following documentation: http://docs.amazonwebservices.com/awsec2/latest/userguide/ebs- attaching- volume.html Once the new volume is created you can repeat steps 1-8 at the beginning of this section above to attach and use the volume 6.2.1. Format your volume These steps assume you are using CentOS SCSI drivers. This step is only necessary if you are mounting a new volume that has not been previously formatted. If you are re- mounting a previously formatted drive, skip this step. Once the volume is attached, run this command to list the device: ls /dev/sd* After executing the command you will see /dev/sdf in the list. Note specific device letter may be different depending on your base AMI. To format the device, enter this command: sudo mkfs t ext3 /dev/sdf You will see a prompt to format entire device, not just one partition. Proceed by entering y After entering y the device will be formatted and end back at the prompt. 6.2.2. Mount the device: Mount the device with these commands: sudo mkdir /helix sudo mount /dev/sdf /helix Verify your device is mounted with: df h To permanently mount the device, add the following to your /etc/fstab file: /dev/sdf /helix ext3 defaults 1 1 Your volume is now ready for the installation of Helix Server. 6.3. Install Helix Server Once your Helix Server is installed you can create a snapshot of the Helix Server volume. If you terminate your instance for any reason you can then easily create a new volume from your snapshot and attach to a new instance. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 8 of 23

Please follow the standard Helix Server installation procedure as outlined in the Helix Server documentation: http://www.realnetworks.com/helix/streaming- media- guides/ http://www.realnetworks.com/helix/streaming- media- manuals/ Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 9 of 23

7. Windows 2008 R2 AMI Instance To launch an instance from the Helix Server 14.3.x public AMI: 1. Login to the AWS Management Console. 2. From the welcome screen, click the EC2 link. 3. In the Navigation pane under IMAGES click on AMIs. To use the referenced AMIs you must have your Region set to US East. Otherwise use a Windows 2008 R2 AMI of your choice. 11. In the Amazon Macine Images pane please click on the Viewing dropdown.menu and select Public Images. Select Windows as your Platform and type in Helix Server in the search field. You should see the following AMI ID: Helix Server 14.3.x WinServ2008_R2_64_Base_v3 (ami- f0d37599) 4. Find the Helix Server 14.3.x WinServ2008_R2_64_Base_v3 or another Windows AMI of your choice and click the checkbox on the far left column. 5. Click Launch in the upper left (above the Viewing drop down menu). The Request Instance Wizard will launch. The wizard is mostly self- explanatory. 6. The instance type determines the number of processors and ram available for the machine. 7. Select your preferred availability zone. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 10 of 23

8. Choose defaults for Kernel ID and RAM Disk. No need to enter user data. Leave shutdown behavior as stop and press Continue. 9. Press Continue to accept the defaults for Storage Device Configuration. 10. Entering a value for the Name key will help you identify and find your instance. Press Continue when finished. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 11 of 23

11. Choose your key pair. Please reference the following documentation for detailed information on key pairs: http://docs.amazonwebservices.com/awsec2/latest/userguide/generating- a- keypair.html http://docs.amazonwebservices.com/awsec2/latest/userguide/using- credentials.html#using- credentials- keypair Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 12 of 23

12. Choose your security group. Please reference the table in Appendix A when configuring your security group. 13. Review the settings and click Launch to start the instance Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 13 of 23

14. A window will announce the instance is launching. Click on Close and go back to Your instances. You should see your instance in the pending state. 7.1. Connecting to the Windows Instance 1. Click on instances in the left navigation pane. 2. You should see your instance running. If you did not label your instance, please label your instance under the Name column. 3. Click the checkbox next to your instance. 4. Next to the Launch Instance button, there is a drop down menu called to Instance Actions. From this menu, choose Connect. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 14 of 23

5. The following window will open giving you a choice to login with your credentials or download a preconfigured RDP shortcut. It is best to download the shortcut file. You will then need to retrieve the Windows password. The process for retrieving the Windows password is described in the Console Connect wizard after clicking on Connect as described above. The instructions that follow are standard connections for RDP (Remote Desktop Protocol) and mounting of a disk in Windows Server. Hint: If when setting up the RDP, you select details and modify options to configure local resources, you can make your local windows disk accessible to the remote windows machine, thus enabling you to easily transfer files, without having to setup an ftp or other file transfer method. 6. Click on connect to launch RDP session Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 15 of 23

7. Click on Yes to accept the certificate and connect to your instance 7.2. Attach and prepare an EBS Volume You can follow this process anytime you need to add new volumes. 1. Once your instance is running, click on Volumes under the ELASTIC BLOCK STORE section of the AWS Management Console navigation pane. 2. On the right hand side pane, on the top menu, click Create Volume Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 16 of 23

3. On the window that pops up, select the volume size and availability time zone. The time zone must be the same as the AMI otherwise it will not show up for selection. 4. Once the volume has been created, find it in the list of EBS volumes and edit the tags to name with a name that you can recognize. Remember that the account pays for the size of the storage. 5. After finding and selecting your volume, click on the More drop down button and select Attach Volume 6. In the pop window that opens select your instance and the device should auto populate. Click on Yes Attach Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 17 of 23

7.2.1. Mount and Format your drive The instructions that follow show how to activate and mount the volume in windows server 2008. 1. Open Server Manager and select Storage then Disk Management You will see which disks are online or offline. In this picture Disk 2 is my recently mounted volume that I will now bring online and format. 2. Right click on the disk that you want to work on and select online, to bring it online. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 18 of 23

3. Once online, right click on it an initialize. 4. A window will pop up asking what type of partition you want. Select MBR 5. After it finishes formatting, give it a volume. Right click and select New Simple Volume Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 19 of 23

6. A wizard window will pop up. Click next 7. Allocate the space to the new disk. 8. Assign a letter to the disk Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 20 of 23

9. Choose NTFS for file system and a volume label of your choice 10. Click Finish Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 21 of 23

11. Finally right click on the disk and Mark the partition as Active: 7.3. Install Helix Server Once your Helix Server is installed you can create a snapshot of the Helix Server volume. If you terminate your instance for any reason you can then easily create a new volume from your snapshot and attach to a new instance. Please follow the standard Helix Server installation procedure as outlined in the Helix Server documentation: http://www.realnetworks.com/helix/streaming- media- guides/ http://www.realnetworks.com/helix/streaming- media- manuals/ Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 22 of 23

Appendix A The following chart can be referenced when configuring your Amazon Web Services EC2 security group. Feature Default Ports Description RTSP/TCP Streaming (Control Channel) 554 Required for streaming to RTSP devices (RealPlayer, Android) RDT or RTP/RTCP 6970-32000 Corresponding data and reporting channel for RTSP RTMP/TCP Streaming 1935 Required for streaming to Flash based players HTTP/TCP Streaming 80 Required for HTTP Live streaming to ios or Android and progressive download Monitoring Port 9090 Required for connecting the Server Monitor remotely Admin Port (HTTP) Randomly assigned Required to access the Helix Server Admin system. Secure Admin Port (HTTPS) Randomly assigned Required to access the Helix Server Admin system via HTTPS Channel Control Port (HTTP/TCP) 8008 Access required for applications using the fast- channel switching feature API. Playlist Control Port(HTTP/TCP) 8009 Access required for applications using the server- side playlist API. File System Control Port(HTTP/TCP) 8010 Access required for applications using the server- side playlist API. Doc: Helix_AWS_Quickstart_Guide-14.3.0-072412.docx Page 23 of 23