This rule ensures that ELB application and classic load balancer logging is enabled.
Rule | ELB application and classic load balancer logging should be enabled |
Framework | CISA-cyber-essentials |
Severity | ✔ High |
Rule Description
Enabling logging for ELB (Elastic Load Balancer) application and classic load balancer is recommended for CISA (Cybersecurity and Infrastructure Security Agency) Cyber Essentials compliance. Logging provides valuable insights into the health and performance of the load balancer and can help in detecting and troubleshooting any issues that may arise.
Troubleshooting Steps
If logging is not already enabled for ELB application and classic load balancer, follow the steps below to enable it:
Step 1: Select the Load Balancer
Step 2: Choose the Load Balancer
Step 3: Enable Logging
Step 4: Save the Configuration
CLI Command
Alternatively, logging for ELB application and classic load balancer can also be enabled using AWS CLI. The following command can be used:
aws elb modify-load-balancer-attributes --load-balancer-name <load_balancer_name> --access-log-enabled --access-log-destination-bucket <S3_bucket_name> --access-log-destination-prefix <prefix>
Ensure to replace
<load_balancer_name>
, <S3_bucket_name>
, and <prefix>
with appropriate values specific to your environment.Remediation Steps
To enable logging for ELB application and classic load balancer, follow the step-by-step guide mentioned above in the "Troubleshooting Steps" section. If you prefer using CLI, execute the provided AWS CLI command after replacing the placeholder values.
Enabling logging for ELB application and classic load balancer will ensure that important data related to traffic, errors, and health of the load balancer is captured and can be used for analysis, auditing, and troubleshooting purposes.