Skip to Content
Cloud Engineering Academy
1. Cloud Computing & AWS Fundamentals

The AWS Management Console

Sign in through IAM Identity Center, find your way around the console, use CloudShell, and build habits that stop wrong-Region and wrong-account mistakes.

beginnerโฑ 1 h ๐ŸŸข FreeCLF-C02SAA-C03

Assumes: .NET 10 LTS ยท AWS SDK for .NET v4 (AWSSDK.ResourceGroupsTaggingAPI 4.1.x) ยท AWS CLI v2 ยท Region us-east-1. Verified against official sources on 2026-11-17.

Learning objectives

By the end of this lesson you can:

  • Sign in to the console through the IAM Identity Center access portal and confirm which account, role and Region you are using.
  • Navigate with unified search, favourites, recently visited services and Console Home widgets.
  • Explain why some consoles show Global and others a Region, and recognise the classic "my resource has disappeared" Region mistake.
  • Open AWS CloudShell, run CLI commands with your console credentials, and explain what CloudShell keeps and what it throws away.
  • Find every resource tagged Project=cea-lab across Regions with Tag Editor, the CLI and C#.
  • Configure unified settings (default Region, language, visual mode) and turn on multi-session support safely.

Prerequisites

  • IAM fundamentals โ€” you know what a role session is
  • Secure your AWS account โ€” Identity Center user, SandboxAdmin permission set and the access portal URL
  • A modern browser. The C# section needs the .NET 10 SDK and the learn-sandbox profile

Why this matters in banking

A Harbourline Bank engineer is asked at 07:30 to check why a payments queue is backing up. They open the console, go to SQS, and see no queues at all. Panic follows: has someone deleted production? Ten minutes and a major-incident bridge later, someone notices the Region selector says US East (Ohio) instead of Europe (London). Nothing was deleted.

The opposite mistake is worse: an engineer believes they are in the non-production account and deletes a stack โ€” but the browser tab was signed in to production. Banks lose hours, and sometimes customer-facing service, to these two errors. The console is where most people first touch AWS, and the habits you build in it โ€” check account, check role, check Region, before every change โ€” are the same habits auditors expect to see in change records.

The idea in plain language

The AWS Management Console is the web interface to AWS. Every button you click becomes an API call, signed with the temporary credentials of your role session, and checked by IAM exactly like a CLI or SDK call. The console is not a different, more powerful door: it has the same permissions as your role.

Three things are always in play:

  1. Account โ€” which AWS account you are signed in to (shown in the top-right account menu).
  2. Identity โ€” which role (permission set) you are using, for example SandboxAdmin.
  3. Region โ€” which AWS Region the regional consoles show and create resources in (top-right Region selector).

Analogy: The console is the bank's branch counter terminal. Your badge decides what you can do (identity), the terminal is logged in to one branch's ledger (account), and a dial on the side chooses which city's vault you are looking at (Region). If you turn the dial to the wrong city, the vault looks empty โ€” not because it was robbed, but because you are looking in the wrong building.

What problem the AWS service solves

The console lets you discover, explore and learn AWS visually, inspect resources during incidents, read dashboards and billing, and perform rare one-off tasks. It also hosts CloudShell, a browser terminal already signed in as you.

Honest limitations:

  • Not repeatable. Clicks leave no reviewable artefact. Banks treat production console changes as exceptions ("click-ops"); routine changes go through IaC and pipelines (Modules 9 and 10).
  • Regional views. Most service consoles show one Region at a time. Resources elsewhere are invisible until you switch.
  • UI changes often. Menu labels move. This course describes navigation in text and verifies it on the date at the top; if a label differs, use unified search.
  • Session-bound. Your console session ends when the permission set's session duration expires (4 hours for SandboxAdmin in this course).

What is free: the console itself, Console Home, unified search, Resource Groups and Tag Editor, the AWS Health Dashboard, and CloudShell (no charge for the shell; you pay only for AWS resources you create from it).

Microsoft / Azure comparison

You know (Microsoft/Azure)AWS equivalentWhat's different
Azure PortalAWS Management ConsoleThe Azure portal can show resources from all regions in one blade; most AWS consoles are per-Region
Directory + subscription switcherAccess portal (choose account and role) + multi-sessionIn AWS you pick account and role together; each is a separate session
Portal search barUnified search (Alt+S on Windows)Searches services, features, documentation and Marketplace
Azure Cloud ShellAWS CloudShellBoth are free browser shells; AWS gives 1 GB persistent home per Region, Azure uses a file share in your storage account
Resource groups as the main containerTags + Resource Groups + Tag EditorNothing forces a container in AWS; tag discipline is how you find things
Azure Resource Graph ExplorerTag Editor, Resource Groups Tagging API, AWS Resource ExplorerTag Editor can search several Regions in one query
Azure Service HealthAWS Health DashboardShows AWS events that affect your account, plus public service status
Portal settings (default directory, language)Unified Settings (default Region, language, visual mode)AWS stores your settings, favourites and recently visited list in every Region so they follow you; you can reset them and opt out of remembering recently visited services

Architecture

Security-boundary view: the trust boundary is your role session. The console, CloudShell, CLI and SDK all present the same temporary credentials, so they all have exactly the same permissions and all their calls are logged in CloudTrail under the same session name (your Identity Center username). CloudShell runs in an AWS-managed environment with outbound internet access, so data you copy into it can leave AWS โ€” administrators can deny CloudShell with IAM if that is a concern.

Step-by-step implementation

Sign in through the access portal

Open your AWS access portal URL (from Module 0, it looks like https://d-1234567890.awsapps.com/start). Sign in with your Identity Center username, password and MFA. On the Accounts tab, expand cea-sandbox, then choose SandboxAdmin (the role name link opens the console). Bookmark the portal URL, not a console URL: the portal is how you choose the account and role.

Confirm who and where you are

Open the account menu (top right). It shows the role and username (for example AWSReservedSSO_SandboxAdmin_โ€ฆ/alex.learner) and the account ID. Compare the account ID with the one you wrote down in Module 0. Then look at the Region selector next to it: it should say United States (N. Virginia) or similar for us-east-1.

Make this a ritual: account, role, Region before every change.

Set your defaults with unified settings

Account menu โ†’ Settings (Unified Settings). Set Default Region to US East (N. Virginia) us-east-1, choose your language, and pick a visual mode (light/dark). The default Region is what the console opens with when a URL does not specify one.

A detail that data-protection teams notice: AWS documents that these console preferences (settings, favourites, recently visited services) are stored in all Regions, including opt-in Regions, so they follow you everywhere. They contain no customer data, but if your organisation objects you can Reset all and opt out of remembering recently visited services.

  • Press Alt+S to focus unified search, type s3, press Enter. Search also finds features ("bucket policy") and documentation.
  • In the Services menu or search results, choose the star next to S3, IAM, CloudShell, Billing and Cost Management, and Resource Groups & Tag Editor. Favourites appear in the navigation bar.
  • Console Home (the AWS logo) shows widgets such as Recently visited, Cost and usage, AWS Health and Welcome to AWS. Rearrange them or add widgets with Add widgets.

Feel the global vs regional difference

  1. Open IAM. The Region selector shows Global: IAM has one control plane for the whole account.
  2. Open S3. The bucket list can show buckets from every Region, with a Region column โ€” but each bucket lives in one Region, and creating a bucket asks you which.
  3. Open SQS or Lambda in us-east-1, then switch the Region selector to Europe (London) eu-west-2. The list is different (probably empty). Switch to Europe (Frankfurt) eu-central-1: the Region guardrail SCP from Module 0 should now produce access-denied banners.

Open CloudShell

Choose the CloudShell icon in the navigation bar (or search "CloudShell"). It opens in the currently selected Region with your role's credentials already loaded. Run the commands in the AWS CLI section. Use Actions โ†’ Upload file / Download file to move small files; anything you save under $HOME survives the session.

Find everything tagged for this course

Search Tag Editor (part of Resource Groups & Tag Editor). Choose Regions us-east-1 and eu-west-2, Resource types = All supported resource types, Tags key Project value cea-lab, then Search resources. If you have not run any lab yet the list is empty โ€” which is exactly the state you want after every teardown. You can Export the results to CSV for your notes.

Check AWS Health and billing

Search Health to open the AWS Health Dashboard: Your account health lists events and scheduled changes that affect your resources. Then switch to your BillingViewer permission set (or open a second session โ€” next step) and search Billing and Cost Management to see month-to-date charges. In the sandbox account with SandboxAdmin you may see an access-denied page: billing for an Organization is consolidated in the management account.

(Optional) Turn on multi-session

Account menu โ†’ Turn on multi-session. You can then be signed in to up to five identities in one browser โ€” for example SandboxAdmin in the sandbox and BillingViewer in the management account. Console URLs gain an account-specific prefix, so the tab's address bar also tells you which session you are in. Give each session a distinct colour or name where the console offers it, and close sessions you no longer need.

AWS Console instructions

Summary of navigation used in this lesson (text only; labels checked 2026-11-17):

TaskNavigation
Choose account and roleAccess portal โ†’ Accounts โ†’ expand the account โ†’ role name
See account ID, role, sign outNavigation bar โ†’ account menu (top right)
Default Region, language, visual modeAccount menu โ†’ Settings (Unified Settings)
Change RegionNavigation bar โ†’ Region selector
SearchNavigation bar search box, or Alt+S (Option+S on macOS)
FavouritesStar icon next to a service in the Services menu or search results
CloudShellNavigation bar โ†’ CloudShell icon; inside it, Actions for upload, download, restart and delete
Find tagged resourcesSearch Tag Editor โ†’ Regions, resource types, tags โ†’ Search resources
Resource groupsResource Groups & Tag Editor โ†’ Create resource group โ†’ Tag based
AWS HealthSearch Health โ†’ AWS Health Dashboard โ†’ Your account health
Multi-sessionAccount menu โ†’ Turn on multi-session

About myApplications: Console Home has a myApplications area for grouping resources into applications with cost and security views. AWS documentation now says myApplications no longer allows creating new applications and points to AWS Resource Groups instead, so this course uses tag-based Resource Groups.

About Console-to-Code: AWS launched Console-to-Code (record console actions, generate CLI/CloudFormation/CDK) in 2024 as part of Amazon Q Developer. Amazon Q Developer stopped accepting new sign-ups on 2026-05-15, so do not plan on this feature in a new account โš  VERIFY. This course teaches IaC directly instead (Module 10).

AWS CLI

Run these in CloudShell (bash). They use your console session's credentials โ€” no profile needed, and no keys stored anywhere.

# Who am I? Shows the assumed-role ARN of your Identity Center session.
aws sts get-caller-identity

# Which Region is CloudShell using? CloudShell sets AWS_REGION to the console's Region.
echo "$AWS_REGION"

# List resources tagged Project=cea-lab in the CURRENT Region (this API is regional).
aws resourcegroupstaggingapi get-resources \
  --tag-filters Key=Project,Values=cea-lab \
  --query "ResourceTagMappingList[].ResourceARN" --output text

# Same query in London, to prove the per-Region behaviour.
aws resourcegroupstaggingapi get-resources \
  --tag-filters Key=Project,Values=cea-lab \
  --region eu-west-2 \
  --query "ResourceTagMappingList[].ResourceARN" --output text

# Loop over both course Regions and print a count per Region.
for r in us-east-1 eu-west-2; do
  n=$(aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab \
        --region "$r" --query "length(ResourceTagMappingList)" --output text)
  echo "$r: $n resource(s) tagged Project=cea-lab"
done

# How much persistent storage is left in this Region's home directory (1 GB per Region).
df -h "$HOME"

From your Windows terminal the same checks need the profile:

aws sts get-caller-identity --profile learn-sandbox
aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab --region us-east-1 --profile learn-sandbox

Line notes:

  • get-resources only returns resources that have been tagged at some point and that the tagging API supports; it is a good check, not a perfect one. Untagged leftovers are why the lab teardown also uses service-specific checks.
  • --query "length(...)" is a JMESPath expression (CLI with SSO profiles covers JMESPath).
  • CloudShell's credentials come from the console session and expire with it; you never run aws configure there.

Infrastructure as Code

The console itself has no IaC equivalent, but the "find my course resources" view does: a tag-based resource group that always shows everything tagged Project=cea-lab in a Region. It is free.

resource-group.tf
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 6.0"
    }
  }
}

provider "aws" {
  region  = "us-east-1"
  profile = "learn-sandbox"
}

resource "aws_resourcegroups_group" "cea_lab" {
  name        = "hl-m01-cea-lab-resources"
  description = "Everything tagged Project=cea-lab in this Region"

  resource_query {
    query = jsonencode({
      ResourceTypeFilters = ["AWS::AllSupported"]
      TagFilters = [
        { Key = "Project", Values = ["cea-lab"] }
      ]
    })
  }

  tags = {
    Project     = "cea-lab"
    Lab         = "m01-hello-aws"
    Environment = "learn"
    Owner       = "alex"
  }
}

After deploying, open Resource Groups & Tag Editor โ†’ Saved resource groups โ†’ hl-m01-cea-lab-resources. The group itself carries the course tags, so it lists itself โ€” a useful reminder to delete it at the end of the course.

Complete code

Tag Editor and get-resources work one Region at a time per call. This small console app checks every Region you list and prints anything tagged for the course โ€” the same check the lab's teardown section asks you to run, but scriptable.

Program.cs
// dotnet new console -n Harbourline.TagSweep -f net10.0
// dotnet add package AWSSDK.ResourceGroupsTaggingAPI --version 4.1.0.2
// dotnet add package AWSSDK.SSO --version 4.1.0.2
// dotnet add package AWSSDK.SSOOIDC --version 4.1.0.2
using Amazon;
using Amazon.ResourceGroupsTaggingAPI;
using Amazon.ResourceGroupsTaggingAPI.Model;
using Amazon.Runtime.CredentialManagement;

string[] regions = args.Length > 0 ? args : ["us-east-1", "eu-west-2"];
const string profileName = "learn-sandbox";

var chain = new CredentialProfileStoreChain();
if (!chain.TryGetAWSCredentials(profileName, out var credentials))
{
    Console.Error.WriteLine($"Profile '{profileName}' not found. Run: aws configure sso");
    return 2;
}

var total = 0;
foreach (var regionName in regions)
{
    using var tagging = new AmazonResourceGroupsTaggingAPIClient(
        credentials, RegionEndpoint.GetBySystemName(regionName));

    var request = new GetResourcesRequest
    {
        TagFilters = [new TagFilter { Key = "Project", Values = ["cea-lab"] }],
    };

    do
    {
        var page = await tagging.GetResourcesAsync(request);
        foreach (var mapping in page.ResourceTagMappingList ?? [])
        {
            var lab = mapping.Tags?.FirstOrDefault(t => t.Key == "Lab")?.Value ?? "(no Lab tag)";
            Console.WriteLine($"{regionName,-12} {lab,-16} {mapping.ResourceARN}");
            total++;
        }
        request.PaginationToken = page.PaginationToken;
    }
    while (!string.IsNullOrEmpty(request.PaginationToken));
}

Console.WriteLine(total == 0
    ? "Nothing tagged Project=cea-lab found. Clean."
    : $"{total} resource(s) still tagged Project=cea-lab. Tear them down.");
return total == 0 ? 0 : 1;

Run it after aws sso login --profile learn-sandbox with dotnet run or dotnet run -- us-east-1 eu-west-2 eu-central-1. Expect access-denied errors for Regions blocked by your SCP; that is the guardrail working.

Code explained line by line

  1. string[] regions = args.Length > 0 ? args : [...] โ€” Regions to sweep; defaults to the two the course SCP allows.
  2. CredentialProfileStoreChain().TryGetAWSCredentials(...) โ€” loads the learn-sandbox SSO profile from %USERPROFILE%\.aws\config. Without the AWSSDK.SSO and AWSSDK.SSOOIDC packages this fails at runtime, not at compile time.
  3. new AmazonResourceGroupsTaggingAPIClient(credentials, RegionEndpoint.GetBySystemName(regionName)) โ€” one client per Region, because the tagging API is regional, just like most console pages.
  4. TagFilters = [new TagFilter { Key = "Project", Values = ["cea-lab"] }] โ€” the same filter you typed into Tag Editor.
  5. The do โ€ฆ while loop โ€” the API returns results in pages; PaginationToken is empty on the last page.
  6. page.ResourceTagMappingList ?? [] and mapping.Tags? โ€” SDK for .NET v4 returns null for empty collections.
  7. Exit code 1 when anything is found โ€” handy for a scheduled "did I forget to tear down?" check.

Security considerations

  • Always enter through the access portal, never through root. Root sign-in should be rare and recorded (Module 0).
  • Check account, role and Region before every change. In banks, change records often require the account ID and Region to be written down before work starts.
  • Prefer read-only roles for looking. Use a read-only permission set for investigation; switch to a write role only for an approved change. Multi-session makes this easy.
  • CloudShell has internet access and sudo. Treat it like a laptop: no customer data, no secrets in $HOME. Organisations can deny cloudshell:* with IAM or an SCP where policy requires.
  • Console actions are logged. Every click is a CloudTrail event with your session name โ€” useful evidence, and a reason not to "just try something" in shared accounts.
  • Do not paste temporary credentials from the access portal's "Access keys" panel into files or chat; use aws sso login instead.

โš  Learning shortcut โ€” not for production

In this course you use the console with SandboxAdmin to explore and sometimes to create resources. In a bank, production accounts are usually read-only in the console for engineers; changes go through IaC and pipelines with peer review, and console write access is a break-glass permission set with an approval step and an alarm. Treat every console change you make here as practice for writing the IaC version.

โš  Learning shortcut โ€” not for production

CloudShell is convenient for running quick commands. In regulated environments its use may be restricted or limited to VPC environments without internet access, because it is an outbound path for data. Check your organisation's rules before relying on it at work.

Banking use case

Harbourline Bank's platform team publishes a short "console etiquette" standard:

  • Console bookmarks point only to the Identity Center access portal.
  • Production permission sets for engineers are read-only; the ProdBreakGlass permission set has a 1-hour session, requires a ticket number in the session name and raises an alert.
  • Engineers enable multi-session and keep production in a separate browser profile with a distinct theme colour.
  • Every resource must carry CostCentre, Application, Environment and DataClassification tags; a tag-based resource group per application gives on-call staff one page to start from.
  • Before closing a change, the engineer attaches a Tag Editor export (or the tag-sweep output) showing that temporary resources were removed.

Whether this satisfies the bank's change-management policy or the regulator's expectations is for the bank's risk and audit functions to decide; the console features only support the process.

Common mistakes

  • Wrong Region โ†’ the console remembers the last Region per service, or a shared link contains ?region= โ†’ resources "disappear" or get created in the wrong place. Read the Region selector before every create.
  • Wrong account โ†’ several tabs signed in to different accounts โ†’ destructive change in production. Use multi-session labels, separate browser profiles and read-only roles.
  • Bookmarking deep console URLs โ†’ they carry a Region and, with multi-session, an account prefix โ†’ you land in the wrong context. Bookmark the access portal.
  • Treating CloudShell as permanent โ†’ software installed with sudo dnf install is gone next session โ†’ keep scripts in $HOME, which persists; reinstall tools from a script.
  • Leaving CloudShell data in an unused Region โ†’ it is deleted after 120 days without a session in that Region โ†’ keep anything important in Git.
  • Expecting Tag Editor to find untagged leftovers โ†’ it filters on tags โ†’ also check service consoles in each Region (EC2, NAT gateways, Elastic IPs) as listed in Cost guardrails.

Troubleshooting

SymptomLikely causeFix
A service console is empty though you created resourcesWrong RegionSwitch the Region selector; check the resource's ARN for its Region
Red banner "You are not authorized to performโ€ฆ" in eu-central-1Region guardrail SCP (working as intended)Switch to us-east-1 or eu-west-2
Billing pages show access deniedYou are in the sandbox account, or IAM access to billing is not activatedUse BillingViewer in the management account; activate IAM access to billing as root once (Module 0)
Console suddenly asks you to sign in againPermission-set session expired (4 h)Sign in again from the access portal
CloudShell: "Failed to open sessions: Timed out while opening the session"A proxy or firewall blocks WebSocketsTry another network, or ask the network team to allow WebSockets to ssmmessages endpoints
CloudShell cannot start: monthly usage quotaPer-Region monthly usage quota reachedUse another allowed Region or request an increase in Service Quotas
CloudShell session closed on its own20โ€“30 minutes without keyboard/pointer activity, or about 12 hours continuousReopen; keep long jobs out of CloudShell
Tag Editor finds nothing although resources existWrong Regions selected, tag key/value case differs, or the resource type is not supportedSelect all relevant Regions; tag search is case-sensitive; check the supported-resources list
Multi-session: a sixth sign-in is refusedUp to five sessions per browserSign out of a session you no longer need

Cost and cleanup

Cost: $0. The console, unified search, Console Home, Resource Groups, Tag Editor, the AWS Health Dashboard and CloudShell (including its 1 GB per-Region home directory) have no charge. Anything you create from CloudShell is billed normally.

Cleanup:

# If you deployed the optional resource group with the CLI or IaC, delete it.
aws resource-groups delete-group --group hl-m01-cea-lab-resources --region us-east-1

# Optional: remove files you uploaded to CloudShell's home directory in this Region.
ls -la "$HOME"

Terraform users run terraform destroy; CDK users run cdk destroy. To reset CloudShell completely in a Region, use Actions โ†’ Delete (this deletes the home directory in that Region and cannot be undone). Finally, run the Tag Editor search once more and confirm it returns nothing.

Exercises

  • ๐ŸŸข Guided: Sign in through the access portal, set your default Region to us-east-1, star five services, open CloudShell and run aws sts get-caller-identity and the two-Region tag sweep loop. Write down the session name shown in the ARN.
  • ๐ŸŸก Challenge: Create a tag-based resource group named hl-m01-cea-lab-resources in the console (not with IaC). Then create any one small tagged resource of your choice (for example an empty SQS queue with the four course tags), confirm it appears in the group, Tag Editor and the C# sweep, and delete everything.
  • ๐Ÿ”ด Live problem: A colleague in the Harbourline payments team sends: "The hl-m04-accounts-api Lambda is gone from the console. I'm in the right account โ€” I checked. Did someone delete it?" List what you would check and in which order, without assuming deletion.

Assignment

Write a one-page "console safety checklist" for your learning-journal repository (docs/console-checklist.md): how you sign in, how you confirm account/role/Region, which permission set you use for what, how you use multi-session, and how you prove that nothing tagged Project=cea-lab remains. Add the C# tag-sweep program under tools/tag-sweep/ and include a sample of its output.

Solutions

Knowledge check

Interview questions

  • "How do you avoid making a change in the wrong environment?" โ€” Separate accounts per environment, Identity Center sign-in with read-only roles by default, a visible account/Region check before changes, multi-session or separate browser profiles, and IaC with pipelines for real changes so the target account is in code.
  • "When is using the console acceptable in production?" โ€” For read-only investigation, dashboards and break-glass emergencies with an audit trail. Routine changes belong in IaC and pipelines.
  • "What is CloudShell and when would you not use it?" โ€” A free, pre-authenticated browser shell with AWS tools and 1 GB persistent home per Region. Avoid it for long-running jobs, for handling sensitive data, or where policy forbids an outbound internet path.

Certification practice

Completion checklist

  • I sign in only through the access portal and can state my account, role and Region at any moment
  • My default Region is us-east-1 and my most-used services are starred
  • I ran aws sts get-caller-identity and the tag sweep in CloudShell
  • I can explain global vs regional consoles and the 120-day CloudShell retention rule
  • Tag Editor (or the C# sweep) shows nothing tagged Project=cea-lab, and I deleted any resource group I created

Key takeaways

  • The console is just another API client: same role, same permissions, same CloudTrail record.
  • Account, role, Region โ€” check all three before every change.
  • Most consoles are regional; IAM, Organizations, Route 53, CloudFront and billing are global.
  • CloudShell is free, pre-authenticated, Region-scoped and keeps 1 GB of $HOME per Region (deleted after 120 days of non-use).
  • Tags plus Tag Editor, resource groups or the tagging API are how you find โ€” and prove you removed โ€” your resources.

Further reading

Independent learning resource โ€” not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page