- Newest
- Most votes
- Most comments
The issue you're experiencing is a common one when setting up IAM Identity Center (formerly known as AWS Single Sign-On) in a new AWS account. The loop of warnings and redirects you're encountering is due to the interdependence between IAM Identity Center and AWS Organizations.
To resolve this issue, you should follow these steps:
-
First, ensure that you have set up AWS Organizations. If you haven't already done so, you need to create an organization from your AWS account, which will become the management account.
-
Once AWS Organizations is set up, go to the IAM Identity Center console.
-
In the IAM Identity Center console, look for an option to "Enable IAM Identity Center" or "Enable Identity Center". Click on this option to begin the setup process.
-
During the setup, AWS will automatically create an organization for you if one doesn't exist, or use your existing organization.
-
You may need to verify your email address associated with the management account. AWS Organizations will send a verification email, which you should respond to within 24 hours.
-
If you encounter a "rate exceeded" error, wait for a longer period (30 minutes to an hour) before trying again. These errors can occur due to AWS's internal processes and usually resolve themselves given some time.
-
If you're still having trouble, you might need to delete your existing IAM Identity Center configuration (if any) and start over. You can do this by going to IAM Identity Center > Settings > Management and deleting the existing configuration.
-
After deletion, create an AWS Organization (if not already done), then re-enable IAM Identity Center.
Remember, IAM Identity Center should be enabled in the management account of your AWS Organization. This setup allows you to centrally manage access across multiple accounts and is indeed considered a best practice for multi-account environments.
If you continue to experience issues after following these steps, it may be worth contacting AWS Support for further assistance, as there could be account-specific factors at play.
Sources
IAM Identity Center cannot be enabled | AWS re:Post
I can't enable IAM Identity Center service | AWS re:Post
Cannot add permissions in IAM Identity Center | AWS re:Post
Solved.
I had a single management account under a "root" organization, and I deleted the organization, then was able to go to Identity Manager in the console and the Enable Identity Manger did work.
This is a new configuration / new account setup (totally new: new credit card, email, etc. vs new Organization or Account resource in an existing setup) so I was not very worried about deleting.
note: going forward, I will use Terraform .tf for pretty much everything to simplify rebuilding if I again get into a bad state where AWS advice and procedures no longer work.
I believe the earlier attempt that reported Rate Error caused a partial configuration to be left in place. Deleting and trying again solved it. I had set up an authorization group and a couple things, which probably put me over the limit halfway through the Identity Center setup. Unsure.
answered 2 years ago
Relevant content
asked 4 years ago
asked 2 years ago
- AWS OFFICIALUpdated a year ago
