AWS Builder Center
From AWS Console to CLI: How I Started Understanding AWS

From AWS Console to CLI: How I Started Understanding AWS

When I first started learning AWS, the number of services and options felt overwhelming. This article shares my beginner experience of moving from the AWS Console to the AWS CLI and understanding when and why each approach is useful.

From AWS Console to CLI: How I Started Understanding AWS

Starting with AWS can feel a little overwhelming.
There are so many services, buttons, settings, and new terms that it is easy to wonder where to begin. When I started learning AWS, I initially focused on the AWS Management Console because it was the easiest way for me to see what was happening.
But after working with AWS for a while, I realized that learning the AWS CLI was an important next step.
In this article, I want to share what I learned while making that transition and how it helped me understand AWS better.

Starting with the AWS Management Console

The AWS Management Console is probably the most beginner-friendly way to start exploring AWS.
You can visually interact with services such as EC2, S3, IAM, and many others without remembering commands.
For example, when working with an EC2 instance, the console lets you see things like:
  • Instance status
  • Instance type
  • Public IP address
  • Security groups
  • Storage
  • Networking information
For someone who is just starting, this visual approach is extremely helpful.
Instead of memorizing commands, I could click through the options and understand what each setting actually did.

Then I discovered the AWS CLI

After getting comfortable with the console, I started using the AWS Command Line Interface (AWS CLI).
At first, using commands instead of clicking through the console felt slightly confusing.
For example, instead of opening the S3 service and manually looking for a bucket, I could use a command to list my buckets.
aws s3 ls

That small change made me realize something important:
AWS wasn't just a website.
The AWS Console was simply one way of interacting with AWS.
The CLI provided another way to communicate with AWS services.

Why use the CLI?

The biggest advantage I noticed was speed and repeatability.
If I need to perform the same type of operation multiple times, using commands can be much faster than navigating through the console every time.
The CLI also becomes especially useful when working with scripts and automation.
For example, a Bash script can contain AWS CLI commands and perform a series of operations automatically.
This is where AWS started connecting with what I was learning about Linux and DevOps.

Console vs CLI

I think of them like this:
AWS Console
AWS CLI
Visual
Command-based
Beginner-friendly
Requires command knowledge
Great for exploring services
Great for automation
Easy to see configurations
Easy to repeat operations
Useful for learning concepts
Useful for scripting and DevOps
Neither approach is necessarily "better."
They are different ways of working with the same AWS environment.

Where Terraform fits in

While learning the CLI, I also came across Terraform.
This introduced another important idea: Infrastructure as Code.
Instead of manually creating infrastructure through the console, or running individual CLI commands, Terraform allows infrastructure to be described using configuration files.
For example, instead of manually creating resources every time, I can define the desired infrastructure in a Terraform configuration and use Terraform to manage it.
This is one of the areas where AWS and DevOps started making much more sense to me.
The progression started looking something like this:
AWS Console → AWS CLI → Infrastructure as Code → Automation
Each step introduced a different way of managing cloud infrastructure.

What I learned as a beginner

One thing I would recommend to other beginners is not to try learning every AWS service at once.
It is much easier to start with a few fundamental concepts and understand how they work together.
For example:
  • IAM for permissions and access
  • EC2 for compute
  • S3 for object storage
  • VPC for networking
  • AWS CLI for command-line interaction
  • Terraform for infrastructure automation
Once these concepts become familiar, learning additional AWS services becomes much less intimidating.

My current approach

I now try to use the AWS Console when I want to visually understand something and use the CLI when I want to practice commands or automation.
I'm also exploring tools such as Terraform as I continue learning DevOps.
I'm still learning, so I don't see this as a "complete guide to AWS." Instead, this is my experience of how AWS started becoming easier to understand once I stopped thinking of it as just a web console.

Final thoughts

If you're just starting AWS, don't worry about memorizing hundreds of services.
Start small.
Create something. Break something safely. Look at the console. Try the same thing from the CLI. Then ask yourself how you could automate it.
That process helped me understand AWS much better than simply watching tutorials.
And honestly, that's what made cloud computing start feeling less complicated and more practical.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article