Not seeing permission called "quicksight:SearchUsers"

Question & Answer
1

Hello,

I’m trying to use the new manage assets functionality in QuickSight. I am an admin within QuickSight but not within our AWS account as a whole.

When I try to search for a user or group to share resources with I get kicked the following error:

image
image1435×97 7.32 KB

I had this error for permissions quicksight:SearchUsers and quicksight:SearchGroups

My AWS admin was able to add the SearchGroups permissions but did not see the SearchUsers permission listed. I also confirmed this on a personal account.

Here is the search results in IAM when trying to assign a policy:
image

I then tried to manually edit the permission incase it just wasn’t listed through the self-help tool but that did not work either:
image

Is this permission by chance under some other name?

2

@divey, please work with your account admin to create a policy such as below and let me know if that helped to address your issue.

{
“Version”
:
“2012-10-17”
,
“Statement”
:
[
{
“Effect”
:
“Allow”
,
“Action”
:
[
“quicksight:SearchGroups”
,
“quicksight:SearchUsers”,
“quicksight:ListUsers”
,
“quicksight:ListNamespaces”
,
“quicksight:DescribeAnalysisPermissions”
,
“quicksight:DescribeDashboardPermissions”
,
“quicksight:DescribeDataSetPermissions”
,
“quicksight:DescribeDataSourcePermissions”
,
“quicksight:DescribeFolderPermissions”
,
“quicksight:ListAnalyses”
,
“quicksight:ListDashboards”
,
“quicksight:ListDataSets”
,
“quicksight:ListDataSources”
,
“quicksight:ListFolders”
,
“quicksight:SearchAnalyses”
,
“quicksight:SearchDashboards”
,
“quicksight:SearchFolders”
,
“quicksight:UpdateAnalysisPermissions”
,
“quicksight:UpdateDashboardPermissions”
,
“quicksight:UpdateDataSetPermissions”
,
“quicksight:UpdateDataSourcePermissions”
,
“quicksight:UpdateFolderPermissions”
],
“Resource”
:
“*”
}
]
}

3

Hi Deepak,

If you search for the quicksight:SearchUsers permission, it doesn’t come up. The policy editor also throws a red X when manually adding it to the policy but if you ignore the error and push it through, it does seem to have worked.

As a side note, I also needed to add, quicksight:SearchDataSets and quicksight:SearchDataSources to the policy for managing assets.

Thanks again Deepak