Check your context first
Before changing a resource, confirm the account and role you are using. Then check the selected Region. These small checks prevent confusion when similar resources exist in multiple environments.
If a resource appears to be missing, check its Region and your permissions before creating another copy. Some services have global views while others show regional resources.
Learn a repeatable navigation habit
Use service search to open the relevant service, then locate its resource list. Read names, identifiers and status before opening an action menu. Console labels can change over time.
Create a short lab note containing the service, Region, resource identifier and purpose. Avoid storing passwords or access keys in that note.
Read before applying a change
Creating or modifying resources can affect access, availability and cost. Review the proposed configuration and use a separate learning environment where practical.
After a lab, revisit the resource lists and check what is still running. Closing the browser does not stop cloud resources.
Try it yourself
Without creating anything, find the Region selector, open EC2 and identify the instance list. Write down how you would confirm the account and Region before a future lab.
A common question
Does signing out stop my resources?
No. Signing out ends your console session. Running resources continue until stopped, deleted or otherwise managed.
References & video notes
An original CloudFolks companion guide to the topic. Older video interfaces and offers may differ from current services. Use the current documentation for implementation details.
Keep learning
- Public, private and hybrid cloud explained
- IaaS vs PaaS vs SaaS: who manages what?
- AWS Regions and Availability Zones explained