Which combination of actions will solve this issue?
(Choose two.)
Add Systems Manager permissions to the instance profile.
Configure the bucket used by Session Manager logs to allow write access.
Install Systems Manager Agent on the instance.
Modify the instance security group to allow inbound traffic on SSH port 22.
Reboot the instance with a new SSH key pair named ssm-user.
Explanations:
The EC2 instance must have appropriate IAM permissions to allow it to use AWS Systems Manager. Adding Systems Manager permissions to the instance profile allows the instance to interact with Systems Manager, enabling the use of Session Manager.
Configuring the bucket used by Session Manager logs to allow write access is not required to establish a Session Manager session. This action is only relevant for logging session activity, not for initiating the session itself.
The Systems Manager Agent (SSM Agent) must be installed and running on the EC2 instance for Session Manager to function. If the agent is not installed, the instance will not appear in Session Manager.
Modifying the instance security group to allow inbound traffic on SSH port 22 is not necessary for using Session Manager. Session Manager does not require SSH to be enabled since it operates over the Systems Manager API.
Rebooting the instance with a new SSH key pair is not needed for Session Manager. SSH keys are used for traditional SSH access, but Session Manager does not rely on SSH keys and works independently of them.
As far as I can tell, the answer is:
Add Systems Manager permissions to the instance profile.
I think the answer is:
Add Systems Manager permissions to the instance profile.