Select Language:
If you’re using QuickSight and hit an error when trying to access Manage account → AWS resources, saying something like “Something went wrong. For more information see Set IAM policy,” here’s a simple way to fix it.
First, make sure your IAM user has the necessary permissions. Even if you already assigned permissions following AWS’s official guides, sometimes the issue persists. This can be frustrating, especially when none of the recommended permissions seem to fix the problem.
One common fix is to delete the QuickSight service role named aws-quicksight-service-role-v0. After deleting this role, reopen the AWS resources page in QuickSight. The idea is that QuickSight will automatically recreate the role, resolving permission issues.
However, if this doesn’t happen, don’t worry. Sometimes the role might not get recreated on its own. Here’s what you can do:
- Log into the AWS Management Console with your administrator account.
- Navigate to the IAM service.
- Check if the role aws-quicksight-service-role-v0 exists.
- If it’s missing, manually create a new IAM role with the same name.
- Attach the necessary permissions to this role. You can find the correct permissions in the AWS documentation linked in the instructions.
Also, double-check some key points:
- Ensure your IAM user has AdministratorAccess or equivalent permissions.
- Confirm that no unauthorized API calls are blocked; you can review CloudTrail logs if needed.
- Make sure you’re working in the correct AWS region, like eu-west-2 in this case.
If you’ve tried all these steps and still face issues, consider reaching out to AWS Support or checking for recent updates or known outages. Sometimes, these problems are temporary and related to backend service updates.
This approach should help you resolve the error and regain access to AWS resources from QuickSight.
ChatGPT
Perplexity
Gemini AI
Grok AI
