A company runs a file-reading application that stores files in a database on Amazon EC2 instances. Regulations require daily deletion of files from the EC2 instances at a specific time, and database records older than 60 days must be removed. Database deletions must occur after the file deletions. The company already has scripts for both deletion tasks and needs email alerts for any deletion-script failures. Which solution meets these requirements with the least development effort?

The correct solution leverages AWS Systems Manager State Manager to schedule an Automation document daily. This document uses Run Command to execute the existing deletion scripts on the EC2 instances sequentially, ensuring file deletions precede database deletions. An Amazon EventBridge rule is then configured to monitor for AutomationExecutionFailed events from Systems Manager and publish these to an Amazon SNS topic, which sends email notifications for any script failures. This approach minimizes development effort by reusing existing scripts and using native AWS services for orchestration, scheduling, and notification. The incorrect options either introduce unnecessary complexity (e.g., conditional steps within Automation for email, or using SES directly within Automation, which is less integrated for failure notifications) or require more development effort (e.g., rewriting scripts to run within a Lambda function, which might exceed Lambda's execution limits or require significant refactoring for EC2 interaction).