Issues Adding New Users to AWS Quick Sight Enterprise Account

Q&A
, , , ,
1

Hey, just letting you know beforehand I had a chat with ChatGPT that wasn’t helpful but it summarized the question for me, in case you’re wondering why it looks AI generated, so here it goes.

Hello everyone,

I’m facing a challenging issue with my AWS managed Quick Sight (Enterprise Edition) and could use some expert advice.

Issue Summary:

  • User Addition Problem: I’m unable to add new users directly through Quick Sight’s “Manage Users” section. Previously, I would add users to a specific AWS group (let’s call it Quick Sight_Production group from my root AWS account), and they would automatically appear in Quick Sight. This method is no longer functioning. I made no changes to the config or any roles, at all.
  • Access Problems for New Users: Newly added users cannot see the Quick Sight app in their AWS startup apps. They only find a Quick Sight_Production management console without access to Quick Sight.
  • Endless Loading Issue: When new users try to access, they face an indefinite loading screen with the URL “eu-west-1.quicksight.aws.amazon.com/sn/console/get-user-email”.

Troubleshooting Done So Far:

  • Checked IAM and SSO configurations.
  • Verified the inline policy and trust relationships for the Quick Sight-SSO role.
  • Existing users, including myself, can access Quick Sight without issues.

Additional Details:

  • Unable to assign ‘reader’ roles - only ‘admin’ and ‘author’ are available.

I’m puzzled about why I can’t add new users anymore, why they can’t see the app, and why there’s an indefinite loading for them. I would greatly appreciate any insights or guidance on resolving these issues.

Thank you in advance for your help!

2

Hi,

I am not a bot, although the answer is standard for these cases, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!