The Controller image is available under My AMIs tab in AWS. You have to create a launch template using the Controller AMI. For auto scaling groups feature, a launch template has to be defined first before creating an auto scaling group. While creating an auto scaling group, this launch template has to be selected to launch new Virtual IPS Sensor instances. The Manager IP address and Cluster name are defined in the launch template.
To create a launch configuration for auto scaling groups, follow the steps below:
In AWS, go to Services → Compute → EC2.
In the left panel, under Auto Scaling, click Auto Scaling Groups.
Select Launch templates. In the Launch templates page, click Create launch template.
.png)
The Create launch template page is displayed.
Go to Launch template name and description and enter the required Launch template name for the configuration.
.png)
Go to the Application and OS Images (Amazon Machine Image), search and select the required AMI from Community AMIs tab.
.png)
Go to Instance type and select the instance type as c5.xlarge (vCPUs: 4, Memory 8GB).
.png)
Go to Key pair (login), you can either choose an existing key pair from the drop-down or create a new key pair.
.png)
Go to Network settings, select the required subnet from the drop-down or create a new subnet, if required. In the Firewall (security groups), you can create a new security group to define the firewall rules to control traffic to the Sensor or choose an existing security group.
.png)
Go to Storage (volumes) and verify if Size (GiB) is 64 and Volume type is gp2.
.png)
Note
The management and data subnets should be configured in the same availability zone as the instance for the deployment to be successful.
Go to Advanced details, in the User data field define the Manager IP address, Cluster name, and Traffic Source.
Option
Definition
Purchasing option
Request Spot Instances to name your own price for the instance types and lower your overall computing cost for time-flexible interruption-tolerant tasks
Monitoring
Enables you to monitor, collect, and analyze metrics about your instances through Amazon CloudWatch
EBS-optimized instance
Enables additional, dedicated throughput between Amazon EC2 and Amazon EBS, and therefore, improved performance for your Amazon EBS volumes
RAM disk ID
A RAM disk that contains the necessary drivers (such as Xen drivers or video drivers) to make the chosen kernel work
Kernel ID
Available kernels that you can use for your instance
Metadata accessible
Turn off access to your instance metadata by disabling the HTTP endpoint of the instance metadata service. If a value is not specified, the default option is to enable the HTTP endpoint.
Metadata version
You can run both V1 and V2, or just V2. If you do not specify a value, the default value is V1 and V2.
Metadata response hop limit
The number of network hops that the metadata token can travel. Maximum value is 64. If you do not specify a value, the default value is 1.
User data
You can specify user data to configure an instance or run a configuration script during launch. If you launch more than one instance at a time, the user data is available to all the instances in that reservation.
Note
You have to provide the Manager IP address, Cluster name, subnet, and the security group name in the script. For the script to define the parameters, see the topic High level steps to configure an auto scale group.
For a Probe-based solution, provide the Traffic Source as PROBE.
.png)
Review all configured details in the Summary and click Create launch template.
.png)
To delete a launch template, select the launch configuration, click Actions, and then click Delete launch template.