How do you fix your usage dashboard?
Enable Cloud Front to deliver access logs to S3 and use them as input of the Elastic Map Reduce job.
Turn on Cloud Trail and use trail log tiles on S3 as input of the Elastic Map Reduce job
Change your log collection process to use Cloud Watch ELB metrics as input of the Elastic Map Reduce job
Use Elastic Beanstalk “Rebuild Environment” option to update log delivery to the Elastic Map Reduce job.
Use Elastic Beanstalk “Restart App server(s)” option to update log delivery to the Elastic Map Reduce job.
Explanations:
Enabling CloudFront to deliver access logs to S3 captures the traffic processed by CloudFront. This will ensure the usage dashboard reflects accurate data, as it will include requests routed through CloudFront instead of only those captured from the Elastic Beanstalk logs.
CloudTrail logs track API calls made within your AWS account but do not provide detailed information about web traffic or user access patterns to your website. Therefore, using CloudTrail logs for the usage dashboard would not yield relevant insights into website traffic.
While CloudWatch ELB metrics provide some insight into traffic, they do not capture detailed log data necessary for understanding specific user interactions and usage patterns, especially after integrating CloudFront. Hence, this option wouldn’t fully address the accuracy of the usage dashboard.
Using the “Rebuild Environment” option for Elastic Beanstalk does not directly impact log delivery settings or processes for the Elastic Map Reduce job. It primarily rebuilds the environment without changing how logs are collected and analyzed.
Similar to option D, the “Restart App server(s)” option only restarts the application servers and does not affect the log collection process or delivery to the Elastic Map Reduce job. This action will not rectify the dashboard’s accuracy.
As far as I can tell, the answer is:
Enable Cloud Front to deliver access logs to S3 and use them as input of the Elastic Map Reduce job.