Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/41 ▾
  1. 1.Cloud Concepts: Benefits & Economics0/4
    1. The six advantages of cloud computing
    2. Elasticity, scalability, agility, high availability and global reach
    3. Cloud economics: fixed versus variable cost and total cost of ownership
    4. Licensing, rightsizing and automation
  2. 2.Cloud Concepts: Well-Architected & Migration0/5
    1. The six pillars of the Well-Architected Framework
    2. Pillar trade-offs and the AWS Well-Architected Tool
    3. The AWS Cloud Adoption Framework: outcomes, perspectives and phases
    4. Migration strategies: the 7 Rs
    5. AWS migration services and tools
  3. 3.Security: Shared Responsibility & Compliance0/4
    1. Security of the cloud and security in the cloud
    2. How responsibility shifts with the service you choose
    3. Compliance reports, programs and where data lives
    4. Encryption, keys and audit records
  4. 4.Security: IAM & Access Management0/4
    1. The root user and sign-in credentials
    2. IAM users, user groups and roles
    3. Policies, deny rules and least privilege
    4. Federation, IAM Identity Center, Amazon Cognito and secrets
  5. 5.Security: Services & Resources0/4
    1. Blocking web attacks and DDoS: AWS WAF, AWS Shield and AWS Firewall Manager
    2. Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie
    3. Collecting, investigating and advising: Security Hub, Detective and Trusted Advisor
    4. AWS Marketplace and where to find security help
  6. 6.Technology: Deployment & Global Infrastructure0/4
    1. Ways to access AWS: console, CLI, SDKs and APIs
    2. Deployment tools and cloud deployment models
    3. Regions, Availability Zones and high availability
    4. Multiple Regions, data residency and edge services
  7. 7.Technology: Compute & Networking0/4
    1. Amazon EC2 instance types, auto scaling and load balancers
    2. Containers, serverless compute, Lightsail and AWS Batch
    3. Inside a VPC: subnets, gateways, security groups and network ACLs
    4. Route 53 and connecting networks to AWS
  8. 8.Technology: Databases & Storage0/4
    1. Relational databases: Amazon RDS, Aurora and databases on EC2
    2. NoSQL, in-memory and graph databases, plus database migration
    3. Amazon S3 object storage, storage classes and lifecycle policies
    4. Block and file storage, Storage Gateway, AWS Backup and disaster recovery
  9. 9.Technology: AI, Analytics & Other Services0/4
    1. AI and machine learning services: pre-trained services and SageMaker AI
    2. Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
    3. Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
    4. Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
  10. 10.Billing, Pricing & Support0/4
    1. EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
    2. Data transfer costs, consolidated billing and cost allocation tags
    3. Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
    4. AWS Support plans, Trusted Advisor, AWS Health and where to get help
Saved in this browser. Move it to another device →
← Cloud Concepts: Benefits & Economics

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 →