Health checks with Route 53 in AWS - Mini Project: Build & Apply

Health checks with Route 53

📖 Scenario: You are managing a website hosted on AWS. To keep your site reliable, you want to monitor if your web server is healthy. AWS Route 53 can check your server's health and help direct visitors only to working servers.

🎯 Goal: Build a Route 53 health check configuration that monitors a web server's health by checking its HTTP response on port 80.

📋 What You'll Learn

Create a health check resource with a unique name

Configure the health check to use HTTP protocol on port 80

Set the IP address of the server to be monitored

Specify the request path as '/' to check the homepage

Set the failure threshold to 3 to mark unhealthy after 3 failed checks

💡 Why This Matters

🌍 Real World

Route 53 health checks help keep websites reliable by monitoring server health and routing traffic only to healthy servers.

💼 Career

Understanding how to configure health checks is essential for cloud engineers and site reliability engineers to maintain uptime and performance.

1

Create the basic health check resource

Create a variable called health_check_config as a dictionary with these exact keys and values: 'IPAddress' set to '192.0.2.44', 'Port' set to 80, and 'Type' set to 'HTTP'.

AWS

# Your code here

Hint

Think of health_check_config as a box holding your server's IP, port, and protocol.

2

Add the request path to check

Add a key 'ResourcePath' with the value '/' to the existing health_check_config dictionary.

AWS

health_check_config = {
    'IPAddress': '192.0.2.44',
    'Port': 80,
    'Type': 'HTTP'
}
# Add 'ResourcePath' key with value '/' to health_check_config

Hint

The ResourcePath tells Route 53 which page to check on your server.

3

Set the failure threshold

Add a key 'FailureThreshold' with the integer value 3 to the health_check_config dictionary.

AWS

health_check_config = {
    'IPAddress': '192.0.2.44',
    'Port': 80,
    'Type': 'HTTP',
    'ResourcePath': '/'
}
# Add 'FailureThreshold' key with value 3 to health_check_config

Hint

The FailureThreshold sets how many times the check can fail before marking the server unhealthy.

4

Create the Route 53 health check resource

Create a dictionary called route53_health_check with the key 'HealthCheckConfig' set to the health_check_config dictionary.

AWS

health_check_config = {
    'IPAddress': '192.0.2.44',
    'Port': 80,
    'Type': 'HTTP',
    'ResourcePath': '/',
    'FailureThreshold': 3
}
# Create route53_health_check dictionary with HealthCheckConfig key

Hint

This dictionary represents the full Route 53 health check resource using your configuration.

Practice

1. What is the main purpose of a health check in AWS Route 53?

easy

A. To monitor if a website or server is working properly

B. To increase the storage capacity of a server

C. To speed up the DNS resolution process

D. To encrypt data between users and servers

Solution

1. Step 1: Understand the role of health checks

   Health checks in Route 53 monitor the status of your website or server to see if it is working correctly.

2. Step 2: Identify the main purpose

   The main goal is to ensure traffic is sent only to healthy endpoints by checking their health status.

3. Final Answer:

   To monitor if a website or server is working properly -> Option A

4. Quick Check:

   Health check purpose = Monitor server health [OK]

Hint: Health checks watch if your site/server is up [OK]

Common Mistakes:

• Confusing health checks with encryption
• Thinking health checks speed up DNS
• Assuming health checks add storage

2. Which of the following is the correct way to configure a Route 53 health check to check an HTTP endpoint on port 80?

easy

A. Set Protocol to FTP and Port to 21

B. Set Protocol to HTTPS and Port to 443

C. Set Protocol to TCP and Port to 22

D. Set Protocol to HTTP and Port to 80

Solution

1. Step 1: Identify the protocol and port for HTTP

   HTTP uses protocol HTTP and port 80 by default.

2. Step 2: Match the correct configuration

   Setting Protocol to HTTP and Port to 80 correctly configures the health check for an HTTP endpoint.

3. Final Answer:

   Set Protocol to HTTP and Port to 80 -> Option D

4. Quick Check:

   HTTP = Protocol HTTP + Port 80 [OK]

Hint: HTTP always uses port 80 [OK]

Common Mistakes:

• Using HTTPS protocol for HTTP checks
• Choosing wrong ports like 22 or 21
• Confusing TCP with HTTP protocol

3. Given a Route 53 health check configured to check an HTTP endpoint every 30 seconds with a failure threshold of 3, how long will it take before Route 53 marks the endpoint as unhealthy after it stops responding?

medium

A. 30 seconds

B. 60 seconds

C. 90 seconds

D. 120 seconds

Solution

1. Step 1: Understand failure threshold and interval

   The health check runs every 30 seconds and requires 3 consecutive failures to mark unhealthy.

2. Step 2: Calculate total time to mark unhealthy

   3 failures x 30 seconds each = 90 seconds before marking unhealthy.

3. Final Answer:

   90 seconds -> Option C

4. Quick Check:

   3 failures x 30s = 90s [OK]

Hint: Multiply interval by failure threshold [OK]

Common Mistakes:

• Using interval time only without threshold
• Adding instead of multiplying
• Confusing seconds with minutes

4. You created a Route 53 health check for an HTTPS endpoint on port 443, but Route 53 always marks it unhealthy even though the site is up. What is the most likely cause?

medium

A. The health check is set to HTTP instead of HTTPS

B. The failure threshold is set too high

C. The endpoint is using port 80 instead of 443

D. The health check is configured with TCP protocol

Solution

1. Step 1: Check protocol mismatch

   If the health check is set to HTTP but the endpoint requires HTTPS, the check will fail.

2. Step 2: Confirm correct protocol and port

   HTTPS requires protocol HTTPS and port 443; using HTTP protocol causes failure.

3. Final Answer:

   The health check is set to HTTP instead of HTTPS -> Option A

4. Quick Check:

   Protocol mismatch causes failure [OK]

Hint: Match protocol exactly with endpoint [OK]

Common Mistakes:

• Ignoring protocol and port mismatch
• Assuming failure threshold causes failure
• Confusing TCP with HTTPS protocol

5. You want Route 53 to route traffic only to healthy web servers in multiple regions. You have health checks set up for each server. Which routing policy should you use to ensure traffic goes only to healthy servers and balances load across them?

hard

A. Simple routing policy

B. Weighted routing policy with health checks enabled

C. Latency routing policy without health checks

D. Failover routing policy

Solution

1. Step 1: Understand routing policies

   Simple routing sends traffic to one resource; failover sends to primary then backup; weighted distributes traffic by weights; latency routes to lowest latency.

2. Step 2: Choose policy that balances load and respects health

   Weighted routing with health checks enabled sends traffic only to healthy servers and balances load based on weights.

3. Final Answer:

   Weighted routing policy with health checks enabled -> Option B

4. Quick Check:

   Weighted + health checks = balanced healthy routing [OK]

Hint: Use weighted routing with health checks for balanced healthy traffic [OK]

Common Mistakes:

• Using simple routing which ignores health checks
• Failover only switches on failure, no load balance
• Latency routing without health checks risks unhealthy targets