Hayden, and welcome back.
Now in today's video, we'll be discussing about batch management, which is part of the systems manager
offering.
Now, the patch manager automates the process of putting the managed instances with border security
related and other types of leads.
So let's understand this with a simple animation where you have a server here, you can consider it
to be easy to instant's and you have a batch manager.
So the best manager here, first it can go ahead and it can scan for missing patches.
Now, once it has kind over four missing pages, it will go ahead and it can create a list of what are
the new updates which are missing on this server so these updates can be fixed, security deleted,
etc..
So once the patch manager has figured out that these are the new updates which are missing on the server,
what it can go ahead and do is it can go ahead and apply the patches.
So if the server is missing patches, then the chances are that this server can be vulnerable to security
and other type of attacks.
So this is the reason why you have this background.
Now, once the Battis has been identified, the device manager can go ahead and also apply the associated
updates to the server.
So once the updates are applied, then again, this is green, which means that there are no new patches
which needs to be applied.
So that's what the batch manager does at a high level.
You know, whenever you're working with the servers, there are certain important terminologies that
you will need to understand.
The first one is the patch baseline, not the patch.
Baseline service determines the list of missing patches that needs to be installed in that instance.
So that baseline defense, which patches are approved for installation on your instances so you can
specify approved or rejected packages one by one, so we can take an example.
So there are a lot of missing patches all year.
So do you want to go ahead and apply all the missing patches to the server or there are certain packages
which you do not want to apply.
So all of those configurations can be applied at about a baseline level.
So in this specific missing patches, if you do not want the government to be applied to the server,
you can specify it at the patch baseline level.
Now, this is very important because a lot of agents are specific to the conclusion.
And sometimes if you upgrade the conclusion to the higher ones, then a lot of agents like specificly,
the idea Sipes agents, they stop working.
So you have to be very careful while applying the patches all year.
So I hope you understood what that baseline does.
The second important terminology here is the maintenance window.
So maintenance window provides a mechanism for scheduling a particular activity on a specific target.
So let's say that you want to perform tatting activity at 2:00 a.m. in the morning so this can be configured
at the maintenance window, period.
So these are the two important terminologies.
Let's do one thing.
Let's quickly take a demo so that this can be better understood.
No, I mean, the systems manager Consolo, you and correctly, you will see that we have one instance
which is available.
Now, if you look at the patch manager, you it your it is showing you did patch BU's lengths as we
were discussing past baseline is where you can go and deal with the approval to do the resection, etc.
So there are a lot of bad baselines which are available and these are the ones which are being created.
Vadarlis So you have passerby's lines for ad hoc yachties, baselines for Amma's only.
That's what you would do for S.O.S and others.
So let's take a sample example of the patch Baisley associated with Amazon Linux.
Now, if you look a year under the approval rules now for declassification of security, so for any
battis associated with the security, having the severity of critical and important, then there is
no auto approval delay which states that wait seven days before approving.
So any time with a badge associated with the security, having a severe variety of critical and important
is release.
Then there is a seven days of approval window post which the badge will be approved and it will be pushed
to the instances within your environment.
Similarly, you also have the classification of bug fix and so on.
So this is an example of a default by Tabby's language and is androids.
Now, let's also take an example of a custom badge Beesley.
So I have created one custom passerby's then for today's demo.
And if you look into this beastliness.
You have a classification and the classification is associated with security, the security is critical
and important, and yet we have defined that anytime there is a bad associated with the security of
critical week, zero days before approving, so that the instances are passed immediately.
Now, there is also one more rule that if there are any parties associated with the severity of importing,
then the three days before approving.
And also, if you look within the exceptions where there is one packet which is rejected, that is gone.
So even if agonal has an important level security, that that will not be pushed to the environment.
So this is a simple example of what that baseline does now.
The next important thing that we need to understand was the maintenance of know.
So if we look into the maintenance window, you see that I have one maintenance window created and the
need is less traffic.
And so let's quickly open this up.
And within this maintenance window, you'll see that the duration is one hour and it has a current rate
expression, Gloria.
So what you can do is via the Koran, you can specify which time you want to push the parties into.
Many times what happens is that if you're are pushing the parties are during the peak hours, then there
can be issues related to your application.
So what you might want to do, decide a time where you have the least amount of traffic.
And in that time you can Gordon push the parties into so certain times you will see that whenever you're
pushing parties, the application can go down.
So you have to be very careful.
Always schedule your parties in the duration when you have the least amount of traffic so that even
if something goes wrong, you have some amount of time for fixing things.
So that's associated with the current expiration.
No.
One good thing that I like is that the maintenance window gives you the exact time.
Then this maintenance window will come into effect.
So you're it is eight thirty UPC, so this maintenance window will be executed at do a.m. in the morning
in this diner in getting green.
So let's go back to the batch manager over here and let's click on Configure Configurability.
Now within you, there is one important thing that I wanted to show you is the patch operations.
So there are two types of bad operations here.
First one is scan only and second one is scan and install.
So can only really go ahead and it will only scan for the missing patches.
It will not apply if we look into the animation that we were discussing after scanning for the missing
patches, the patch manager also has a capability to apply the patches so that the system is up to date.
So you have the option to do any one of these.
Now, when you do a scan, only then, as you are discussing it, will show you the list of missing
patch and that list can be seen at the compliance level.
So if you click on the compliance level, basically I have created one bad manager that can only option.
So once you have done that within the complaint, you will typically see that there are certain non-compliant
results as far as the batting is concerned.
And if you open this up, let's click on the instant.
Zaydi.
So you're it basically shows you the list of packages that are part and also shows the list of updates
that I need in grey.
So that was associated with the compliance.
So that's the high level overview about the patch manager and the capability that it offers under the
SSA offerings so that this will conclude this video.
I hope this review has been informative and I look forward to see you in the next video.