What should a SysOps administrator do to resolve this issue?

By:
In: SOA-C01
Tagged:
With: 1 Comment
A company’s security policy states that connecting to Amazon EC2 instances is not permitted through SSH and RDP.If access is required, authorized staff can connect to instances by using AWS Systems Manager Session Manager.Users report that they are unable to connect to one specific Amazon EC2 instance that is running Ubuntu and has AWS Systems Manager Agent (SSM Agent) pre-installed.These users are able to use Session Manager to connect to other instances in the same subnet, and they are in an IAM group that has SessionManager permission for all instances.

What should a SysOps administrator do to resolve this issue?

Add an inbound rule for port 22 in the security group associated with the Ubuntu instance.

Assign the AmazonSSMManagedInstanceCore managed policy to the EC2 instance profile for the Ubuntu instance.

Configure the SSM Agent to log in with a user name of ג€ubuntuג€.

Generate a new key pair, configure Session Manager to use this new key pair, and provide the private key to the users.

Explanations:

Adding an inbound rule for port 22 would allow SSH access, which contradicts the company’s security policy that forbids SSH access.

The AmazonSSMManagedInstanceCore policy grants the necessary permissions to allow the EC2 instance to communicate with Systems Manager. The instance profile might be missing this policy.

The SSM Agent does not require a specific username to be configured for Session Manager to work. This option is unrelated to the issue.

The issue does not involve SSH key pairs, as the company policy forbids SSH and RDP access. Session Manager should be used, and a new key pair is unnecessary.

2025-09-29

1 Comment

  1. Alice
    Author

    I think the answer is:
    Assign the AmazonSSMManagedInstanceCore managed policy to the EC2 instance profile for the Ubuntu instance.

Leave a Reply

Your email address will not be published. Required fields are marked *

two × one =