3 ms·
Some advice that may help: * Visit the console directly from another region's URL (e.g., https://us-east-2.console.aws.amazon.com/console/home?region=us-east-2
by bilalq 5y ago
Some advice that may help:
* Visit the console directly from another region's URL (e.g., https://us-east-2.console.aws.amazon.com/console/home?region=us-east-2 https://us-east-2.console.aws.amazon.com/console/home?region...). You can try this after you've successfully signed in but see the console failing to load as well.
* If your AWS SSO app is hosted in a region other than us-east-1, you're probably fine to continue signing in with other accounts/roles.
Of course, if all your stuff is in us-east-1, you're out of luck.
EDIT: Removed incorrect advice about running AWS SSO in multiple regions.
- binaryblitz 5y agoI don't think you can run SSO in multiple regions on the same AWS account.
- bilalq 5y agoThanks, corrected.
- staticassertion 5y ago> Might also be a good idea to run AWS SSO in multiple regions if you're not already doing so. Is this possible? > AWS Organizations only supports one AWS SSO Region at a time. If you want to make AWS SSO available in a different Region, you must first delete your current AWS SSO configuration. Switching to a different Region also changes the URL for the user portal. [0] This seems to indicate you can only have one region. [0] https://docs.aws.amazon.com/singlesignon/latest/userguide/regions.html https://docs.aws.amazon.com/singlesignon/latest/userguide/re...
- bilalq 5y agoGood call. I just assumed you could for some reason. I guess the fallback is to devise your own SSO implementation using STS in another region if needed.