Health checks with Route 53 in AWS - Time & Space Complexity

Time Complexity: Health checks with Route 53

O(n)

Understanding Time Complexity

When using Route 53 health checks, it is important to understand how the number of health checks affects the system's work.

We want to know how the time to perform health checks grows as we add more checks.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Create multiple Route 53 health checks
for (int i = 0; i < n; i++) {
  aws route53 create-health-check --caller-reference "ref-"$i \
    --health-check-config IPAddress=192.0.2.1,Port=80,Type=HTTP,ResourcePath="/"
}
    

This sequence creates n health checks, each monitoring a specific endpoint.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: The API call to create a health check.
• How many times: This call happens once for each health check, so n times.

How Execution Grows With Input

As the number of health checks (n) increases, the total number of API calls grows directly with n.

Input Size (n)	Approx. Api Calls/Operations
10	10
100	100
1000	1000

Pattern observation: The work grows in a straight line with the number of health checks added.

Final Time Complexity

Time Complexity: O(n)

This means the time to create health checks grows directly in proportion to how many you create.

Common Mistake

[X] Wrong: "Creating multiple health checks happens all at once, so time stays the same no matter how many."

[OK] Correct: Each health check requires a separate API call, so more checks mean more calls and more time.

Interview Connect

Understanding how operations grow with input size helps you design scalable systems and explain your reasoning clearly in interviews.

Self-Check

"What if we batch health check creations using a bulk API? How would the time complexity change?"

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