Skip to main content

Troubleshooting Elastic Load Balancing Connectivity in AWS

Hands-On Lab

 

Photo of Mark Richman

Mark Richman

AWS Training Architect II in Content

Length

00:30:00

Difficulty

Intermediate

The goal of this hands-on lab is to fix the broken environment and achieve the goal as outlined below. The first video in this lab presents the scenario and the goal, while the second video provides the solution (if needed). Do your best to solve the connectivity issue without viewing the solution video. Goal: Fix the connectivity issue in the AWS environment so that you can view the Linux AMI/Apache test page of the provisioned EC2 instances via the ELB's DNS name. Good luck!

What are Hands-On Labs?

Hands-On Labs are scenario-based learning environments where learners can practice without consequences. Don't compromise a system or waste money on expensive downloads. Practice real-world skills without the real-world risk, no assembly required.

Troubleshooting Elastic Load Balancing Connectivity in AWS

Introduction

In this hands-on lab, we're going to fix the connectivity issue in the AWS environment so we can view the Linux AMI/Apache test page of the provisioned EC2 instances via the ELB's DNS name.

Solution

Log in to the live AWS environment using the credentials provided. Make sure you're in the N. Virginia (us-east-1) region throughout the lab.

Hint #1

The Issue

The ELB's security group does not allow HTTP traffic.

How to Fix the Issue

Add an allow rule for HTTP traffic (port 80) to the ELB's security group.

  1. Navigate to EC2 > Load Balancers.
  2. With the load balancer selected, scroll to the Security section in the Description section, and click the listed security group.
  3. With the security group selected, scroll to the Inbound section, and click Edit.
  4. Change the Type to HTTP, and click Save.
  5. Click Load Balancers in the left-hand menu.
  6. Copy the load balancer's DNS name in the Description section, and paste it into a new browser tab. The page won't be able to load.

Hint #2

The Issue

EC2 instance health checks are not passing.

How to Fix the Issue

Change health check "ping port" on the ELB to port 80.

  1. Back in the AWS console, click the Instances tab on the load balancers page, where we'll see the instances associated with our load balancer are marked as OutOfService.
  2. In the Health check tab, click Edit Health Check.
  3. In the dialog, change Ping Port to 80, and click Save.
  4. Back in the Instances tab, we should see they're now listed as InService.
  5. Reload the load balancer DNS in the browser, which should now display the Linux AMI/Apache test page.

Conclusion

Congratulations on completing this hands-on lab!