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 →
← Technology: Compute & Networking

Chapter 7 · Lesson 2 of 4

Containers, serverless compute, Lightsail and AWS Batch

1 min read

Container questions test whether you can tell an orchestrator from a registry and from a compute layer. These are separate roles, and each wrong answer usually gives one service another service's job.

  • Amazon ECS is the AWS-native container orchestrator.
  • Amazon EKS is managed Kubernetes. AWS runs the control plane, and because it is conformant Kubernetes, a team can bring existing Kubernetes workloads and tooling without refactoring.
  • Amazon ECR is the managed registry that stores container images; ECS and EKS pull images from it. It does not run containers.
  • AWS Fargate is serverless compute under ECS or EKS. You set CPU and memory per task and stop managing virtual machines.

AWS Lambda runs short pieces of code as functions in response to events, with no servers to manage, so it suits irregular jobs such as creating a thumbnail each time a file is uploaded.

Amazon Lightsail bundles a simple virtual private server with storage and data transfer at a predictable price, which suits a small website run by someone new to the cloud.

AWS Batch queues large numbers of jobs, schedules them and provisions the compute to run them. Example: a lab with 50,000 overnight jobs that can wait in line points to AWS Batch, not to a fleet of servers it sizes by hand.

Check yourself

1. A team already uses Amazon ECS to orchestrate its containers but wants to stop provisioning and scaling the virtual machines underneath them. What should the team adopt?

2. A company already runs its applications on Kubernetes on premises. It wants to move to AWS, keep its Kubernetes tooling and avoid refactoring. Which service best fits?

Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, Domain 3, Amazon EC2 Instance Types, Amazon VPC User Guide: Compare security groups and network ACLs

AWS Cloud Practitioner cheat sheet: every key fact on one page →