Which of the following services can help you get a history of Classic Load Balancer API calls?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A.
This is given in the AWS documentation.
For more information on the ELB FAQ's please see the below link:
https://aws.amazon.com/elasticloadbalancing/faqs/The correct answer is A. CloudTrail.
CloudTrail is a service that provides a record of events and API calls that have been made within your AWS account. This includes events related to Classic Load Balancer, as well as many other AWS services.
By default, CloudTrail logs all management events, data events, and control plane events related to Classic Load Balancer. These events are logged in JSON format and can be stored in an S3 bucket or sent to CloudWatch Logs.
Using CloudTrail, you can audit Classic Load Balancer API calls, including details such as the time of the API call, the user who made the call, and the request parameters. This can help you with compliance, governance, and security.
Option B, CloudWatch, is a monitoring service that can be used to collect and track metrics, collect and monitor log files, and set alarms. While it can be used to monitor Classic Load Balancer, it does not provide a history of API calls.
Option C, CloudWatch Logs, is a service for storing, monitoring, and accessing log files. While you can send CloudTrail logs to CloudWatch Logs, it is not the best option for viewing a history of Classic Load Balancer API calls.
Option D, AWS Config, is a service that provides a detailed inventory of your AWS resources, including configurations and relationships between resources. While it can be used to monitor the configuration of Classic Load Balancer, it does not provide a history of API calls.