Skip to content
AWS aws getting-started 5 min read

The AWS Management Console

The AWS Management Console is the web-based dashboard you use to create, configure, and watch over your cloud resources from a browser. AWS (Amazon Web Services) has over 200 services, and the console is where most beginners first meet them. Learning the layout early saves you hours of confusion later, because the single biggest source of “where did my resource go?” panic is the Region selector hiding in the top-right corner. This page walks you through the parts of the console you will touch every day.

What the console is (and when to use it)

The console is the graphical front door to AWS. Behind the scenes, every button click is just calling the same AWS API (Application Programming Interface) that the CLI (Command Line Interface) and SDKs (Software Development Kits) call. That means anything you do in the console can also be done from a script.

When to use the console: exploring a new service, one-off manual tasks, reading dashboards and metrics, and learning. The visual layout helps you discover options you didn’t know existed.

When NOT to use it: anything you need to repeat or reproduce. Clicking buttons by hand is not repeatable and is impossible to review. For production changes, prefer the CLI or Infrastructure as Code (IaC) tools like CloudFormation or Terraform so every change is written down and version-controlled.

Tip: Treat the console as a teaching tool and a dashboard, not as your deployment mechanism. If you find yourself doing the same clicks twice, script it.

A tour of the layout

When you sign in, the console has a few fixed areas. Here is what each one does, going from the top bar downward.

AreaLocationWhat it does
Service searchTop centerType a service name (e.g. “EC2”, “S3”) to jump straight to it
Region selectorTop rightChooses which geographic Region you are working in
Account menuFar top rightAccount ID, billing, security credentials, sign out
Notifications / CloudShellTop right iconsAlerts, and a browser-based terminal
Pinned services / favoritesLeft nav and homeQuick links to the services you star

The fastest way to navigate is the search box at the top. Type the service name or even what you want to do (for example “create bucket”), and the console suggests services, features, docs, and blog results. Click the star next to any service to pin it to the top navigation bar so it is one click away next time.

The account menu

The menu under your account name (top right) is where you find your 12-digit Account ID, the Billing and Cost Management dashboard, and your security credentials. This is also where you sign out and where you switch IAM (Identity and Access Management) roles if you work across multiple accounts.

The Region selector — the #1 source of confusion

A Region is a physical location in the world where AWS runs clusters of data centers (for example us-east-1 in Northern Virginia or eu-west-1 in Ireland). Most AWS services are regional: a resource you create in one Region simply does not exist in another. The Region selector in the top-right corner controls which Region the console is currently showing you.

Here is the gotcha that bites almost every beginner: you create an EC2 instance (a virtual server) in us-east-1, switch the Region selector to eu-west-1 later, and your instance has “disappeared.” It is not gone. You are just looking at the wrong Region. The instance is exactly where you left it.

Warning: If a resource you definitely created seems to be missing, check the Region selector FIRST before assuming anything was deleted. This single habit prevents the most common beginner support tickets.

Global vs regional view

A small set of services are global and are not tied to any one Region: IAM (users, roles, policies), Route 53 (DNS), CloudFront (the content delivery network), and billing. For these, the Region selector is greyed out or shows “Global” because the data is the same everywhere. Everything else — EC2, S3 buckets, RDS databases, Lambda functions, VPCs — is regional.

You can confirm where your resources live from the CLI. Set your Region with a flag and you will only ever see that Region’s resources.

aws ec2 describe-instances \
  --region us-east-1 \
  --query "Reservations[].Instances[].[InstanceId,State.Name,Placement.AvailabilityZone]" \
  --output table

Output:

-----------------------------------------------------
|                 DescribeInstances                 |
+----------------------+----------+-----------------+
|  i-0a1b2c3d4e5f      |  running |  us-east-1a     |
|  i-0f9e8d7c6b5a      |  stopped |  us-east-1b     |
+----------------------+----------+-----------------+

Run the exact same command with --region eu-west-1 and you will likely get an empty list — proof that the resources are regional, not lost.

aws ec2 describe-instances --region eu-west-1 \
  --query "Reservations[].Instances[].InstanceId" --output text

Output:

To see which Region your CLI defaults to when you omit the flag, check your configuration:

aws configure get region

Output:

us-east-1

CloudShell — a terminal inside the browser

CloudShell is a browser-based terminal you launch from the icon in the top navigation bar. It comes pre-authenticated with your console sign-in, so you can run AWS CLI commands without installing anything or storing credentials on your laptop. It includes the AWS CLI v2, Python, Node.js, and 1 GB of persistent storage in your home directory per Region.

When to use CloudShell: quick commands, trying CLI examples while learning, or working from a machine where you cannot install the CLI.

When NOT to use it: long-running jobs or automation — CloudShell sessions time out after about 20 minutes of inactivity, and the environment is reset after roughly 120 days of no use. For automation, install the CLI locally or use a build pipeline.

To verify which identity CloudShell (or any CLI session) is using, run:

aws sts get-caller-identity

Output:

{
    "UserId": "AIDAEXAMPLE1234567890",
    "Account": "123456789012",
    "Arn": "arn:aws:iam::123456789012:user/dev-jaswinder"
}

Cost note: CloudShell itself is free. You only pay for the AWS resources you create with it. The 1 GB of storage is included at no charge.

Best practices

  • Always glance at the Region selector before creating, searching for, or deleting any resource — make it a reflex.
  • Pin (star) the handful of services you use most so they sit in the top navigation bar.
  • Use the console to learn and to read dashboards, but switch to the CLI or IaC for anything you will repeat.
  • Remember that IAM, Route 53, CloudFront, and billing are global; everything else is regional.
  • Use CloudShell for quick, credential-free commands instead of pasting access keys into a local terminal.
  • Keep a default Region set in your CLI config so console and CLI views stay consistent and you avoid “missing resource” surprises.
Last updated June 15, 2026
Was this helpful?