A company runs infrastructure across Regions, AZs, on-premises servers, EC2, and AWS IoT Greengrass devices. The DevOps team will use AWS Systems Manager to automate patches and configuration across EC2, IoT devices, and on-prem servers. Systems Manager is available in the needed Regions. Which steps are required to implement automated patching and configuration across all these resources? (Choose three.)

Patch Manager, a component of Systems Manager, is designed for automated patching and uses Maintenance Windows to schedule these operations across various resource types, including EC2 instances, on-premises servers, and IoT Greengrass devices. For Systems Manager to manage these resources, they need appropriate permissions. EC2 instances require an IAM instance profile with SSM permissions. On-premises servers and IoT Greengrass devices need IAM service roles. To register on-premises servers with Systems Manager, a managed-instance activation is required, providing an Activation Code/ID. For IoT Greengrass devices, the Greengrass token exchange role needs to be updated to allow SSM Agent deployment. Incorrect options: Session Manager is for interactive access, not automated patching. While Run Command can execute patches, Patch Manager and Maintenance Windows provide a more comprehensive, scheduled, and policy-driven patching solution. EventBridge monitors events; it doesn't directly initiate patching across all resources in this context. Patch Manager handles the scheduling and execution.