Hey.
And welcome back.
Now, in today's We Do, we'll be implementing our first auto scaling group from scratch.
Now, before we go ahead and implement auto skilling, you need a list at a certain important auto scaling
concepts that we need to understand.
One among them is associated with the auto skilling group sings.
Now, whenever you're configuring the auto skilling, you have to set a minimum maximum as well as their
desired capacity.
So this can be better expanded.
So you have a design minimum and maximum.
So let's go in and understand what each of these mean.
So let's assume that you have a minimum of one and a maximum of five.
So what would happen is acting instinct of dying 24/7.
There will be a minimum of one easy two instance that will always be running.
So that is why it is that effort as a minimum.
So if the minimum would have to be two, then at an instant of time there would be a minimum of two
easy two instances that would always add up.
So that is what minimum capacity basically is.
Then is the maximum capacity, maximum capacity denotes what is the maximum number of easy two instance
that you want to relaunch?
So India, since the maximum is fine.
You can have a maximum of five.
You see two instances that we be running at an instant of.
So depending upon the amount of law that the website gets, you can play it on the minimum as well as
maximum.
And the third one is their desired capacity, which denotes what is the number of instances that you
want to be running as part of your auto scaling group.
So in this case, since the desired capacity is to.
And when you launch auto scaling group based on this configuration, the number of instances that can
be launched would be to the minimum amount of instances can be one and the maximum amount of instance
based on which auto scaling would skip is five.
So let's quickly go ahead and revise that definition.
Minimum denotes the minimum number of instances that will be running as part of the auto scaling group.
Maximum denotes the maximum number of instances that can be scaled, and Bozak capacity demotes the
number of instances that should be done in indeed true.
So if you're looking to the diagram, minimum yeard is one desired capacity is two.
And that is that is in way that are too easy to instances that they're running and maximum size Yoda's
for so important.
If the load increases, your auto scaling group can launch more easy two instances as part of the group.
Second, important concept is associated with a launch configuration or a launch template.
So the launch configuration launch template contains a medius important instance configuration information
like M80 Security Group, Instant State, EBD, etc..
Now, in the earlier phase, we used to extensively make use of launch configuration.
However, Eatables has newly released the launch template and it is recommended to always make use of
launch template instead of launch configuration.
The third important concept is that elected put the auto scaling health check so easy to auto scaling
can determine the health status of, for instance, using one of the following.
So you have easy to health check.
You have you'll be high tech and you can also have custom hinting.
Hello.
Let's look into their two primary ones.
First one is these C2, which is provided by the Amazon.
Easy to go identify the hardware and software issues that me embed an easy coincidence.
So remember that in that instance is in any orders it then running or if the system status is impaired,
then this helps tech Villepin.
So we'll be discussing more about this practically in a moment.
You want to have a Eagleby health check?
So these are the whole tech that I've been provided by the elastic load balancer.
In case if you're on the Skilling group is under E.A., the last important concept before that practical
would be the types of skilling.
So remember that at a high level, Audu, there are two primary skilling types that are relevant.
One is the manual skilling.
And second is that dynamic skilling.
So the manual skilling is the most basic way to scale your resources where you specify only the genes
in minimum, maximum or desired capacity of your auto skilling group.
And depending upon these three barometers, the auto scaling will go ahead and create auto minuter instances
to be infused with configurations.
You also have a dynamic skilling that we'll be discussing at a later stage.
So let's do one thing.
Let's jump into practical.
In today's video, we'll be performing the MENOS getting so that our auto concepts are clear.
So currently I'm in DC to console.
Now, as you're discussing, you can either make use of launch templates and you also have an option
of launch configuration.
However, since launch templates either recommended one, we'll be using this.
So let's quickly go ahead and create a launch template here.
So I'll say EMC launch template, the template division.
Let's quickly call it as demo.
The M.A.
Let's use Amazon only next to.
Instead, they will be using a two micro keypad.
Let's quickly use one of the keepers.
Or you can even use nine.
Security in case if you want.
Let's use any of the different security groups that are relevant.
And the instance stack, let's call it days ETF.
Hey, for instance.
And let's also it for the desk manual once.
Then you can quickly go ahead and create a launch template.
And now, as we're discussing, there are multiple use cases of long standing.
One is you can tactically launch an instance.
You can also associate a launched imprint from auto killing group, or you can also use that splotched
fleet.
Anyways, we ignore this as of now.
And this is the launch template.
Now, if you go back down, you have an option of auto scaling groups.
So currently there are two versions of the UI that is available.
This is the order console.
How do I deliver a speech order?
And so it will no longer be present and only the newer one would be available.
So since both of them are present right now, let's go ahead and click on go to the new console.
So from the new open.
So let's go ahead and create the auto scaling group.
So the name of the auto scaling loop, let's call it as EDC hafe manual haven scaling.
Now you're let's associate the launch template and it will basically give in information on what exactly
the launch template contains.
Let's click on Next.
And now you can go ahead and associate VPC or you can also associate multiple subnets, or you, Les
Gordon, do it next.
Now, as we're discussing as part of the help take the deflater, one is easy to you can also configure
the you'll be health tech.
Now, based on easy to as we're discussing that anything other than branding is considered to be IMPAC
and we'll be discussing this practically Lenzer instances long.
So let's use thesea two one, which is the default one.
And the one that you're discussing is that group size.
You have a design.
You have a minimum.
And you have a maximum.
So let's say minimum is one desired.
Let's call it as two and maximum.
Let's call it.
S fine.
Now, you do know that you cannot have desired weightism more than maximum.
So if you tried to have a desirable seven, that cannot be done.
So it must be between a minimum and maximum.
So let's continue to put it as you know it in this giving policies.
You have got to get tracking's getting policy, which is more as part of the dynamic scaling.
And you also have an option of none.
So they be using nine years.
So that we can do the scaling manually.
So once that let's click on next, you can add a notification, will ignore it.
As of now, let's go ahead and do a next.
We'll get that abuse creep.
Let's go into the auto scaling group.
Greg Sword, auto scaling group is created.
Let's quickly open this up.
I know, sir, they moved unnecessary messages.
I did not.
So this is the order of review.
So if you see that these ideas to a minimum is one, maximum is faith, and there are multiple types
through which you can get exact information on what exactly is happening under the activity that you
can see on what is the exact activity that is happening, whether the instances are getting created,
instances I get into remaindered and so on.
You also have the automatic scaling back where you can go ahead and add multiple scaling.
So let's break it down.
So then you try to deskilling that are multiple scaling types as part of the dynamics.
Getting that data, I mean, but we ignored it.
As of now and within the instance management, you get the information related to the instances that
are available.
So as expected, there are two instances that are available.
So when you go to the instances you're now, since we are not making use of dynamic scaling.
In order for us to scale up or maybe scale down, you have to manually go ahead and configure things
accordingly.
So let's quickly try them.
So let's quickly go towards getting group.
So I guarantee you, you can also see the same thing I spotted before a concert anyways.
We'll be using the newest concert because this newer one will be replaced after some amount of pain.
So let's quickly open this up and let's assume that you've won more instances as part of the auto scaling.
So what you can do is you can go ahead and edit it and you can create their desired capacity to the
number of instances that you want to be running at this moment of.
And now, before we do that, I want to show you one of the aspects that elected to helped shape.
So as we're discussing that baby for the easy to help tech was available.
Now, what happens in the easy to help tech is pack it very face of whether that instance is running
or not.
In case if the instance is in any other state apart from running.
So, for example, if this instance is in stocks state, then how you take will assume that there is
an issue with this easy to instance, an auto scaling with, and we need that instance and a new instance
will be launched.
So let me quickly show you this.
So let's go ahead and stop the forced easy to instancing.
All right.
So easy to instance now is in this top speed.
So now the health check will determine that since this instance is in stops state, it is considered
as impaired as part of the auto scaling and auto scaling will go ahead.
And not one more instance.
So I'm different.
You see that the easy doing stent that we had to stop, it was automatically terminated.
And this is done as part of the auto scaling.
It set.
And on one more refreshed, you will see that you have one more easy to instance that this automatically
being lodged.
So this is the basic concept.
Now, as part of manually scaling, if you want more instances to be available later tomorrow, there
will be a big traffic that is expected.
And you want more amount of instances that back of the auto scaling.
Let's go ahead and break it up so you can go at eighteens their desired capacity.
Let's do it as three and let's click on update.
So from the easy to concern on that fish, you see one more easy to instance has been created.
Now, again, yet if you go to activity, you see the exact activity that the auto scaling has done.
And this is really helpful in the longer term.
So initially, you are seeing a message to the elliptic to successfully launching an instant.
It is also showing you the two instance I did that it had launched in the third step.
It has terminated data specific instance.
And it is showing you the instance.
And it is also showing that the exact message stating that an instance was taken out also is, in response
to it, easy to detect, indicating it has been terminated or stopped.
So this is one.
Then you have one more instance that was created an active life.
You have one more instance that was created primarily because of the difference between that design
capacity and the actual capacity.
So that's the high limit or view about how you can go ahead and implement a the auto scaling.
We look into some of the important concepts as part of the auto scaling group.
And we also looked into various aspects related to the health check.
So this will conclude today's video.
I hope this will have informative for you.
And again, if you want, you can go ahead and domine these.
You see two instances primarily because David costs, too.
So let's quickly do that.
Nelkin, you can Goyder overheated either by removing the auto scaling group altogether or by changing
the minimum or desired one.
So let's quickly, Gordon, change it.
So let's modify.
Let's use that design as zero minimum as zero.
And you can go ahead and do upgrade.
So currently, since there are three easy two instances that are running, let's quickly refresh and
now you see all of the three easy two instances are shutting down.
And the subsequent briefly, you see all the instances of humanity.
Now, one more important part to remember here is that let's assume that the bizarre capacity is, too.
And there are two instances that are running and no change.
There is at capacity two to three.
So it's not like that after two seconds, after three seconds.
One more easy to instance, will be launched.
So there will be a little amount of time after which the instances that will be launched or terminated
depending upon the configurations that you say.
So that's a verdict.
And we conclude today's video.