AWS Cloud Practitioner (CLF-C02) · Lesson 4 of 26
Rightsizing, Automation and Licensing
Explain rightsizing and the tools that recommend it, list the benefits of automation, and choose between Bring Your Own License and License Included.
Tip: turn your phone sideways or use full screen for larger labels.
Captions match the narration word for word. Press Space to play or pause and the arrow keys to change scenes.
Learning objective
Explain rightsizing and the tools that recommend it, list the benefits of automation, and choose between Bring Your Own License and License Included.
Exam mapping
Domain 1: Cloud Concepts (24%). Task statement 1.4 in the official exam guide.
Key takeaways
- Rightsizing matches instance type and size to what a workload actually uses, based on metrics. It's a continuous process, not a one-time task.
- AWS Compute Optimizer uses machine learning to recommend better sizes for EC2, Auto Scaling groups, EBS, Lambda, ECS on Fargate, RDS and more. Cost Explorer and Trusted Advisor also flag idle or underused resources.
- Rightsizing changes the size of a resource; Auto Scaling changes the number of resources.
- Automation is faster, more consistent and less error-prone, gives repeatable environments (for example with AWS CloudFormation) and avoids paying for idle resources.
- License Included puts the license cost into the hourly price: no up-front purchase, AWS handles compliance, and you can stop any time.
- BYOL reuses licenses you own (sometimes on EC2 Dedicated Hosts); you remain responsible for compliance, and AWS License Manager helps track it.
Exam tips
How the exam asks about this
Questions describe a situation and expect you to recognize the concept behind it.
| If the question mentions… | Think |
|---|---|
| An instance is much bigger than its workload needs | Rightsizing |
| Machine learning recommendations for the right instance size | AWS Compute Optimizer |
| Add or remove instances as demand changes | Auto Scaling (not rightsizing) |
| Build identical environments quickly with fewer errors | Automation (infrastructure as code) |
| The software license is part of the hourly price | License Included |
| Use existing licenses on AWS | Bring Your Own License (BYOL) |
| Track license usage and enforce license rules | AWS License Manager |
Common traps
- Rightsizing isn't Auto Scaling: one fixes the size of each resource, the other changes how many there are.
- BYOL isn't automatically cheaper. For short-term or changing workloads, License Included can cost less and is simpler.
- With BYOL, license compliance stays your responsibility. License Manager helps you track it, but doesn't take over the responsibility.
- Rightsizing once isn't enough: workloads change, so review recommendations regularly.
Practice
Exam-style questions
Answer each one before you open the explanation.
Question 1. A company's Amazon EC2 instances run at less than 10% CPU utilization most of the time. Which practice would reduce costs without affecting performance?
- Rightsizing the instances to a smaller size
- Adding more instances with Auto Scaling
- Moving the instances to a second Region
- Bringing their own operating system licenses
Show answer
A. Rightsizing the instances to a smaller size. Rightsizing matches the instance size to actual use, so oversized instances move to smaller, cheaper sizes. Auto Scaling changes the number of instances, which doesn't fix an instance that's too big.
Question 2. Which AWS service uses machine learning to recommend optimal instance types and sizes based on historical utilization?
- AWS License Manager
- AWS CloudFormation
- AWS Compute Optimizer
- AWS Pricing Calculator
Show answer
C. AWS Compute Optimizer. Compute Optimizer analyzes usage metrics with machine learning and recommends better configurations. The Pricing Calculator estimates costs of a planned design; it doesn't analyze running resources.
Question 3. Which TWO are benefits of automating infrastructure tasks on AWS? (Select TWO.)
- Fewer human errors
- AWS takes over responsibility for license compliance
- Consistent, repeatable environments
- Instances never need rightsizing again
- Lower prices for every AWS service
Show answer
A. Fewer human errors and C. Consistent, repeatable environments. Automation follows the same steps every time, which reduces errors and builds identical environments. It doesn't transfer license compliance to AWS or replace the need to review sizing, and it doesn't change AWS prices.
Question 4. A company wants to run Microsoft SQL Server on AWS for a three-month project. It doesn't own any SQL Server licenses. Which licensing approach is MOST suitable?
- Bring Your Own License on Dedicated Hosts
- Buy perpetual licenses before the project starts
- Use AWS License Manager to create licenses
- Use a License Included option
Show answer
D. Use a License Included option. License Included builds the license into the hourly price, with no up-front purchase, so it suits short projects. BYOL needs licenses the company already owns, and License Manager tracks licenses but doesn't sell them.
Question 5. A company owns Windows Server licenses that are counted per physical core and wants to use them on AWS. Which option supports this?
- Amazon EC2 Dedicated Hosts
- AWS Trusted Advisor
- Amazon EC2 Auto Scaling
- AWS Compute Optimizer
Show answer
A. Amazon EC2 Dedicated Hosts. Dedicated Hosts give you a physical server with visible sockets and cores, which supports BYOL licenses counted that way, subject to the license terms. The other services monitor or scale resources; they don't address licensing.
Transcript
Lesson transcript
The full narration, scene by scene. The captions file contains the same text with timings.
Scene 1 · 0:00
Lesson 4: Rightsizing, automation and licensing. In lesson three, we saw why the cloud can cost less than your own data center. Now we'll see how to keep your cloud bill low, which is also part of cloud economics in Domain 1. We'll cover two ideas. First, rightsizing, and how automation saves time and money. Second, the two ways to pay for software licenses on AWS: Bring Your Own License, or BYOL, and License Included.
Scene 2 · 0:30
Rightsizing: match the size to the need. Our online store launched its web server on a large instance, just to be safe. Months later, its CPU rarely goes above ten percent. That's capacity the store pays for every hour but doesn't use. Rightsizing means matching the instance type and size to what the workload actually needs. Moving to a smaller instance gives the same performance for customers and a lower bill for the store.
Scene 3 · 0:59
Rightsizing never stops. Rightsizing isn't a one-time job. You measure how resources are really used, with metrics such as CPU, memory and network from Amazon CloudWatch. You look for resources that are too big or too small, change the type or size, and then keep watching, because workloads change. A server that fits today may be too big after a redesign, or too small during the holiday rush.
Scene 4 · 1:28
Tools that recommend the right size. AWS does the analysis for you. AWS Compute Optimizer uses machine learning on your usage metrics to recommend better sizes for EC2 instances, Auto Scaling groups, EBS volumes, Lambda functions, ECS services on Fargate, RDS databases and more. Cost Explorer's rightsizing recommendations find idle and underused EC2 instances and estimate the monthly savings. And Trusted Advisor's cost optimization checks flag things like instances with low utilization.
Scene 5 · 1:56
Rightsizing is not Auto Scaling. Don't confuse rightsizing with Auto Scaling. Rightsizing fixes the size of each resource, for example replacing one large server with one smaller server. Auto Scaling changes the number of resources as demand changes: it adds servers during a busy hour and removes them when it's quiet. Most workloads use both: right-sized instances, in a group that grows and shrinks automatically.
Scene 6 · 2:23
The benefits of automation. Auto Scaling is one example of automation, and the exam expects you to know its benefits. Automated tasks run in minutes instead of weeks. They follow the same steps every time, so there are fewer human errors. With infrastructure as code, such as an AWS CloudFormation template, the store can build identical test, staging and production environments on demand. And staff spend their time on the business instead of repetitive work.
Scene 7 · 2:54
Stop paying for idle hours. Automation also saves money directly. The store's developers only use their test servers during office hours, but the servers run all week. A week has a hundred and sixty-eight hours. Running ten hours a day, five days a week, is only fifty. A schedule that stops the servers at night and on weekends, for example with the Instance Scheduler on AWS solution, cuts their running hours by about seventy percent.
Scene 8 · 3:24
License Included. Now the second idea: software licenses. Some software, like Windows Server, SQL Server or Oracle Database, needs a license. With License Included, the license cost is built into the hourly price of the instance or database. You don't buy anything up front, AWS takes care of license compliance, and when you stop using it, you stop paying. Windows Server on EC2 and SQL Server on Amazon RDS are common examples.
Scene 9 · 3:55
Bring Your Own License (BYOL). With Bring Your Own License, or BYOL, you reuse licenses your company already owns. Some licenses are counted per physical socket or core, so you may need an EC2 Dedicated Host: a physical server just for you. Some Microsoft licenses with Software Assurance can run on shared instances through License Mobility. Either way, you stay responsible for compliance. AWS License Manager helps by tracking license usage and enforcing your rules.
Scene 10 · 4:25
Which license model to choose. So which should you choose? License Included fits when you don't own licenses, the workload is short-term or changes a lot, or you want AWS to handle compliance and start right away. BYOL fits when you've already paid for licenses, the workload is steady and long-term, and the vendor's terms allow it. Neither is always cheaper: compare the total cost for your own workload.
Scene 11 · 4:53
How the exam asks about this. Here's how the exam asks about this. Matching instance size to actual usage is rightsizing, and machine learning recommendations for it point to AWS Compute Optimizer. Adding servers when traffic grows is Auto Scaling, not rightsizing. Stopping development servers at night is automation saving cost. A license cost built into the hourly price is License Included, reusing licenses you own is BYOL, and tracking license usage is AWS License Manager.
Scene 12 · 5:24
Recap: rightsizing, automation and licensing. To recap: rightsizing matches each resource to what it really needs, and it's a continuous habit, helped by Compute Optimizer, Cost Explorer and Trusted Advisor. Automation makes work faster and more consistent, and it stops you paying for idle resources. And for software, License Included is simple and flexible, while BYOL reuses licenses you already own. Next, we'll meet the AWS Well-Architected Framework and its six pillars.
Sources and accuracy
Checked against AWS documentation and the official CLF-C02 exam guide on October 18, 2026. AWS changes often, so confirm details in the current documentation. Diagrams and numbers in the animation are illustrative.
- AWS resources supported by Compute Optimizer
- Instance Scheduler on AWS: automate starting and stopping AWS instances
- What is AWS License Manager?
- RDS for Oracle licensing options
- CLF-C02 exam guide: Domain 1, Cloud Concepts
This free course is independent and isn't affiliated with or endorsed by Amazon Web Services. AWS and AWS Certified Cloud Practitioner are trademarks of Amazon.com, Inc. or its affiliates.
Preparing a team for AWS certification?
I run hands-on AWS training for teams, from Cloud Practitioner basics to architecture, built around your own environment.