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 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.
| Method | Best fit |
|---|---|
| AWS Management Console | A browser interface for one-time or visual tasks, with no code needed |
| AWS CLI | Commands typed in a terminal or saved in shell scripts |
| AWS SDKs | Calling AWS from inside an application, in its programming language |
| AWS CloudFormation | Describing 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 →