Which logging solution will support these requirements?
Enable Amazon CloudWatch Logs to log the EKS components. Create a CloudWatch subscription filter for each component with Lambda as the subscription feed destination.
Enable Amazon CloudWatch Logs to log the EKS components. Create CloudWatch Logs Insights queries linked to Amazon EventBridge events that invoke Lambda.
Enable Amazon S3 logging for the EKS components. Configure an Amazon CloudWatch subscription filter for each component with Lambda as the subscription feed destination.
Enable Amazon S3 logging for the EKS components. Configure S3 PUT Object event notifications with AWS Lambda as the destination.
Explanations:
CloudWatch Logs can capture EKS logs, and using CloudWatch Logs subscription filters with Lambda allows for real-time log processing and sending notifications to the appropriate SNS topics.
While CloudWatch Logs Insights can analyze logs, using EventBridge to invoke Lambda is not a direct method to filter and trigger notifications based on EKS component logs.
Amazon S3 is not typically used for logging EKS components. CloudWatch Logs are a more appropriate option for EKS.
S3 logging is not suitable for EKS component logs. CloudWatch Logs should be used instead for capturing EKS-related log data.
I calculate that the answer is:
Enable Amazon CloudWatch Logs to log the EKS components. Create a CloudWatch subscription filter for each component with Lambda as the subscription feed destination.
I rate that the answer is:
Enable Amazon CloudWatch Logs to log the EKS components. Create a CloudWatch subscription filter for each component with Lambda as the subscription feed destination.