I configured quicksight via aws organization users that has admin access.
I accidentaly delted the association between admin IAM group to admin group in quicksight. As result I’m now locked out from quicksight.
Is there any way to restore this access (e.g. with root?)? or I need to completely delete and recreate the subscription?
if the access is lost, how can I delete the current subscription and create a new one?
Hello @Emiliano1
Welcome to Quick Sight Community!!
From root/admin access in AWS console, you can try clicking on Quick Sight, you might get a landing page like this:
From here, you can go to “Manage users” → “Manage role groups”
Here you can associate your existing groups for required roles
Please note, you might need Admin/root access from AWS console, then you can add additional groups.
Hope this helps!!
Hi, thank you for the answer. I lost my access because I manually removed the admin group from the page that you displayed. Anyway I fixed it updating the permission in IAM Identity Center, it foced a re-sycn of the group in quicksight, then I was able to access again.
I have another issue. I’m an admin in both quicksight and IAM identity center, I created a datasource. Another admin seems not able to use my datasource (it say contact administrator). Is this possible?
Note I shared the datasource with the entire admin group.
Any help will be appreciated.
Kind Regards,
Emiliano
Hello @Emiliano1, what data source are you using in Quick Sight? Maybe something else related to admin permissions was messed up in the process and the users have lost access to creating datasets or viewing the data source. Do you have a policy in the IAM identity center for the admin users that are not root users? Or possibly you need to create one now to provide them with the permissions they need.
Hello @Emiliano1
Are you still working on this issue or were you able to find a solution?
Also, were you able to look into the @DylanM’s suggestions above?
Hey @Emiliano1
This topic is being archived because it has been some time since we have heard from you. If you still need help with this issue or have a new issue, please feel free to post a new topic at the top of the community.