Health checks configuration in AWS - Time & Space Complexity

Time Complexity: Health checks configuration

O(n)

Understanding Time Complexity

When setting up health checks in AWS, it's important to understand how the number of checks affects system behavior.

We want to know how the time spent on health checks grows as we add more resources to monitor.

Scenario Under Consideration

Analyze the time complexity of configuring health checks for multiple targets.

for target in targets:
    elb.configure_health_check(
        Target=target.endpoint,
        Interval=30,
        Timeout=5,
        UnhealthyThreshold=2,
        HealthyThreshold=2
    )
    

This sequence sets up health checks for each target in a load balancer.

Identify Repeating Operations

We look at what repeats as the number of targets grows.

• Primary operation: API call to configure health check per target.
• How many times: Once for each target in the list.

How Execution Grows With Input

Each new target adds one more health check configuration call.

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

Pattern observation: The number of operations grows directly with the number of targets.

Final Time Complexity

Time Complexity: O(n)

This means the time to configure health checks grows linearly as you add more targets.

Common Mistake

[X] Wrong: "Configuring health checks happens once and covers all targets automatically."

[OK] Correct: Each target needs its own health check setup, so the work grows with the number of targets.

Interview Connect

Understanding how configuration steps scale helps you design systems that stay manageable as they grow.

Self-Check

"What if health checks were configured in batches instead of individually? How would the time complexity change?"

Practice

1. What is the main purpose of a health check in AWS services like Elastic Load Balancer?

easy

A. To verify if a server or service is responding correctly

B. To increase the server's CPU capacity automatically

C. To backup data from the server regularly

D. To encrypt data sent between servers

Solution

1. Step 1: Understand the role of health checks

   Health checks monitor if a server or service is working properly by sending requests and checking responses.

2. Step 2: Identify the main goal

   The main goal is to detect unhealthy servers so they can be removed from traffic, ensuring reliability.

3. Final Answer:

   To verify if a server or service is responding correctly -> Option A

4. Quick Check:

   Health check purpose = verify server response [OK]

Hint: Health checks confirm server responsiveness, not capacity or backups [OK]

Common Mistakes:

• Confusing health checks with scaling or backup tasks
• Thinking health checks encrypt data
• Assuming health checks improve server hardware

2. Which of the following is the correct way to configure a health check path for an HTTP service in AWS Elastic Load Balancer?

easy

A. HealthCheckInterval: 60

B. HealthCheckPath: "/status"

C. HealthCheckProtocol: TCP

D. HealthCheckPort: 8080

Solution

1. Step 1: Identify the correct parameter for HTTP path

   For HTTP health checks, the path to check is set using HealthCheckPath with a URL path string.

2. Step 2: Differentiate from other parameters

   HealthCheckPort sets the port, HealthCheckProtocol sets the protocol, and HealthCheckInterval sets the time between checks, not the path.

3. Final Answer:

   HealthCheckPath: "/status" -> Option B

4. Quick Check:

   HTTP health check path = HealthCheckPath [OK]

Hint: Path is set with HealthCheckPath, not port or interval [OK]

Common Mistakes:

• Using HealthCheckPort to set the path
• Confusing protocol with path
• Setting interval instead of path

3. Given this health check configuration for a load balancer:
IntervalSeconds: 30
TimeoutSeconds: 5
HealthyThresholdCount: 3
UnhealthyThresholdCount: 2
How many consecutive failed health checks will cause the instance to be marked unhealthy?

medium

A. 30

B. 3

C. 5

D. 2

Solution

1. Step 1: Understand UnhealthyThresholdCount meaning

   This value defines how many failed health checks in a row mark the instance unhealthy.

2. Step 2: Identify the value from configuration

   UnhealthyThresholdCount is set to 2, so after 2 failed checks, the instance is unhealthy.

3. Final Answer:

   2 -> Option D

4. Quick Check:

   Failed checks to unhealthy = UnhealthyThresholdCount = 2 [OK]

Hint: UnhealthyThresholdCount = failed checks before unhealthy [OK]

Common Mistakes:

• Confusing HealthyThresholdCount with unhealthy count
• Using IntervalSeconds as count
• Assuming timeout affects count

4. You configured a health check with TimeoutSeconds set to 10 seconds, but your service responds in 3 seconds. The health check still fails. What is the most likely cause?

medium

A. HealthyThresholdCount is set too low

B. TimeoutSeconds is too high causing failure

C. The health check path is incorrect or unreachable

D. IntervalSeconds is set to 1 second

Solution

1. Step 1: Analyze TimeoutSeconds vs response time

   TimeoutSeconds is 10, service responds in 3 seconds, so timeout is not the issue.

2. Step 2: Consider other causes for failure

   If health check fails despite quick response, likely the path is wrong or the service is unreachable.

3. Final Answer:

   The health check path is incorrect or unreachable -> Option C

4. Quick Check:

   Fast response but failure = wrong path/unreachable [OK]

Hint: Fast response but failure? Check health check path [OK]

Common Mistakes:

• Assuming timeout too high causes failure
• Confusing threshold counts with timeout
• Ignoring path correctness

5. You want to configure a health check for a web service behind an AWS Application Load Balancer. The service sometimes takes up to 8 seconds to respond under load. Which configuration best ensures accurate health status without false failures?

hard

A. Set TimeoutSeconds to 10, IntervalSeconds to 30, HealthyThresholdCount to 3, UnhealthyThresholdCount to 2

B. Set TimeoutSeconds to 5, IntervalSeconds to 10, HealthyThresholdCount to 2, UnhealthyThresholdCount to 2

C. Set TimeoutSeconds to 3, IntervalSeconds to 5, HealthyThresholdCount to 5, UnhealthyThresholdCount to 5

D. Set TimeoutSeconds to 1, IntervalSeconds to 15, HealthyThresholdCount to 1, UnhealthyThresholdCount to 1

Solution

1. Step 1: Match TimeoutSeconds to max response time

   The service can take up to 8 seconds, so TimeoutSeconds should be at least 8 to avoid false failures. Set TimeoutSeconds to 10, IntervalSeconds to 30, HealthyThresholdCount to 3, UnhealthyThresholdCount to 2 sets 10 seconds, which is suitable.

2. Step 2: Choose thresholds and intervals for stability

   Longer IntervalSeconds (30) and thresholds (3 healthy, 2 unhealthy) help avoid flapping due to temporary slow responses.

3. Step 3: Evaluate other options

   Options A, C, and D have TimeoutSeconds too low or thresholds too sensitive, risking false unhealthy marks.

4. Final Answer:

   Set TimeoutSeconds to 10, IntervalSeconds to 30, HealthyThresholdCount to 3, UnhealthyThresholdCount to 2 -> Option A

5. Quick Check:

   Timeout ≥ max response + stable thresholds = Set TimeoutSeconds to 10, IntervalSeconds to 30, HealthyThresholdCount to 3, UnhealthyThresholdCount to 2 [OK]

Hint: Timeout must exceed max response time to avoid false failures [OK]

Common Mistakes:

• Setting TimeoutSeconds less than max response time
• Using too low thresholds causing flapping
• Ignoring service response variability