for you AWS folks out there who use multiple accou...
# general
a
Nice.
Don’t you use the account switcher?
Like….
<http://mycompany.awsapps.com|mycompany.awsapps.com>
I have all my accounts on that page, not sure if it’s new or what.
s
the built-in AWS switcher is not that great. #1, it doesn’t sync across computers (it’s cookie based) #2, it’s limited to 5 accounts max before it removes the oldest one
you also can’t remove accounts either
a
Yeah.
In my previous jobs always used 1 account for all, now that we have 3 or 4 it gets more complicated.
We actually have SSO, and I think the roles work differently.
s
ahh yeah
a
That’s why I use that home page in
<http://awsapps.com|awsapps.com>
.
t
I highly recommend setting up AWS SSO (even if you already have a different sso provider). I use that to switch between accounts
a
But where do you do the switch? from where I mean.
s
what does that experience look like? yeah, I was wondering the same
a
This is the experience that I use.
s
is that the AWS SSO switcher?
a
But not sure if there are other ways, I didn’t setup SSO, was other person.
I think so.
We use SSO with our Microsoft 365. accounts.
And I get to that page entering to “mycompany.awsapps.com
But not sure if there are better ways, the bad thing about this is you can only have 1 account open, you can’t open 2 sessions at the same time.
Sometimes I want to compare resources from DEV / STAGE, and I can’t easily.
a
Agreed, can fully recommend AWS SSO. We followed these instructions for G Suite and it worked the first try. Combined with Control Tower it allows us to easily vend developer AWS accounts and assign groups to each AWS account. E.g. the owner of the developer account has full admin privileges, but every developer has read-only access to all personal accounts as well. This works for the CLI as well, although you do need to reauthenticate every 30-2 hours (depending on session duration). And using something like ssocred allows you to use legacy AWS CLI tooling that doesn't support reading SSO temporary credentials. The one downside as Adrian mentions is that you can only be logged into 1 account.
j
To get around the limitation of only being able to log into a single account, what has worked well for us is setting up a new chrome profile for each of the accounts (I am not sure if there is a configuration setting in AWS SSO that may prevent it in some cases). In each profile, log into AWS SSO, and you should then be able to log into one account per chrome profile simultaneously. The new chrome profiles also have a nice set of default colors you can set so you can distinguish your different environments.