--- title: "Virtual Service Router deployment on AWS" slug: "virtual-service-router-deployment-on-aws" updated: 2025-04-17T14:59:39Z published: 2025-04-17T14:59:39Z canonical: "docs.zpesystems.com/virtual-service-router-deployment-on-aws" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zpesystems.com/llms.txt > Use this file to discover all available pages before exploring further. # Virtual Service Router (vSR) deployment on AWS # Nodegrid vSR on Amazon Web Services AWS This documentation details creating a Virtual Service Router VM instance on [Amazon Web Services AWS](https://aws.amazon.com/). The objective is to create a Nodegrid vSR instance that acts as a concentrator/hub to interconnect with other Nodegrid (e.g., Hive SR, Bold SR, or Mini SR). The following diagram, *Diagram-1*, shows the expected result: ![Diagram-1](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/awsinstance.svg) This is the process: 1. Licensing and Instance requirements 2. AWS Credentials 3. Nodegrid vSR AMI image 4. Create a Nodegrid vSR instance 5. Web Access to the Nodegrid vSR ## 1. Licensing The Nodegrid vSR product has five hardware license tiers. vSR VM can run for 30 days with no restraints, but after 30 days without a license, the software restrict vSR use. | Tier | CPU | RAM | Equivalent | | --- | --- | --- | --- | | 1 | 2vCPU | 4GiB | AWS c5.large | | 2 | 4vCPU | 8GiB | AWS c5.xlarge | | 3 | 4vCPU | 16GiB | AWS m5.xlarge | | 4 | 8vCPU | 32GiB | AWS m5.2xlarge | | 5 | 16vCPU | 64GiB | AWS m5.4xlarge | ## 2. AWS Credentials The following is assumed: - AWS user with privileges to create [EC2](https://aws.amazon.com/ec2/) and [VPC](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) resources - [AWS Region and Zone](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) selected to deploy the instance ## 3. Nodegrid vSR AMI image Request access to VSR AMI image The Nodegrid vSR AMI is distributed by ZPE Systems (currently, not publicly available in the *AWS Marketplace AMIs*/ *Community AMIs*). To request the AMI, contact support@zpesystems.com. Support will require the customer AWS account ID and will then share the current AMI image with the customer. The AMI image is by default shared to us-east-2 To verify the AMI availability: 1. Access [https://console.aws.amazon.com/](https://console.aws.amazon.com/) and select Region and Zone 2. Select **Images > AMI Catalog > My AMIs** 3. Verify the image, e.g., *Nodegrid_Platform_v5.8.3_20230221.iso* ![aws-ami-catalog.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/aws-ami-catalog.png) ## 4. Create a Nodegrid vSR instance This is the simplified procedure to deploy an EC2 instance in AWS (some resources shown in the *Diagram-1* are automatically created with pre-defined AWS default configurations. 1. Access [https://console.aws.amazon.com/](https://console.aws.amazon.com/) and select the preferred Region and Zone 2. Select **Images > AMI Catalog > My AMIs** 3. Select the Nodegrid vSR image, e.g., *Nodegrid_Platform_v5.8.3_20230221.iso* 4. Select **Launch Instance with AMI** 5. Enter **Instance Name**, e.g., *vsrAWS-1* 6. Select **Instance type**, e.g., *t3.medium* 7. Create or select a **Key pair** 8. On *Network settings* - Select **Create security group** - Select **Allow SSH traffic from** *Anywhere* (adapt this rule as needed) - Select **Allow HTTPS traffic from the internet** - Select **Allow HTTP traffic from the internet** 1. Go to **Network settings > Edit** - **Create a new default VPC**, then refresh the drop-down list and select it - On **Auto-assign public IP**, select **Enable** - On **Create security group**: enter Name and Description, e.g., *zpe-vsr* and *Security Group for Nodegrid vSR* ![aws-instance-network-settings.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/aws-instance-network-settings.png) 1. **Configure storage** - Define disk size, e.g., 64 GiB, and select **gp2** 1. Select **Launch Instance** ![aws-instance-creation.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/aws-instance-creation.png) 2. **Launch an instance Success** ![aws-instance-creation-success.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/aws-instance-creation-success.png) 3. Click **View all instances**: on the list, select the created instance and look for the assigned public IP ## 5. Web Access to the Nodegrid vSR 1. In a browser, open **https://Public-AWS-IP** 2. Log in to the Nodegrid vSR WebUI. Default credentials are: - user: admin - password: admin 1. Follow the steps to change the password 2. **Congratulations!** You have successfully deployed a Nodegrid vSR instance. ![web-ui.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/web-ui.png) ## 6. Enroll vSR to ZPE Cloud A Nodegrid vSR is managed on ZPE Cloud. The new deployed unit must be enrolled to the customer's ZPE Cloud instance. 1. Login to your ZPE Cloud account [Global](https://zpecloud.com) , [EU](https://zpecloud.eu) or onPrem 2. Go to **SETTINGS :: ENROLLMENT :: CLOUD** 3. Copy the **Customer Code** and **Enrollment Key** (required to claim the vSR). ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 4. In a browser, login to vSR with **https://Public-AWS-IP**. 5. Go to **Security :: Services** and enable ZPE Cloud service ![security-zpecloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/security-zpecloud.png) 6. Go to **System :: Toolkit :: Cloud Enrollment** ![system-toolkit](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit.png) 7. Enter the following information 1. **URL**: URL of the zpecloud instance, default https://zpecloud.com 2. **Customer Code**: Use the copied Customer Code from the Cloud Instance 3. **Enrollment Key**: Use the copied Enrollment Key ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 8. Click **ENROLL** ![system-toolkit-cloud-enrolment-success](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit-cloud-enrolment-success.png) 9. The unit is enrolled on ZPE Cloud and become available in ZPE Cloud under **DEVICES :: AVAILABLE**. ![devices-available](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/devices-available.png) 10. To start management of the vSR, select and click on **ENROLL**. 11. When enrolled, the vSR is managed on ZPE Cloud like any other Nodegrid device. ## 7. VSR Firmware Update The created VSR instance can be updated using all officially supported methods, similar to all other appliance, including ZPE Cloud and firmware updated via the WebUI or CLI. The AMI image is required only for the initial deployment.