Here and welcome back now into this, we will be discussing about one of the features of systems management,
which is this session's manager now at a high level overview sessions manager allows customers to connect
to the instances through an interactive click browser beashel or through the database ceiling.
So this can be better understood with this diagram.
So let's say you have a set of two instances running now instead of using a SFH plan like Putty or even
if this is Glen from my Linux, what you can do is from your Web browser itself, you can connect through
the sessions manager to the set of two instances.
Now, let me quickly, given of you both, which will be discussing things in wanted now from the systems
manager.
And so let's go back down towards the fleet manager, make sure that your agent is within the on line
state.
So, yes, our agent is in the online stage.
Let's go back let's go to session manager.
Let's go ahead and start our session.
I'll select the instance, which is easy decision and let's do a start session.
And now you see we're connected.
So if I don't come on like Ellis, if I don't come on like top or maybe let's say you do a password,
we will quickly through the list of users and its associated data and so on.
So basically, this is like a skill that you can go in and run commands.
So that is what the sessions manager allows you to do.
Now, one of the questions that comes is what is so special about sessions manager?
Primarily because if you discuss about what is he doing since you can also go ahead and get the connection
through, easy to connect.
So if very quickly, select instance, let's do a connect over here.
You have two instant scanning, if you will, quickly do a connected, you see, and connected.
So again, you file rank commands like let's stop and we so this thing seems to be working perfectly.
So the question that comes is what is the difference between both of them and when should you use systems
manager instead of other traditional methods now at a high level?
Or when you discuss about the difference between easy to connect and sessions manager, there are few
primary difference that we need to know first.
One is that for the easy to connect, IBM role is not required.
However, for the sessions manager, IBM rule is required, and if a user wants to connect to the EU
via the station's manager, that user will also need appropriate policy in place.
Second is that for the security group perspective, easy to connect requires the security group with
the board 22 to be open.
This is one of the very important differences, Harveyville, for the sessions manager.
You do not really need it.
Even if the security group does not have bought 20 22 open, it does not really matter for the station's
manager.
Third one is the public eye.
Before the easy to connect the public IP must be there for the easy to instance.
However, for the station's manager, even if they see two instances within the private subnet and does
not have a public IP, you will still be able to connect to it.
So let's go ahead and try it on.
Now, going back to the instances audio, the reason why we were able to connect to it, we are the
easy to connect voice because the instance had a public IP and along with that you also had a message
board of 22 that was open forum.
So let's do one thing.
Let's go ahead and remove this message board and let's see what happens here.
So let's editor in module and let me remove zero zero zero zero and insert that lets us quickly do one
two seven zero zero.
That one followed by 32 and it will do a several year.
So now if you'll go ahead and try connecting the ADC to instance, connect and immediately you'll see
it is trading problem connecting to your easy to insert.
And so you need to have about 22 open.
And since we had a zero zero zero zero in our board, 22, the easy two instance connect used to work
perfectly with Harveyville for the station manager.
Even after you have removed that.
Or let me also show you one thing.
Let's go and remove the entire support so that the confusion does not delay.
So I'll go ahead and edit the inbound.
Let delete this completely.
Alright, let's connect to the instance now.
Let's do it.
We either instance connect and as expected, you are getting an editorial.
Similarly, if you try to do it via the station's manager.
Now you see we are connected perfectly well.
So this is the benefit of sessions manager.
Not only you have to not worry about the security group continue to be open.
You also do not really need a public IP.
You know, before you go ahead and explore various other features of station's manager, let's look
into some of the notable benefits here.
First one is that you can have a centralized access.
Control by making use of IEM policies, second is no inbound port needs to be open.
This is something that we have seen important benefit specifically from audit perspective is that it
supports logging and auditing sessions history.
So this is something that will make the auditors really happy.
If you have this, will we just look into this in a moment here?
Then you also have a one click access to instance from the console as well as the SEAL.
And the last one is you do not really need VPN connection.
So let's go ahead and explore this third benefit of logging and auditing this person's activity now
from the sessions manager.
We had already run some commands like a stop and others.
So let's say you have completed running the comments.
You can go ahead and terminate the session.
So now if you look into the station history, you'll basically get the details on who is the user.
So you have a user demo labs and this user connected to the instance.
I did this on this specific start date on this specific ended and the status is now terminated.
So essentially you'll get to know one who exactly is connecting two, which is two instances within
your environment.
So this is one great benefit.
Second important benefit is related to the logging perspective.
So currently the logging is not inhibit.
However, we can also go ahead and enable the logging.
So now what will happen is the commands that the user type, those commands will also be logged.
So let's try it.
So before we try this, let's go ahead and open up that cloud watch console.
So Amazon has been regularly updating the cloud once again.
So let's try out the new interface.
So within cloud, which console?
We are more interested in logs.
So we'll go to the log groups here and let's go ahead and create a log group, let's call it.
This system commands will go ahead and created Hoylake now from the systems manager under the preferences.
Let's go ahead and edit it up.
Let's go a bit down.
So within the cloud watch logging will go ahead and enable it.
And encryption lets us select the encryption within the cloud watchdog group.
Let's select the group with this system command.
So this is where all the commands would be stored, will go ahead and will do as if both so are cloud
waterlogging is now enabled.
Let's go back to the sessions.
Let's start the session.
And let's run some comments, so I'll say it, OK, let's do it, let's have fun on en route, let's
do a get into password.
Also, there are certain commands that we have executed.
And after doing that, Will Terminator's perfect.
So in this nation's history now you will see the detail.
So this is the section that we just got terminated.
And within the output location, you have cloud watch logs.
So if I quickly open up the cloud autologous audio now immediately within the cloud org console, you
basically get editorial.
Now, the reason why this error is coming is because the system is in.
That is part of this easy to instance, does not have permission to store the logs to cloud.
So it is very important specifically if you want to store the logs to cloud, what is that?
The IBM rule of the easy to instance should have its associated permission.
So let's do one thing.
Let's go back to the easy to instant's instance here, and we'll go ahead and modify the IBM rule so
that the cloud org logs related access is given.
So little attach and more policy.
Now, just for simplicity, will give a cloud watch logs, full access, great.
So when this specific permission is added, let's go ahead and start the session again.
Let's create a new file called Not DHT.
Let's also run a command of top and we'll do a controlled now within cloud, which let's refresh this
page.
And immediately now you'll see a new log stream is created and you have a Dewson like even so, this
is much, much better.
So one of the first command that we had is Patch 36.
The and within the output it was cannot touch.
But this is very similar to what we had seen.
Now, similarly, we had also run a top command and within the top command, you see, we had got various
output related to the processes that are running and various others.
That's great.
So I hope with this you understood the basics of the sessions manager, the advantages that decision
manager provides, not only in terms of connecting to the private key to instance, but also in terms
of the logging in auditing perspective.
This is very important and this is one of the reasons why a lot of organizations have actively started
to use sessions manager.
So with this will conclude today's video.