Cloud Defense Logo

Products

Solutions

Company

Rule: Auto Scaling Groups with a Load Balancer Should Use Health Checks

This rule ensures that Auto Scaling groups with a load balancer implement health checks for better performance and reliability.

RuleAuto Scaling groups with a load balancer should use health checks
FrameworkNIST 800-53 Revision 5
Severity
Critical

Rule Description:

Auto Scaling groups with a load balancer should use health checks to ensure the availability and proper functioning of instances. This rule is aligned with NIST 800-53 Revision 5, which emphasizes the importance of monitoring and maintaining the health of systems in order to minimize disruptions and ensure continuous service delivery.

Troubleshooting Steps:

If instances in your Auto Scaling group are not passing health checks, follow these troubleshooting steps:

  1. 1.

    Verify Load Balancer Configuration:

    • Confirm that the load balancer associated with the Auto Scaling group is correctly configured.
    • Ensure that the listener rules and target groups are properly set up.
    • Check that the load balancer is correctly configured to perform health checks on the instances.
  2. 2.

    Check Instance Health:

    • Review the health status of individual instances in the Auto Scaling group.
    • Identify any specific instances that are failing health checks.
    • Validate that the instances have the necessary resources and are functioning properly.
  3. 3.

    Analyze Health Check Settings:

    • Evaluate the health check settings configured for the Auto Scaling group and associated load balancer.
    • Ensure that the health check settings are appropriate for your specific application and workload.
    • Adjust the health check frequency and timeout values if necessary.
  4. 4.

    Review Security Group Settings:

    • Verify that the security group associated with the instances allows traffic from the load balancer for health checks.
    • Ensure that the security group rules are properly configured to allow the necessary health check traffic.
  5. 5.

    Check Application/Server Logs:

    • Inspect the application or server logs to identify any errors or issues that may be affecting instance health.
    • Use log analysis tools to identify patterns or anomalies that could be impacting instance health.
  6. 6.

    Monitor Network Traffic:

    • Monitor network traffic to identify any potential network issues that may be causing health check failures.
    • Analyze network data to identify any bottlenecks, errors, or abnormalities.

Necessary Codes:

Ensure you have the necessary codes in place to configure health checks for your Auto Scaling group with load balancer. Here is an example in AWS CLI:

aws autoscaling update-auto-scaling-group --auto-scaling-group-name <auto-scaling-group-name> --health-check-type ELB --health-check-grace-period <health-check-grace-period>

Replace

<auto-scaling-group-name>
with the name of your Auto Scaling group and
<health-check-grace-period>
with the desired health check grace period in seconds.

Remediation Steps:

To configure health checks for your Auto Scaling group with a load balancer, follow these step-by-step instructions:

  1. 1.

    Identify the Auto Scaling group:

    • Determine the name of the Auto Scaling group that needs health checks configured.
  2. 2.

    Open the AWS Management Console:

    • Go to the Amazon EC2 page on the AWS Management Console.
  3. 3.

    Navigate to the Auto Scaling group:

    • Select "Auto Scaling Groups" from the sidebar menu.
    • Locate and click on the desired Auto Scaling group.
  4. 4.

    Edit Auto Scaling group settings:

    • Click on the "Edit" button to modify the Auto Scaling group configuration.
  5. 5.

    Configure health checks:

    • Scroll down to the "Health check type and grace period" section.
    • Select "ELB" as the health check type.
    • Specify the desired health check grace period in seconds.
  6. 6.

    Save the changes:

    • Click on the "Save" button to apply the health check configuration.
  7. 7.

    Verify health check configuration:

    • Monitor the Auto Scaling group's health check status to ensure instances are passing the checks.
    • Review associated logs, metrics, and alerts to identify any issues and ensure proper health check functionality.

By following these steps and implementing health checks for your Auto Scaling group with a load balancer, you can adhere to the NIST 800-53 Revision 5 requirement and ensure the availability and reliability of your infrastructure.

Is your System Free of Underlying Vulnerabilities?
Find Out Now