Topic lessonTopic: AWS Console: context and navigation
AWS Console basics: understand the screen and check your target
The AWS Management Console is a browser-based interface for using AWS services. Before acting, check the account, your current identity or role, and the target service, Region and resource. Use a fictional reporting server to practise reading that context.
Distinguish an account from a user identity or role, check the service, Region and resource, and choose the next check when an expected resource is missing.
For readers new to the AWS Console. You do not need to sign in or have an AWS account. Work only with the illustration and fictional observation notes on this page.
Read your current context before acting
The console provides navigation to services and service-specific screens for viewing or changing resources. Being signed in does not mean that an intended action is permitted. Compare the account and your current identity or role with the task before looking for its target.
An AWS account is a unit for creating and managing AWS resources, with access and billing boundaries. It is different from one person's username. Separate the account that contains resources from the identity of a person accessing them.
Identity information tells you who you are accessing AWS as. AWS Identity and Access Management (IAM) manages access to AWS resources; an IAM role is an identity that an authorized person or workload can assume to use its permissions. A session is the signed-in state in which you are working. Sign-in methods vary. If you are using a role, check which role is currently active too.
- Account → Identity or roleCompare the target account and current identity, including the role if one is in use.
- Identity or role → ServiceCheck that the open service matches the requested task.
- Service → Region scopeCheck what Region selection means for this service.
- Region scope → Target resourceFor a regional resource, match the Region, then compare the resource and list filters.
- Target resource → Next actionAfter identifying the target, choose only an action covered by the task.
- Account
- Which account manages the resources? Compare it with the task, separately from the person's username.
- Identity or role
- Who are you accessing AWS as? If using a role, check its identity; its display name alone does not establish permission.
- Service
- Which service is open, such as EC2? Distinguish similarly named search results.
- Region scope
- Check whether the service manages the resource by Region or uses a different scope.
- Target resource
- Which instance or other resource is the target? Compare identifiers, names and list filters.
- Next action
- Distinguish navigation, reading documentation, launching an execution environment and changing a resource.
Separate the account, identity, service and resource
The example below assumes that you are using a role assigned by the responsible team. Different sign-in methods expose different identity information. When a role is in use, check that role and the target account.
| Term | What it identifies | This example |
|---|---|---|
| AWS account | A unit for resources, access and billing. In a real environment, compare approved account identifiers. | Training account A |
| User identity | Who is accessing AWS; different from the account itself. | The training identity assigned by the responsible team |
| Role | The permission-bearing identity assumed when a role is in use; different from a username or account name. | An invented role named ReportViewer |
| Service | The capability or type of managed resource. | EC2: the service used to inspect the server in this example |
| Region | Where regional resources are managed. Its meaning depends on the service. | The target EC2 resource is in Tokyo |
| Resource | A specific object managed by a service. | One EC2 instance for the reporting app |
A role session uses permissions based on its role. The name ReportViewer does not prove that only read operations are allowed. What actions are permitted depends on the applicable permissions and other controls. A display name or color helps recognition; it is not the permission policy itself.
EC2 instances are regional resources. An instance may be absent from the current list because you are viewing another Region. IAM users and roles are not resources that you find by switching between regional lists like EC2 instances. Check the meaning of the selected scope for each service.
Example: the reporting server is missing from the list
| Item | Requested target | Current view or note |
|---|---|---|
| Account | Training account A | Training account A |
| Role | The team's assigned ReportViewer role | ReportViewer; its detailed permissions are not established by these notes. |
| Service | EC2 instance list | EC2 instance list |
| Region | Tokyo | Osaka |
| Resource | Teaching alias R17; invented display name report-web. | Not found in the current list. |
| List filters | R17's state has not yet been established. | The list shows only running resources. |
The notes establish a Region mismatch and an active list filter. They do not establish that R17 was deleted, is stopped or cannot be viewed because of permissions. A different resource with the same display name is not automatically the requested target.
- Compare the requested account, assigned role, service and resource identifiers with the current view. Do not enter real environment details into this site.
- For this EC2 example, note that the target is Tokyo while the current view is Osaka. Any change of viewing scope in a real environment must follow the organization's instructions and authorized boundaries.
- Check list filters and search conditions. Do not settle on one cause without evidence; distinguish an error from a view that may need refreshing.
- If the target still cannot be identified, or permissions or task boundaries remain unclear, stop and tell the responsible team what you observed and what is unknown. Do not recreate a resource or increase your own permissions.
Choose the next check in three situations
Choose an option to see the result and explanation.
Questions about reading the console
What if the live screen differs from the illustration?
The display can vary with screen width, service and sign-in method. Instead of relying on fixed positions, use the corresponding official guidance to check the account information, current identity or role, viewing scope and destination.
Will searching for a service name find every resource?
A service entry, documentation and an individual resource are different result types. Finding the service is not the same as finding the intended resource. Check the scope and filters, and the Region for a regional resource.
Does the role name ReportViewer mean pressing Stop cannot do anything?
A name alone does not establish which actions are allowed. Do not test permissions by attempting a change such as stopping a resource when your task is only to inspect it. Ask the responsible team about unclear permissions or task boundaries.
Check, then explain in your own words
- Compare the account and current identity with the task. If using a role, check the active role too. Do not infer permissions from its display name.
- Check the service and what Region selection means for it. Match resource identifiers and list filters.
- Distinguish navigation, reading documentation, launching an execution environment and changing a resource. Stop changes when the scope is unclear.
Check your understanding: If the account name and display name report-web match, may you stop that resource?
No. Compare the target account, current identity and role if one is in use, service, applicable Region, resource identifiers and requested action. An inspection-only task does not include stopping the resource.
Matching display names do not establish target identity or permission. Identifying a resource and being authorized to change it are separate checks.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsMultiple search result types, including services, documentation and resources; not a guarantee of exhaustive resource discovery.
Used in this lessonDistinguish service search, list filters and execution Questions about reading the console
Scope and conditionsAccount, organization and billing information access depends on permissions. Distinguish account context from a concrete resource.
Used in this lessonRead your current context before acting Separate the account, identity, service and resource
- Choosing your RegionChecked:
Scope and conditionsRegional resource visibility in many services, with exceptions such as IAM. A Region mismatch alone does not establish that a resource is absent or deleted.
Used in this lessonSeparate the account, identity, service and resource Questions about reading the console
Scope and conditionsRole-session permissions and account context. Display names and colors assist recognition but are not permission policies. No sign-in or switching procedure is executed.
Used in this lessonRead your current context before acting Separate the account, identity, service and resource Questions about reading the console
- What is AWS CloudShell?Checked:
Scope and conditionsA pre-authenticated browser-based shell can send AWS CLI requests. Distinguish shell launch from documentation viewing; no commands or pricing guarantees.
Used in this lessonDistinguish service search, list filters and execution
- Regions and Zones — Amazon EC2Checked:
Scope and conditionsRegion/AZ isolation and placement; EC2 resources are not automatically replicated across Regions. Multi-AZ placement needs application and dependency design.
Used in this lessonSeparate the account, identity, service and resource
- What is an AWS account?Checked:
Scope and conditionsAccount resource, access and billing boundaries; account versus individual identity. No sign-up or account-configuration steps.
Used in this lessonRead your current context before acting Separate the account, identity, service and resource
- IAM rolesChecked:
Scope and conditionsIAM role identity, trust, temporary credentials; role versus session.
Used in this lessonRead your current context before acting Separate the account, identity, service and resource
- Find your Amazon EC2 resourcesChecked:
Scope and conditionsThe fictional EC2 example uses the normal Region-scoped resource list and instance-state filters. Supported operators vary across screens; this is not a guarantee of exhaustive discovery, and Global View is a distinct cross-Region view. No live console operation is performed.
Used in this lessonDistinguish service search, list filters and execution Questions about reading the console