The Controller image is available under My AMIs tab in AWS. You have to create a launch configuration using the Controller AMI. For auto scaling groups feature, a launch configuration has to be defined first before creating an auto scaling group. While creating an auto scaling group, this launch configuration has to be selected to launch new Virtual IPS Sensor instances. The Manager IP address and Cluster name are defined in the launch configuration.
To create a launch configuration for auto scaling groups, follow the steps below:
Task
- In AWS, go to Services → Compute → EC2.
- In the left panel, under AUTO SCALING, click Launch Configurations.
-
Click
Create launch configuration.
- Under Create Launch Configuration, enter the Name for the configuration.
-
Go to the
Amazon machine image (AMI) section, search and select the required AMI.
-
Under the
Instance type section, click
Choose instance type. Select the instance type as
c4.large (vCPUs: 2, Memory 3.75 GB), and click
Choose.
-
In the
Additional configuration - optional section, define the Manager IP address and the Cluster name.
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. IAM instance profile IAM roles allow you to manage permissions of IAM users and AWS services to your EC2 resources. Note
Select the IAM role you created with the "Network Administrator" rights enabled. For the script to create an IAM role, see the topic High level steps to configure an auto scale group.
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 Advanced details Kernel ID Available kernels that you can use for your instance RAM disk ID A RAM disk that contains the necessary drivers (such as Xen drivers or video drivers) to make the chosen kernel work 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.
IP address type When you launch an instance into your Amazon Virtual Private Cloud (VPC), you can optionally assign a public IP address to it. -
Under the
Storage (volumes) section, define the database server details.
Option Definition Device The available device names for the volume. Depending on the block device driver of the selected AMI's kernel, the device may be attached with a different name than what you specify. Snapshot A snapshot is a backup of an EC2 volume that's stored in S3. Size (GiB) Volume size must be greater than zero or the size of the snapshot used. Note
Use the default size as 64 GiB.
Volume Type General Purpose (SSD) volumes can burst to 3000 IOPS, and deliver a consistent baseline of 3 IOPS/GiB. IOPS The requested number of I/O operations per second that the volume can support Throughput Throughput that the volume can support is specified for Streaming Optimized volumes: ST1 and SC1. Delete on Termination EBS volumes persist independently of the running life of an EC2 instance. Encrypted Volumes that are created from encrypted snapshots are automatically encrypted, and volumes that are created from unencrypted snapshots are automatically unencrypted. If no snapshot is selected, you can choose to encrypt the volume. Note
The management and data subnets should be configured in the same availability zone as the instance for the deployment to be successful.
-
In the
Security groups section, you can create a new Security Group to define the firewall rules to control traffic to the Sensor or choose an existing Security group.
Option Definition Assign a security group Create a security group or assign an existing security group. Security group name Name for the security group Description Description for the security group Rules Type The protocol to open to network traffic. You can choose a common protocol, such as SSH (for a Linux instance), RDP (for a Windows instance), and HTTP and HTTPS to allow Internet traffic to reach your instance. You can also manually enter a custom port or port ranges. Protocol The type of protocol, for example TCP or UDP. It provides an additional selection for ICMP. Port Range For custom rules and protocols, you can manually enter a port number or a port range. Source Type You can configure either Custom IP, or it can be accessed from anywhere. Source Determines the traffic that can reach your instance. Specify a single IP address, or an IP address range in CIDR notation (for example, 203.0.113.5/32). -
In the
Key pair (login) section, you can either choose an existing key pair or create a new key pair, and click
Create launch configuration. The instance is now launched.
Note
Even though you provide a key pair, you cannot login to the Sensor instance using the key pair. You should use the Sensor's user account to login.
- To delete a launch configuration, select the launch configuration, click Actions, and then click Delete launch configuration.