AWS Certified Cloud Practitioner
Ways to Access AWS
Learn the main ways to work with AWS services: the Management Console, the CLI, the SDKs, and the underlying API, plus when to reach for each one.
- Identify the four main ways to access AWS: Console, CLI, SDKs, and the API
- Explain what the AWS Management Console is and when it fits best
- Describe how the CLI and SDKs support scripting and automation
- Explain that the Console, CLI, and SDKs all call the same AWS API
Why this matters
Once you have an AWS account, you need a way to actually create and manage resources. AWS does not lock you into one method. You can click through a web interface, type commands in a terminal, or call services straight from your application code. The method you pick depends on the task: a quick one-off change, a repeatable script, or a feature inside an app.
There are 4 main ways to work with AWS: the Management Console, the Command Line Interface (CLI), the Software Development Kits (SDKs), and the API that sits underneath them all. Knowing what each one is for is enough for the exam, and it shapes how you work day to day.
AWS Management Console
The AWS Management Console is a web-based graphical interface. You sign in with a browser, and you point and click to launch instances, create storage buckets, view dashboards, and check on your resources. It groups services into menus and shows visual feedback, so it is the easiest place to start when you are learning or exploring.
The Console is a good fit for one-off tasks, for trying out a new service, and for getting a visual picture of what you have running. It is less suited to work you need to repeat exactly, because every step depends on a person clicking the same buttons in the same order. There is also a mobile app version of the Console for checking resources on the go.
AWS Command Line Interface (CLI)
The AWS CLI is a single tool that lets you control AWS services from a terminal. With one tool installed and configured, you can manage many services by typing commands instead of clicking. It runs on Windows, macOS, and Linux.
The real strength of the CLI is automation. Because commands are just text, you can put them in a script and run that script on a schedule or as part of a larger process. This makes your work repeatable: the same script produces the same result every time, with no manual clicking. A command looks like this:
aws s3 ls
aws ec2 describe-instances --region us-east-1
AWS also offers CloudShell, a browser-based shell that you launch from inside the Console. It comes pre-authenticated and has the CLI already installed, so you can run commands without setting anything up on your own machine.
AWS SDKs
The AWS SDKs (Software Development Kits) let your application talk to AWS services directly from code. Instead of shelling out to the CLI, you call AWS using functions in your programming language. AWS provides SDKs for many languages, including Python, JavaScript, Java, .NET, Go, Ruby, and others.
SDKs are the right choice when AWS access is part of an application you are building. For example, a web app that stores user uploads in Amazon S3 would use the SDK for its language to send and retrieve those files. The SDK handles the lower-level work for you, such as signing requests and retrying failed calls, so you write less plumbing code.
The AWS API underneath
Every method above is a front end over the same thing: the AWS API. The API is a set of HTTPS requests that AWS services accept. When you click a button in the Console, it sends an API call. When you run a CLI command or call an SDK function, those also turn into the same API calls.
You rarely call the API by hand, because the Console, CLI, and SDKs are easier. But it helps to understand the picture: there is one API per service, and the friendlier tools are just different ways to reach it. This is why anything you can do in the Console you can usually also do with the CLI or an SDK.
Choosing the right method
| Method | Interface | Best for |
|---|---|---|
| Management Console | Web graphical interface | Learning, exploring, one-off tasks, visual checks |
| CLI | Terminal commands | Scripting, automation, repeatable tasks |
| SDKs | Code in your language | AWS access built into an application |
| API | HTTPS requests | The low-level layer the others call |
There is no single "correct" method. Many teams use all of them: the Console to explore and check, the CLI to automate operations, and the SDKs inside their applications.
Exam tips
- The Management Console is the web-based graphical interface; best for learning and one-off tasks.
- The CLI controls services from the command line and is built for scripting and automation.
- SDKs let application code call AWS services in a specific programming language.
- The Console, CLI, and SDKs all send requests to the same AWS API.
- CloudShell is a browser-based shell, launched from the Console, with the CLI pre-installed and pre-authenticated.