Installing in AWS
Introduction
This guide describes the process for deploying a Session Smart Conductor and a Session Smart Router (SSR) in AWS.
Mist-managed SSR installations are now available through AWS. However, SSR Version 6.x installed as an AWS image will only support Mist-managed routers. It will not support a conductor-managed deployment. See Installing a Mist-Managed Router in AWS for details.
If you wish to install SSR Version 6.x on a conductor and conductor-managed router in AWS, the suggested procedure is to first install an earlier version of SSR software such as 5.x.x, and upgrade through the conductor.
The process for deploying Conductor-managed networks consists of the following steps:
- Selecting the AMI.
- Deploying a Session Smart Conductor.
- Deploying a Session Smart Router.
Proceed to the next section Selecting the AMI.
Version | Supported Modes |
---|---|
5.x | Conductor and Conductor-Managed Router |
6.x | Mist-Managed Router |
Selecting the AMI
There are different AMIs (images) available for the Juniper Session Smart Networking Platform offering:
- Private: For cases where there is no access to the SSR repositories (no internet connection) from the AWS environment where the software will be deployed, a Private Offer can be issued to your AWS account via the AWS Marketplace. To request access to a private offer, refer to Requesting access to a Private offer for additional information.
- Hourly: This provides a free trial period for 30 days and an hourly software cost after the trial expires. This plan is recommended for Proof of Concepts and Trials only. Software upgrades and deployments outside of the cloud, (on premises) require a token or certificate. The software can not be purchased via the marketplace. Refer to the Session Smart Networking Platform (PAYG) offering.
Once you have selected the AMI that better suits the needs of your deployment, proceed to the section Session Smart Conductor Deployment to deploy a Session Smart Conductor, or proceed to the section Session Smart Router Deployment to deploy a Session Smart Router.
SSR Version 6.x installed as an AWS image will only support Mist-managed routers. It will not support a conductor-managed deployment.
Requesting access to a Private Offer
There is no software cost associated with deploying the Private image, the cost of running the EC2 instance is the only cost (AWS compute cost). Please also note that software upgrades and deployments outside of the cloud (e.g., on premises) will not be possible without a token or certificate.
To request access to a Private offer:
- Locate the account ID of the AWS account where the deployment of the software is going to take place:
- Open the AWS Console.
- On the right at the top of the screen, click on the downward arrow next to your username, and the account ID will be displayed.
- Make a note of your account ID.
- Contact your Juniper Networks Sales representative and provide:
- The Account ID of the AWS account that will be used for the deployment.
- The version of the Session Smart Networking software. Your Juniper Sales representative will assist you if you don't know the version you need for your deployment.
-
Your Juniper Sales representative will email you the private offer.
-
When you receive the email containing the private offer, open it and review / accept the terms and conditions.
Session Smart Conductor Deployment
Use the following information to deploy a Session Smart Conductor in AWS.
Requirements
The following infrastructure must exist in your AWS account:
- A VPC where the Conductor will be deployed.
- The existing VPC is segmented with at least one subnet.
- The subnet is reachable for SSH and HTTPs access for administration purposes.
- The Session Smart Routers managed by this Conductor must be able to reach the IP address of the Conductor in this subnet.