Hi, everyone, and welcome back.
Now, in today's video, we are going to discuss about the basics of a Compute Optimizer service.
Now, in most of the organizations that are based on eight tables or in fact any cloud environment,
one of the primary challenges is related to over provisioning.
So you will generally see that the easy two instances are not sized correctly when a developer launches
an easy to instance for his own test environment, he might launch an easy to instance with eight GB
RAM and so on, which is not always required.
So this is one of the common issues and this at the end of the month leads to a big bill.
So one of the question that comes is since a US is launching so many services, is there a specific
tool or is there a specific service that can check about this or provisioning or maybe under provisioning
related activity and can give us a good report?
So this is where the Compute Optimizer service comes into picture at a high level overview, the Compute
Optimizer service, it recommends the optimal resources for your environment and that can in fact reduce
your cost and improve the performance.
So how does it recommend the optimal resources?
It does it by using the machine, learning to analyze the historical utilization matrix.
For example, if you look into this specific screenshot, you have 13 EC2 instances among which 30%
are under provision, 61% are over provision and 7% are optimized.
And it will also give you which of them are under provision or provision so you can go ahead and size
them accordingly.
Along with that, the compute optimizer, it also provides a recommendation related to the optimal instance
types.
For example, you see that all of these instances are over provision.
It shows the current instance type and it also shows you what are the recommended instance type.
So for first AC to instance from C five dot slash, it is recommending PT three dot large and there
is also a significant cost benefit of migrating to the recommended instance type.
And in fact this is very beneficial for the organizations.
The next important point is related to the supported resource types.
We have seen that the Compute Optimizer does provide recommendation related to the EC two instances.
Apart from that, it also gives recommendation related to the auto scaling groups, the EBS volumes,
the X service on a Farragut as well as Lambda functions.
Now, before we proceed further, let's go ahead and have a quick look into the Compute Optimizer service.
So currently I am in the Compute Optimizer service.
Again, since this is a test account, you do not have too much of data that is populated over here,
but it shows you the savings opportunity in percentage as well as the absolute numbers.
And as we're discussing, it shows you the under provision instance, the optimise instance and over
provision.
The instance that I have is optimise at this stage.
Along with that, as we're discussing, it supports ESI two auto scaling, Lambda EBS volumes X Service
on target and at a later stage more of the resources will be supported as part of the Compute Optimizer.
Now one of the question that comes is how does the Compute Optimizer service know whether the EC2 instances
optimize or it is over provision or under provision?
One of the important part here is that it makes use of the cloud watch matrix as basis of the recommendation.
Now, when we discuss about the cloud watch matrix, by default you have the matrix like CPU utilization,
the disk IO network, IO and so on.
So let me also quickly show you this.
So when we discuss about this EC2 instance, if we go to monitoring, there are certain matrix that
you see over here.
You have CPU utilization, you have the network related matrix, the disk related matrix and so on.
So all of these matrix are taken into account.
Apart from that, if you want the compute optimizer to take into account the operating system level
matrix, like how much memory has been used, then in such case you need to install the cloud agent
on your EC2 instance that can publish the set of matrix.
Generally in production environments.
Memory usage matrix is a very important one.
So this is something that you have to take a note of.
Apart from that, you need to also keep a note of an enhanced infrastructure matrix, which is quite
important for production environments.
So at a high level overview, the enhanced infrastructure matrix is a paid feature of compute optimizer
that applies specifically to the EC2 instance resources.
So one of the benefit that it provides is that it extends the utilization matrix analysis lookback period
to up to three months, which is 93 days compared to the 14 days period.
So since this period is increase, it gives a longer history of utilization metric for the overall analysis
to take place.
So since this is a paid feature by default, you will generally see it to be disabled.
However, in case if you like, you can go ahead and enable it.
So in fact, let me also quickly show you so I have one easy to instance that is available for this
specific easy to instance.
It is giving a certain recommendation related to the instance type and how much price difference it
would make if we switch.
Apart from that, the important part here is the enhanced infrastructure matrix.
So in case if you like, you can go ahead and enable it so that the overall lookback period is much
more larger and it can give you a better recommendation.
The last important point is related to the export recommendations.
So all of the recommendations that you see from the GI console at the instance level in case if you
like, you can also export them to the S3 bucket so that you can go ahead and record the details over
time and you can also share it with others.
So these set of recommendations are exported in a CSV file and its metadata in JSON file at the S3 level.
So if you look into the screenshot, also the resource type of EC two instance is exported to a specific
S3 bucket.
Let me also quickly show you.
So if you look into the exports here at this stage, the resource type of EC two instance, the details
associated with this is exported to the destination S3 bucket.
So if I quickly open this up, it shows me the CSV file over here.
So in case if I download it, let's open this up and this is where all of the details related to the
ESI two instance are log.
You see all of the details are present over here grid.
So I hope with this at a high level overview, you understood the basics of the Compute Optimizer service
and with this will conclude today's video.