Skip to main content

Creating a Virtual Kraken Server

Signing in to AWS

  1. Sign in to your AWS account: https://console.aws.amazon.com
  2. After you have successfully logged in to the AWS portal, click Services > EC2.

Creating a Virtual Instance

  1. On the EC2 Dashboard, click Launch Instance.
  2. Click AWS Marketplace.
  3. Type "Haivision" in the search box and press Enter to find the Kraken image.
  4. Click the Select button corresponding to the version of the Amazon Machine Image (AMI) you wish to use, PAYG or BYOL.
  5. Review the product and pricing details, and then click Continue.
  6. Choose an Instance Type, and then click Next: Configure Instance Details:

    Important

    • Only instances built on the Nitro system are supported. Please see the following link for a list of compatible instances: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances
    • For high bandwidth streams or critical viewing requirements, we recommend using Compute Optimized C5 Instances (e.g. c5.xlarge, c5.2xlarge, etc.) tiers, as they are optimized for compute-intensive workloads and have high-performance network I/O.


    Note

    We do not recommend using tiers with low CPU resources, because the resulting performance of your server will be inadequate.

    Note

    For high bandwidth streams or critical viewing requirements, we recommend using compute-optimized (C5) instance tiers, as they are optimized for compute-intensive workloads and have high-performance network I/O. c5.2xlarge is generally recommended for Kraken AWS.

  7. Modify your Instance Details as needed, and then click Next: Add Storage:

    Note

    You may wish to choose Enable under Auto-assign Public IP to give your server an IP address reachable from any location.

  8. Set the amount of storage space you wish to make available to the server. For Kraken, set 75GB as minimal. Then click Next: Add Tags:


    Note

    You may wish to choose Delete on Termination to have the storage space automatically removed if you cancel your subscription for the server instance.

  9. Apply one or more tags (such as a Name) to the server, and then click Next: Configure Security Group:

     
  10. Create a new security group, or select from a list of existing groups. Make sure you have the following ports open:
    • Port 443 for HTTPS access to the web interface
    • Port 22 for SSH access to the Console UI interface
    • A custom port to allow incoming UDP traffic, such as SRT streams (use Custom UDP Rule). See SRT for more information.
  11. Click Review and Launch.
  12. Review your settings, and make any necessary corrections or changes. When you are satisfied, click Launch:
    Launch Instances screen
  13. When prompted, select or create a public/private RSA key pair that is used to authenticate SSH sessions, and then click Launch Instances:

    Launch Instances screen - Select Key Pair

    Note

    SSH access to the Console UI is only allowed via SSH public key.

  14. In a few moments, a Launch Status page appears, informing you that your instance is in the process of launching. Creating your server instance can take up to several minutes. At any time, click View Instances to see more details:
  15. After the Instance State changes to "running", reboot the virtual server by selecting it in the AWS View Instances page and clicking Actions > Instance State > Reboot.
    Reboot
  16. Confirm rebooting in the confirmation dialog box.
    Confirm Reboot
  17. Return to the AWS View Instances page. In the row corresponding to your server, take note of the Public IP address and Instance ID assigned by AWS to your instance. The Instance ID is the default password for signing into Web Interface.

At this point, your virtual server is up and running!

  • If you have created a BYOL instance, before continuing you need to license your server. See Licensing Your Server.
  • If you have created a PAYG instance, you are ready to sign in and begin using your server. See Signing in to Your Server.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.