From the course: AWS: Automation and Optimization

Verify the Auto Scaling group - Amazon Web Services (AWS) Tutorial

From the course: AWS: Automation and Optimization

Start my 1-month free trial

Verify the Auto Scaling group

“

- [Instructor] Now that we've created the auto scaling group, it's time to look at the changes. With the auto scaling group selected, under the Details tab, we notice that our desired capacity is two, minimum is two, and maximum is two. This is because we chose to perform manual scaling, meaning, we'll scale out or scale in when required. Under the Activity History tab, you will notice that two new EC2 instances have been launched, and here are the instance IDs. The Scaling Policies tab does not show you any scaling policy because we haven't configured one. The Instances tab will show you the details of the EC2 instances. You will notice the EC2 Instance IDs, Lifecycle, Launch Configuration, Availability Zone, and Health Status. In this case, both the instances are healthy. The life cycle shows as InService, meaning both the instances are serving traffic. Next, we'll click on Instances in the left navigation bar. This shows both the EC2 instances that have been launched. Click on a specific instance, and then click on Tags. This shows the tags that have been applied. In this case, there are two tags. The first tag is called Department, which has a value of Sales, and this is the one that we defined while creating the auto scaling group. The second tag is the name of the auto scaling group. In this case, myASG. Notice that both the instances have a public IP address assigned. This is from the setting that we configured in the launch configuration. While creating the auto scaling group, we also configured the usage, often elastic load balancer. Let's verify this. Scroll down to left navigation bar and click on Load Balancers. This is the classic load balancer I had created earlier and configured under the auto scaling group. Clicking on the Instances tab shows the EC2 instances registered behind the load balancer. The status is InService, meaning they are both serving traffic. Let's verify this. Click on the Description tab, and copy the DNS name of the load balancer. Open a new browser window or tab, paste the DNS name, and hit enter. You will notice a text that says served from, and then the instance host name. This confirms that the script we wrote in the User Data section while configuring the launch configuration works fine. If you refresh the browser, you will notice the host name change. This is because the traffic is being served from the other EC2 instance. This confirms that the auto scaling group has launched the required number of instances, and the auto scaling group has also registered the instances behind the elastic load balancer.

Contents