I am setting up an account for a small organization and I decided to isolate the master account and create an admin IAM user. I set up the database and follow the tutorial to create an admin IAM user. I log in to the admin account later to verify everything looks good and don't see any services including the RDS instance. I go through the pain of verifying all of the details in the tutorials and more.
Turns out my console was just on a different region then the master account's console.
Seems like there ought to be either 1) a console view of all resources (across all regions so a true all resources view) OR 2) an ability to set a default console region.
Either of these would enable one to have a bit more sanity during management of their setup.
If you signed up for an AWS account on or after May 17, 2017, the default Region when you access a resource from the AWS Management Console is US East (Ohio) (us-east-2); for older accounts, the default Region is either US West (Oregon) (us-west-2) or US East (N. Virginia) (us-east-1).
For most commands, the AWS CLI automatically determines the URL based on the selected service and the specified AWS Region. However, some commands require that you specify an account-specific URL.
The Default region name identifies the AWS Region whose servers you want to send your requests to by default. This is typically the Region closest to you, but it can be any Region. For example, you can type us-west-2 to use US West (Oregon).
Amazon EC2 is hosted in multiple locations world-wide. These locations are composed of AWS Regions, Availability Zones, Local Zones, AWS Outposts, and Wavelength Zones. Each Region is a separate geographic area. Availability Zones are multiple, isolated locations within each Region.
Sign in to the AWS Management Console. In the upper right corner of the console, choose your account name or number and then choose My Account . In the AWS Regions section, next to the name of the Region that you want to enable, choose Enable . In the dialog box, review the informational text and choose Enable Region .
In the Cloud Console, go to the Settings page. From the Region drop-down menu, select a default region. From the Zone drop-down menu, select a default zone. Click Save.
Some services, such as AWS Identity and Access Management (IAM), do not have Regional resources. You can use policy conditions to control access to AWS services in an AWS Region.
About AWS Regions. An AWS Region is a collection of AWS resources in a geographic area. Each AWS Region is isolated and independent of the other Regions. The resources that you create in one Region do not exist in any other Region unless you explicitly use a replication feature offered by an AWS service.
tl;dr: No. If you've logged into an account before, your browser caches the last region you were in for each service.
When you login to a new account the region isn't cached so it usually (service dependent) loads the us-east-1 / us-west-2 page.
+1000 for being able to set up a default console region either in the account, or in the AWS Organization for each sub-account/OU/the whole organization.
You can do it in the CLI, so why not the console? Seems like an easy feature add.
There's an old doc on it here: https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/console-help-gsg.pdf
Edit: This isn't just an issue for newbies, it would save a lot of mini heart attacks when people log in to an account and think they're missing resources, only to find out they're in the wrong region!
According to the recent announcement by AWS, it is now possible to have a preferred/default region set. Read more here: https://aws.amazon.com/about-aws/whats-new/2022/04/unified-settings-aws-management-console/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With