Hello and welcome back.
And let's now touch on cost optimization consideration and strategies on IBS.
So let's start with right.
Easy to instant sizing.
So it appears as we know offers wide range of resource types in general but when it comes to easy to
as well we have so many.
We have all the way from the general purpose one through the GPO optimize the memory optimize the processing
optimized instances that we learned about.
So we have services like easy to ideas redshift elastic search EMR they give a lot of choices for instance
type usually when you are talking about easy two instances just a quick refresher.
We're talking about families so the families are the general purpose or the M4 for them family or the
C family or the family.
That's the family.
But within a family they are different sizes right.
So when you combine the family with the size that's the type.
So when I refer throughout the lectures type then you need to know.
That implies there is a specific family and a size within the term.
Okay.
In some cases selecting the cheapest type that suits workload requirements might be the best that could
be in some.
So you want to host your own blog that no one knows about yet and you would like to save on costs.
What would you do.
Free to finish the free tier then go for the t to go for the nano size within the T family.
In other cases so that could be a good a good choice but you could be launching a lot of t to micro
instances let's say you have seven eight nine and you're running most of the time using these instances.
Your job takes a long time to do.
And if you had the same done with two or three larger instances probably you would have had a much better
performance much better user experience and more satisfaction.
So in other cases using larger instance type can help reduce the overall cost for better performance.
The use of benchmarking to select the right instance.
So it's not about guessing it is not encouraging guessing at all but you need to benchmark you need
to test your application and find out when you load it.
What is the CPI you if I go with this instance.
So selecting the right instance type family and size which depends primarily on how the workload utilized
the CPSU Ram network storage and Io.
So these are all important factors that you need to take into consideration when you are benchmarking
to select the right instance type so it's not about guessing at all cost can also be reduced by selecting
the right storage solution for the needs as well so which storage solution would you go for SSD or do
you go for the regular ones.
Is it the provision I opps or is it the general purpose.
The one that provides bursting or the provision types on which one are you going to use also s three
offers a variety of storage classes.
So now we are talking about volumes or are they not also about storage class and so which one would
you use.
These are important considerations that we have done benchmarking.
Knowing what you need testing your application making sure that it can provide what you have selected
can provide what you are looking for at different performance requirements.
Let's talk about tagging and continuous monitoring.
One thing we need to understand cost of optimization is not something that you will do once and that's
it as your requirements grow as your business grows as your traffic grows as your application base grows.
You need to revisit always you need to have continuous monitoring analysis and find out what's going
on in your infrastructure and decide maybe you need to add maybe need to remove maybe need to to swap
and change things of what you have.
The applications are obvious and their usage will evolve through time.
Also NWS always launches new services to now if you have deployed something and it obviously has a better
solution than you used to do server bays and now there is server list.
Why don't you look into that and find out the cost benefits but also it could be efficiency benefits
could be less administration has.
There's a lot of things that you can gain from doing monitoring that could impact your cost in obvious
iterate frequently and regularly release new options as we mentioned and also it provides you tools
to help identify those cost saving opportunities and keep the resources right sites.
If you're talking about trusted advisor if you're talking about it this budgets that we talked about
we're talking about cost explorer all of these are things that could help you find out your usage your
costs and also some of them would be able to advise you on where you can save on cost and of course
those services will enable you to filter by service by region by celebrities on by usage etc. which
shows you where are the cost elements or the bigger chunks of course that you are incurring and definitely
you would start to look into that and find out how you can cut costs.
So if you're a CTO or comes to you and complains that our database bill is much higher now than six
months ago what's going on.
Please find out areas for cost optimization you need to be able to zoom into the bill and find out different
cost elements by service different cost elements by region.
If you have different regions availability zones by application so you can find out which one is costing
you more.
And then you can find by exploring new NWS options to save on that tagging strategies.
So how do we do tagging.
How do we approach the tagging thing.
Do we do it during the launch.
Do we do it after the fact.
Do we do it through the automation.
What do we do with Target.
It can be part of the build process.
So as you are launching an easy to instance as you are creating a security group as you are creating
an S three bucket then you start adding tags so it could be done through the build process and automated
with management tools like Elastic Beanstalk or it obvious works.
We can do tagging through them or we can use other services like as config which can be used to assess
whether specific tags are applied to your resources or not.
Let's take a quick break and come back and continue our discussion.
I'll see you after the break.
Thank you.