This guide covers the launch and network configuration of the WebStream server within the AWS Cloud. The server works with an Access Anywhere appliance that may be deployed in a different region or cloud.
Once network configuration is complete return to the Getting Started: WebStream On-Premises documentation to continue setup.
For general documentation see WebStream.
A single WebStream Server provides streaming services to one or more Access Anywhere instances. The server must be accessible by each Access Anywhere instance as well as web browsers through a public endpoint.
The WebStream appliance may be launched from the AWS Marketplace. When deployed with a single Access Anywhere appliance the architecture may look like this:
The appliance uses the following AWS services:
This guide walks through deploying the WebStream to your environment as a software appliance. An instance will be launched directly from the AWS Marketplace. You'll have the ability to choose the target region and size of the instance for your requirements. After the appliance is started you'll set up the network and connect to an existing Access Anywhere instance.
This guide is for IT infrastructure architects and DevOps professionals who are deploying Access Anywhere on AWS.
To follow this guide a user should have some familiarity with the AWS Console and with a Linux shell. They may require support from a network administrator to create a DNS record, and from an IT administrator if a corporate SSL certificate is required.
Following this guide, the WebStream server can be deployed in under thirty minutes.
You will need the following information before you can complete the setup:
Open the page AWS Marketplace: WebStream Server.
Select “Continue to Subscribe”.
Review terms and select “Continue to Configuration”.
Select your preferred Region and then select “Continue to Launch”
This page allows you to launch the instance directly from this webpage, or through the EC2 launch instance wizard.
Leave the setting as Launch from Website (Recommended). Instructions for launching from EC2 instead are provided in the section Launch Through EC2.
Review settings.
Default is c5.2xlarge:
Select a VPC.
Choose a public subnet.
Select “Create New Based on Seller Settings”.
Add a name and description such as “NAA WebStream”.
Do NOT change the Source (IP or Group) to “My IP” as this setting incorrectly assigns an internal AWS IP address.
Select “Save”.
The following inbound firewall rules are required.
Type | Protocol | Port Range | Source | Description |
---|---|---|---|---|
SSH | TCP | 22 | 0.0.0.0/0 | SSH access for initial network configuration |
HTTP | TCP | 80 | 0.0.0.0/0 | Used by Certbot |
HTTPS | TCP | 443 | 0.0.0.0/0 | Access point for Access Anywhere and Web browsers |
Add a name and description such as “WebStream Server”.
Do NOT change the Source (IP or Group) to “My IP” as this setting incorrectly assigns an internal AWS IP address.
Select “Save”.
Amazon EC2 uses SSH-2 RSA keys for SSH which is required to complete the configuration. A public/private key pair can be assigned or created.
Choose an existing Key Pair or create a new one.
Select the “Launch” button to deploy.
Select EC2 Console to see the instance running in the region you selected.
Add a Name by clicking in the empty Name box and entering “WebStream”.
Jump to the next step Configure Public Endpoint.
If you did not “Launch from the website”, follow these steps to launch the instance.
Choose at least an c5.2xlarge, c5a.xlarge or c6a.2xlarge instance. For example:
For example,
Family | Type | vCPUs | Memory (GiB) | Instance Storage (GB) | Network | Notes |
---|---|---|---|---|---|---|
c5 | c5.2xlarge | 16 | 8 | EBS Only | Up to 10 Gigabit Ethernet | Recommended |
Select “Next: Configure Instance Details”.
Check the following setting:
Select “Next: Add Storage”.
Change the size and Volume Type which will give 3000 IOPS:
You might wish to change “Delete on Termination” to False to prevent your instance from being accidentally terminated through Amazon EC2.
You can also encrypt the root volume here.
Select “Next: Add Tags”.
No changes, select “Next: Configure Security Group”
Create a new security group for the controller. For example,
Security group name: WebStream Controller
Type | Protocol | Port Range | Source | Description |
---|---|---|---|---|
SSH | TCP | 22 | Anywhere 0.0.0.0/0, ::/0 | SSH access for initial network configuration |
Custom TCP Rule | TCP | 8081 | Anywhere 0.0.0.0/0, ::/0 | User interface for administration |
Custom UDP Rule | UDP | 8445 | Anywhere 0.0.0.0/0, ::/0 | IPv4, IPv6 public endpoint for WebStream |
Select “Review and Launch”.
Select [Launch] to bring up the dialog to choose or create a public/private key pair that will allow you to SSH into the instance.
Select Launch Instances.
To continue configuration see Configure Public Endpoint.