AWS Certified SysOps Administrator – Associate — Question 79

A SysOps administrator uses AWS Systems Manager Session Manager to connect to instances. After the SysOps administrator launches a new Amazon EC2 instance, the EC2 instance does not appear in the Session Manager list of systems that are available for connection. The SysOps administrator verifies that Systems Manager Agent is installed, updated, and running on the EC2 instance.

What is the reason for this issue?

Answer options

• A. The SysOps administrator does not have access to the key pair that is required for connection.
• B. The SysOps administrator has not attached a security group to the EC2 instance to allow SSH on port 22.
• C. The EC2 instance does not have an attached IAM role that allows Session Manager to connect to the EC2 instance.
• D. The EC2 instance ID has not been entered into the Session Manager configuration.

Correct answer: C

Explanation

The correct answer is C because an IAM role is essential for Session Manager to have the necessary permissions to connect to the EC2 instance. Without this role, the instance cannot be recognized by Session Manager, even if the agent is running. Options A and B are incorrect as they relate to SSH access, which is not relevant for Session Manager connections, while option D is misleading since the instance ID configuration is not a requirement for Session Manager functionality.