A company runs applications on Amazon EC2 instances that are in an Amazon EC2 Auto Scaling group. The EC2 instances are behind an Application Load Balancer (ALB). Users recently began to experience er

Question

Options

• AConfigure the Auto Scaling group to use ELB health checks. Enable AWS Config. Create an AWS
• BConfigure the Auto Scaling group to use EC2 health checks. Enable AWS Config. Create an AWS
• CConfigure the Auto Scaling group to use EC2 health checks. Create an Amazon CloudWatch
• DConfigure the Auto Scaling group to use ELB health checks. Create an Amazon CloudWatch

• A
  76% (22)
• B
  14% (4)
• C
  3% (1)
• D
  7% (2)

Explanation

The issue occurs because the Auto Scaling group is using EC2 instance status checks, which only check if the instance is running but do not validate the application health. The correct approach is to use ELB health checks, which consider both the instance and application health before routing traffic. 1. Use ELB health checks for the Auto Scaling group ELB health checks validate that the application is responding correctly before routing traffic to If an instance starts returning errors, the ELB will mark it as unhealthy and stop sending traffic 2. Ensure compliance with AWS Config AWS Config can enforce policies to ensure that all Auto Scaling groups use ELB health checks instead of EC2 health checks. A custom AWS Config rule can notify the team if any new Auto Scaling group does not adhere to this requirement. 3. Set up SNS notifications If a change in the traffic routing configuration occurs (e.g., someone changes the health check type), AWS Config will detect it and trigger a notification to the support team via SNS.

No community discussion yet for this question.