What is the reason for this?

You have just recently deployed an application on EC2 instances behind an ELB. After a couple of weeks, customers are complaining on receiving errors from the application. You want to diagnose the errors and are trying to get errors from the ELB access logs. But the ELB access logs are empty.

What is the reason for this?
A . You do not have the appropriate permissions to access the logs
B. You do not have your CloudWatch metrics correctly configured
C. ELB Access logs are only available for a maximum of one week.
D. Access logging is an optional feature of Elastic Load Balancing that is disabled by default

View Answer

Answer: D

Explanation:

Clastic Load Balancing provides access logs that capture detailed information about requests sent to your load balancer. Cach log contains information such as the time the request was received, the client’s IP address, latencies, request paths, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot issues.

Access logging is an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logging for your load balancer. Clastic Load

Balancing captures the logs and stores them in the Amazon S3 bucket that you specify.

You can disable access logging at any time.

For more information on CLB access logs, please refer to the below document link: from AWS

✑ http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/access-log-collection. html