Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 1 · Lesson 4 of 4
Licensing, rightsizing and automation
1 min read
Software licenses are part of cloud economics. With Bring Your Own License (BYOL), a company reuses licenses it already owns, such as per-core database licenses, instead of paying for them again, and it stays responsible for following the license terms.
AWS License Manager helps it track license use across accounts. With License Included, AWS provides the license and its cost is built into the instance price, which suits a company that owns no licenses and wants nothing separate to buy or track.
Rightsizing means matching an instance's type and size to actual need at the lowest cost that still meets performance goals, for example moving instances that idle at low CPU to a smaller type.
It is an ongoing review, because workloads change, and the customer decides on the change. Auto Scaling changes how many instances run and Savings Plans change how you pay, so neither one is rightsizing. AWS Compute Optimizer can suggest better-fitting sizes from utilization data.
Automation saves money too. AWS CloudFormation builds identical environments from templates, treating infrastructure as code, which cuts manual labor and human error. Example: a team that hand-builds a demo environment in two days can launch the same template in minutes for every new client, and every copy matches.
Check yourself
1. A company already owns per-core database licenses and wants to keep using them after moving to AWS rather than pay for them again. Which licensing approach fits?
2. A company's instances run at about 10% CPU around the clock while performance goals are easily met. Which action is rightsizing?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, Overview of Amazon Web Services: Six advantages of cloud computing, AWS Well-Architected Framework: Cost Optimization pillar
AWS Cloud Practitioner cheat sheet: every key fact on one page →