Troubleshooting ELB Access Logs: No Data Recorded in S3
Question
You are a Devops Engineer for your company.
You are in charge of an application that uses EC2, ELB and Autoscaling.
You have been requested to get the ELB access logs.
When you try to access the logs , you can see that nothing has been recorded in S3
Why is this the case?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - B.
The AWS Documentation mentions.
Access logging is an optional feature of Elastic Load Balancing that is disabled by default.
After you enable access logging for your load balancer, Elastic 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 ELB access logs please see the below link:
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/access-log-collection.htmlELB access logs capture detailed information about every request made to the load balancer. The logs contain information such as the client's IP address, the request time, the response time, and more. The logs are useful for debugging, monitoring, and analyzing traffic to your application.
In this scenario, the DevOps Engineer has been requested to access the ELB access logs, but when trying to access the logs, they realize that nothing has been recorded in S3. There could be a few reasons why this is the case:
A. You don't have the necessary access to the logs generated by ELB.
It is possible that the DevOps Engineer does not have the necessary permissions to access the ELB access logs. The permissions required to access ELB logs are different from the permissions required to access other AWS services. To access the ELB logs, the user needs to have permissions to read from the S3 bucket where the logs are stored, and permissions to access the logs in the ELB console.
B. By default, ELB access logs are disabled.
ELB access logs are not enabled by default. In order for the logs to be recorded, the user needs to enable access logging and specify an S3 bucket where the logs will be stored. If access logging has not been enabled for the ELB, then no logs will be recorded.
C. The Autoscaling service is not sending the required logs to ELB.
Autoscaling is a service that automatically adjusts the number of EC2 instances running based on the traffic to the application. Autoscaling can be configured to send logs to various AWS services, including ELB. If the Autoscaling service is not configured to send logs to ELB, then no logs will be recorded.
D. The EC2 instances are not sending the required logs to ELB.
EC2 instances are the virtual machines that run the application. ELB can be configured to record logs from the instances that it is load balancing. If the instances are not configured to send logs to ELB, then no logs will be recorded.
In conclusion, to determine why no logs are being recorded in S3, the DevOps Engineer should check if the ELB access logging has been enabled, if they have the necessary permissions to access the logs, if Autoscaling is configured to send logs to ELB, and if the EC2 instances are configured to send logs to ELB.
