Become an AWS pro with techniques to optimize cloud costs, efficiency, and automation. Developed by AWS Solution Certified Architects. Get hands-on skills with no setup, no cleanup, no hassle.

'AWS Cost optimization' Course Cover Art.png

Your organization weighed the options, ran the numbers, took a deep breath, and migrated to the cloud. That’s a perfectly solid strategic move—but your monthly invoices aren’t quite as lean as your original business case predicted. What’s worse, they are actually larger than your prior costs and increasing! This, unfortunately, is not uncommon. However, you can manage your resources with smart cost optimization techniques to shrink those bills. 

Optimizing your costs–regardless of the cloud provider–takes some work. In this course, you'll discover methods and tools on AWS to optimize cloud costs, including best practices for efficiency, cost transparency, and automation. 

You'll gain a comprehensive grasp of cloud economics, cost considerations, and a practical toolbox for streamlining AWS workloads with reduced manual effort. By implementing some strategies in this course, you will significantly reduce the chances of ever getting that surprise AWS invoice again!

AWS Cost Optimization

What would be the most cost-effective way to guarantee that we have resources available for a small failover instance in the event of a disaster recovery scenario?

What would be the most cost-effective way to guarantee that we have resources available for a small failover instance in the event of a disaster recovery scenario?

A Spot Instance of an `m5.xlarge` instance

A Convertible Reserved Instance of an `m5.xlarge`

A Standard Reserved Instance of an `m5.xlarge`

A Standard Reserved Instance of an `t4.xlarge` in unlimited mode

A customer has a long-running process on a server with CPU demand that varies considerably. Although their application CPU demand varies, the application will fit nicely within an `m5.xlarge` or `t5.xlarge` footprint. Additionally, they need to keep their monthly cost for this instance consistent. You have been asked to recommend a reserved instance model and instance type. What would be the most cost-effective and consistent option?

A customer has a long-running process on a server with CPU demand that varies considerably. Although their application CPU demand varies, the application will fit nicely within an <code>m5.xlarge</code> or <code>t5.xlarge</code> footprint. Additionally, they need to keep their monthly cost for this instance consistent. You have been asked to recommend a reserved instance model and instance type. What would be the most cost-effective and consistent option?

4 EC2 instances and 4 databases running as containers on ECS Fargate

4 EC2 instances and 4 SageMaker Inference Endpoints

What scenario would be best for a Compute Savings Plan (i.e., result in the best cost savings)?

What scenario would be best for a Compute Savings Plan (i.e., result in the best cost savings)?

Spot Instances are not an option because they do not support the ARM64 architecture.

Spot Instances must be purchased in advance in minimum quantities.

Spot Instances will always be available when we need them because AWS has unlimited capacity.

A Spot Request can be set up to maintain a min/max of one instance when the spot price is within our desired range.

We have an AMI of a system that hosts a business process on ARM64 architecture. As this process is not mission-critical, it does not have to remain running at all times. We believe that Spot Instances might be a suitable option. What is _true_ of Spot Instances in this case?

We have an AMI of a system that hosts a business process on ARM64 architecture. As this process is not mission-critical, it does not have to remain running at all times. We believe that Spot Instances might be a suitable option. What is true of Spot Instances in this case?

A company has EC2 instances across several regions but wants to use some strategies to help save money. At this point, they are unsure whether they should be consolidate into one region or continue to have instances in multiple regions. Which strategy allows for the most regional flexibility?

A company has EC2 instances across several regions but wants to use some strategies to help save money. At this point, they are unsure whether they should be consolidate into one region or continue to have instances in multiple regions. Which strategy allows for the most regional flexibility?

Test your knowledge of the topics covered in this chapter.

Introduction

The Economics of Cloud Computing

The AWS Cost Optimization Pillar

Rightsizing

Elasticity

Pick the Right Pricing Model

Measure, Monitor, Improve

More Ways to Save

Wrap Up and Keeping Current

You Make The (Cost Optimization) Call!

Quiz: AWS Pricing Models