Topic 1 Question 346
A company's security policy states that connecting to Amazon EC2 instances is not permitted through SSH and ROP. 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 Session Manager 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.
ユーザの投票
コメント(2)
- 正解だと思う選択肢: B
By assigning the AmazonSSMManagedInstanceCore managed policy to the EC2 instance profile associated with the Ubuntu instance, you grant the necessary permissions for the instance to communicate with AWS Systems Manager. This policy includes the required permissions for Session Manager to establish connections to EC2 instances.
👍 3Pete9872023/06/30 B
To resolve the issue of users being unable to connect to the specific EC2 instance using Session Manager, the SysOps administrator should assign the AmazonSSMManagedInstanceCore managed policy to the EC2 instance profile for the Ubuntu instance. This managed policy provides the necessary permissions for the SSM Agent to communicate with the Systems Manager service, which is required for Session Manager to work. Once the policy is attached to the instance profile, users should be able to connect to the instance using Session Manager.
👍 2[Removed]2023/07/09
シャッフルモード