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: Deployment & Global Infrastructure

Chapter 6 · Lesson 1 of 4

Ways to access AWS: console, CLI, SDKs and APIs

1 min read

Every way of working with AWS is a layer over the public AWS service APIs. Whether someone clicks in a browser, types a command or runs a program, the request ends up as an API call, with no relay server in your VPC and no stack in between.

The exam asks you to pick the layer that fits who is doing the work and how often.

MethodBest fit
AWS Management ConsoleA browser interface for one-time or visual tasks, with no code needed
AWS CLICommands typed in a terminal or saved in shell scripts
AWS SDKsCalling AWS from inside an application, in its programming language
AWS CloudFormationDescribing whole environments as code so they can be built again the same way

Read the scenario for clues. A non-technical person doing something once points to the console. An operator automating a nightly job points to the CLI. Work that happens as part of a program's own logic, such as saving each new upload to Amazon S3, points to an SDK.

Example: a clinic's office manager wants to see this month's bill once, so the console fits. Its patient portal must store each scanned form in Amazon S3 as it arrives, so the portal's code uses an SDK.

Check yourself

1. A development team is building an order-processing application. As part of its normal logic, the application must save each uploaded invoice to Amazon S3. Which access method should the team use?

2. A finance analyst with no programming experience needs to check, just this once, which Amazon EC2 instances are running in one Region. Which access method fits best?

Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, AWS Global Infrastructure: Regions and Availability Zones, AWS CloudFormation User Guide

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