Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Install Routing Director on AWS

This topic provides an overview of deploying Juniper Routing Director on Amazon Web Services (AWS). It outlines the installation prerequisites, required AWS permissions, and the overall workflow for installation. Use this section to understand the deployment process and prepare your cloud environment before beginning the setup.

Deploy Routing Director on Amazon Web Services by using a manual, nonintegrated model that runs the cluster on Amazon Elastic Compute Cloud (Amazon EC2) instances. This deployment model provides north-south access by using AWS Network Load Balancers (NLBs) in front of Kubernetes NodePort services.

Important:

Ensure that the administrator performing the installation is AWS Certified or has strong working knowledge of AWS.

Perform the following steps to install and deploy the Routing Director cluster on AWS:

  1. Import Routing Director VMDK image files to Amazon Machine Image (AMI). See Import Routing Director Image Files to AMI.

  2. Create the security groups to allow traffic to and from the Routing Director cluster nodes. See Create the Security Groups.

  3. Create and launch the EC2 VMs. See Launch the EC2 VMs.

  4. Create the target groups and load balancers to enable access to the Routing Director cluster and its applications. See Create the Target Groups and Load Balancers.

  5. Deploy the cluster. See Deploy the cluster.

Prerequisites to deployment

Ensure that you have the following information available before you install Routing Director.

  • Login credentials to AWS with permission to create, modify, and delete VMs, security groups, load balancers, IAM roles and policies, along with access to the S3 bucket.

    For information on AWS CLI settings, see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html.

  • The S3 bucket must be preconfigured.

  • The vmimport role must be created.

  • A VPC subnet that can access the Internet on any NTP server.

  • External DNS names for the following:

    • Hostname for generic ingress shared between the Routing Director Web GUI, NETCONF, and gNMI-term access

    • Hostname for Active Assurance test agent gateway

    • Hostname for PCE server

    • Hostname for routing observability.

  • Install the aws-cli utility.

  • Access + secret key to run aws-cli to upload and import images.

Start the deployment process by importing the Routing Director image files to Amazon Machine Image (AMI). Go to Import Routing Director Image Files to AMI.