A solutions architect imported a VM from an on-premises environment using VM Import/Export and created an AMI. An Amazon EC2 instance launched from that AMI runs in a public subnet within a VPC and has a public IP address. The EC2 instance does not appear as a managed instance in the AWS Systems Manager console. Which combination of troubleshooting steps should the solutions architect take? (Choose two.)

For an EC2 instance to be managed by AWS Systems Manager, two critical components are required. First, the AWS Systems Manager Agent (SSM Agent) must be installed and running on the instance. This agent is responsible for processing Systems Manager requests and sending information back to the service. Second, the instance needs an IAM role with the necessary permissions (e.g., AmazonSSMManagedInstanceCore) attached to it. This role grants the SSM Agent the authorization to communicate with the Systems Manager service. Without either of these, the instance cannot appear as a managed instance. A VPC endpoint for Systems Manager is not strictly required if the instance has internet connectivity to reach the Systems Manager public endpoints. The AWS Application Discovery Agent is used for migration planning, not for Systems Manager management. Service-linked roles for Systems Manager are typically created automatically and are not usually a troubleshooting step for individual instance management.