A company's security policy prohibits connecting to Amazon EC2 instances through SSH and RDP. Instead, staff must use AWS Systems Manager Session Manager. Users report they cannot connect to one…

Question

Options

• AAdd an inbound rule for port 22 in the security group associated with the Ubuntu instance.
• BAssign the AmazonSSMManagedInstanceCore managed policy to the EC2 instance profile for
• CConfigure the SSM Agent to log in with a user name of "ubuntu".
• DGenerate a new key pair, configure Session Manager to use this new key pair, and provide the

• A
  3% (1)
• B
  80% (24)
• C
  13% (4)
• D
  3% (1)

Explanation

According to AWS Cloud Operations and Systems Manager documentation, Session Manager requires that each managed instance be associated with an IAM instance profile that grants Systems Manager core permissions. The required permissions are provided by the AmazonSSMManagedInstanceCore AWS-managed policy. If this policy is missing or misconfigured, the Systems Manager Agent (SSM Agent) cannot communicate with the Systems Manager service, causing connection failures even if the agent is installed and running. This explains why other instances work--those instances likely have the correct IAM role attached. Enabling port 22 (Option A) violates the company's security policy, while configuring user names (Option C) and key pairs (Option D) are irrelevant because Session Manager operates over secure API channels, not SSH keys. Therefore, the correct resolution is to attach or update the instance profile with the AmazonSSMManagedInstanceCore policy, restoring Session Manager connectivity.

No community discussion yet for this question.