Configuring Riverbed Edge on an AWS VM
Riverbed IQ's data sources are network monitoring applications such as Riverbed Technology's Riverbed NetIM and Riverbed NetProfiler, which forward observability data to Riverbed IQ for correlation and analysis via Riverbed Edge, which handles data source connections for IQ. Each data source must be configured explicitly to communicate with Edge.
Follow these steps to configure an Riverbed Edge instance and a data source:
- Create new non-admin user accounts on your Riverbed Technology data sources. For NetProfiler, use the role Operator. For NetIM, use the role ALLUVIO_IQ. For AppResponse, use a non-admin role with permissions for Feature Settings and Definitions set to Full Control.
-
In the Riverbed IQ web UI, open the Data Sources page and click Add an Edge to display the Add an Edge wizard.
-
Specify the Riverbed Edge instance name and virtual machine type, and click Next.
-
If necessary, specify the connection type for the Edge:
-
If the Edge does not have access to the Internet, specify a proxy to use and enable Use Websockets.
-
If the Edge has only port 443 open to the Internet, enable Use Websockets.
-
If neither condition applies, simply click Next.
-
-
Inspect the summary of the Edge definition and click Submit to make it manageable by IQ. IQ shows you a brief summary of the next steps you need to execute.
Note: Riverbed IQ employs a shared ownership model in which Riverbed supplies an Edge image for deployment on top of a customer-owned and managed VM.-
Download the Edge cloud-init file using the provided external link URL.
-
Go to the external, official Ubuntu VM download page to retrieve a supported version to set up the customer-owned and managed VM that will host Riverbed Edge.
-
Deploy and prepare your VM for Riverbed Edge.
-
Use the Edge cloud-init file to configure your target VM environment for Edge.
-
-
Select the Edge in the Data Sources page and click on the ... menu. Choose Obtain VM Image to open an external web page for AWS Marketplace for the Ubuntu VM download page to retrieve a supported version in order to set up the customer-owned and managed VM that will host Riverbed Edge.
- Select the Edge and click on the ... menu. Choose Download cloud-init to obtain the necessary zip file. Deploy a VM using the provided OVA file and the contents of the cloud-init zip file (specifically, the user-data file).
-
The recommended instance type requires the following resources: RAM: 16GB, vCPU: 4 cores, and Storage 300GB. (For example, t2.xlarge.)
-
After configuration, click Launch through EC2 in AWS. AWS will prompt you about “Selecting an existing key pair or create a new key pair”. Here, select “Proceed without a key pair” to complete the deployment process.
-
While launching the instance, under Advanced Details, paste the content of the user-data file (included in the cloud-init zip file) into the User Data field.
Upon first boot, the initial configuration will be set. (This may take a few minutes; wait for at least five minutes before attempting log in to the VM.) - If you use a firewall with a domain whitelist or a list of blocked ports, make sure to modify it to whitelist DNS names and open ports for the deployed Edge as indicated in Firewall Rules.
-
Check the Riverbed Edge instance's health:
-
Verify that the Status for the Edge is green on the Data Sources page. This page does not refresh automatically, so refresh it explicitly if you are watching for a status change.
-
Contact Riverbed Technology in case of any errors or issues
-
-
Select the Edge in the Data Sources page and click ..., then click Connect a Data Source to display the Connect a Data Source dialog and follow the procedure for Adding a Data Source. Click Submit to dismiss the Connect a Data Source dialog when you're finished.
-
Select the Edge in the Data Sources page and click the arrowhead to its left; this will show the status of connected data sources. The web UI should show green status for the Edge and connected data sources.
-
Note: See Troubleshooting Riverbed Edge Status for information about identifying and correcting problems with connecting to Riverbed Edge