Aaron, and welcome back now there is video will be discussing about Adaba systems manager.
Now, the simplest definition of systems manager is that it is a group of services which allows the
customer to have a better visibility and control of the infrastructure.
So this can be better.
It's been better diagram where you have a systems manager and this systems manager has a lot of support
services.
So you have run command, you have parameters or you have stations manager, you have batch manager
along with many others.
So these four are just for the representation purposes because this signifies some of the media services
on their systems manager.
However, there are many more.
So let's look into the systems manager of at a very high level overview.
So the first thing that we need to understand is what is the use case that systems manager solves?
So the idea behind systems manager is that there will be an assistant agent which would be installed
in two instances or even on premise servers.
And the customers can provide specific task to the installed agent from the systems manager console.
So this can be better explained with this diagram where you have an instance here and this easy two
instance has this SSA agent in store.
So from the systems manager consolingly, W.S., you instruct the assistant agent to perform task.
He now assistant agent.
Once it receives the instruction, it goes ahead and implements the task here in that instance.
And whatever it is, those associated with tasks are retrieved by the same agent and are sent back to
the assistant console.
So this is the high level idea behind the systems manager.
Now, many of the popular services like it and command.
You have the station manager, you have badge manager, you have compliance, all of them.
They depend on this SSN agent.
However, there are certain services like Barometer's Stone, which has a completely different use case,
and it does not require a certain agent.
So that's the high level overview about the systems manager.
Before we conclude, let's quickly have a quick demo.
So currently I'm in my systems manager console and you will see on the left hand side, there are a
lot of features which are part of the systems manager we were discussing about.
Right.
Come on, you have station manager, you have compliance in the entry package manager and so many others.
Now, let's quickly go to the easy to console.
So for our demo published today, what I have done is I have created an easy two instance, as we were
discussing here, the primary idea associated with most of the media services systems manager is to
do work with the SSN Megyn.
So I have created this easy two instances where our system agent is installed and running.
Now, if you look into the managed instances within the instance, you see that you have one instance
cholecystectomy system and the being statuses on net, that basically means that the system is responding
perfectly.
So now let's take certain sample services and assistant manager and have a demo.
So the first interesting one that will be taking is the station manager.
So let's open this up and let's click on succession.
So this is the easy to instance.
I click on succession.
And you see, we are connected to the sequence.
And so generally what happens is that you will have to it into the actual instance before you you will
have to verify if the security group is allowing both 22 and so on.
So instead of all of that, you can directly connect to the instant from the Web browser.
So if you do, unless you see you're getting the responses similar to what you will see in a typical
Sherzad, you are running a top command audio and so on.
So this is the station's manager.
So if you quickly do a assistant status on the Amazon system aging, you will see that the agent is
currently active and running.
And primarily because of this aging, we are able to connect to the easy to instincts.
So that is associated with the station manager.
You also have a feature of Runcorn.
So at a high level or you what rank allows customers to do is they allow customers to run a specific
set of commands in instances.
So, for example, let's say there are 100 instance and you want to install a specific package in all
that hundred instance.
So the simplest way is you can go ahead and user and command and deploy that, do all the instances
here.
So let's quickly run.
Nechama, we basically run a command based on Chynn.
So we reinitiated script.
So the command that we want to run is touch them.
Damodar to the.
So this will go ahead and create a file in that temp directly and you can specify which instances you
want to run the command to.
Again, you can only add to the instances where your SSN agent is running.
So let's go ahead and do a run.
So currently it states that this is in progress.
On the refresh, you see that it has been successful.
So you're if you quickly do a list on the demo, you'll see that you have a file which is currently
created.
So that is what run commanders.
So now, before we conclude, let me also show you the compliance aspect of it.
So what this service basically does, it tells you if that you see two instances is missing certain
updates, many times what happens is that there are vulnerable packages within the C two instance due
to which they get attacked and even breached.
So the service will verify the instances and if they have the older packages.
So it says that the overall status of these two instances non-compliant.
And currently it also says that updates needed at issue.
So it basically also shows you the inventory, which basically means a list of packages which are part
of the instance.
So, again, all of these data is retrieved via the system.
Egypt here.
And in case if you want to update or pacho instances, you can make use of systems manager to do that.
Great.
So at the height of it all, you I hope you understood the code use case based on which the systems
manager service was introduced as it was discussing.
Systems manager contains a lot of support services, many of them users of services.
LeGrande communications manager, parts manager.
Complaints are completely dependent upon the SSA meeting.
There are certain services like the perimeter store, which does not really require a system agent here.
Great.
So again, depending upon the certification, the amount of services which would be part of the scope
would differ.
So it will only look into the services which are in scope with the certification that we're doing.
So with this will conclude this video.
I hope this video has been informative and I look forward to see you in the next video.