So now let's talk about Systems Manager
and more specifically the SSM Session Manager subservice.
So it allows you to start a secure shell
on your EC2 instance and your on-premises server,
but the particularity is that you don't need any SSH access.
You don't need any bastion host,
you don't need any SSH keys,
and therefore you do not open the port 22
on your EC2 instances,
therefore providing you with better security.
So you have your EC2 instance
and it's running the SSM agents,
and for example, the Amazon in Linux 2 AMI
do have these kind of agents running on it.
And then we go onto Session Manager
with the right IAM permissions
and we execute commands directly on the EC2 instance.
So it supports Linux, macOS, and Windows,
and any session data can be sent to S3 or Calabash logs.
So whatever commands someone types on Session Manager,
you can see an audit, which is really good.
The one thing is that the EC2 instance must have an IAM role
that is allowing it to access the Session Manager service.
So if you see access to a secure shell on EC2 instances,
for example, but without connecting through SSH
or EC2 instance connect, which also leverages SSH,
then you have to think about the SSM Session Manager.
So that's it for this lecture, I hope you liked it,
and I will see you in the next lecture.