Which solution will meet these requirements?
Enable S3 server access logging for audit logs. Set up an Amazon Simple Notification Service (Amazon SNS) notification for the S3 bucket. Select DeleteObject for the event type for the alert system.
Enable S3 server access logging for audit logs. Launch an Amazon EC2 instance for the alert system. Run a cron job on the EC2 instance to download the access logs each day and to scan for a DeleteObject event.
Use Amazon CloudWatch Logs for audit logs. Use Amazon CloudWatch alarms with an Amazon Simple Notification Service (Amazon SNS) notification for the alert system.
Use Amazon CloudWatch Logs for audit logs. Launch an Amazon EC2 instance for the alert system. Run a cron job on the EC2 instance each day to compare the list of the items with the list from the previous day. Configure the cron job to send a notification if an item is missing.
Explanations:
Enabling S3 server access logging will log all access attempts. Using Amazon SNS for notifications will provide real-time alerts for DeleteObject events, which meets the requirement for immediate notification on delete actions.
While S3 server access logging will log access attempts, using an EC2 instance with a cron job to scan logs daily is not efficient for immediate notifications. The cron job approach would delay the detection of delete events.
CloudWatch Logs are used for monitoring, but using it for audit logs of S3 access is not ideal. While CloudWatch alarms and SNS notifications can be configured, the solution doesn’t log S3-specific actions like DeleteObject directly, so it doesn’t fully meet the requirement.
Using an EC2 instance with a cron job to compare the list of items daily will not provide immediate notifications and could miss real-time events. This method is inefficient compared to using native S3 logging and SNS for alerts.