Permissions for Amazon QuickSight resources
If you're not sure what the necessary permission is, you can attempt to make a call.
The client then tells you what the missing permission is. You can use asterisk
(*
) in the Resource field of your permission policy instead of
specifying explicit resources. However, we highly recommend that you restrict each
permission as much as possible. You can restrict user access by specifying or excluding
resources in the policy, using their Amazon QuickSight ARN. To retrieve the ARN of an Amazon QuickSight resource,
use the Describe
operation on the relevant resource.
Before you can call the Amazon QuickSight API operations, you need the
quicksight:operation-name
permission in a
policy attached to your IAM identity. For example, to call list-users
,
you need the permission quicksight:ListUsers
. The same pattern applies to
all operations. If you attempt to make the call you don't have permissions to call, the
resulting error shows you what the missing permission is. We highly recommend that you
restrict each permission as much as possible.
You can add conditions in IAM to further restrict access to an API in some scenarios. For
example, when you add User1
to Group1
, the main resource is
Group1
. You can allow or deny access to certain groups. Or you can also
edit the Amazon QuickSight IAM key quicksight:UserName
to add a condition to allow or
prevent certain users from being added to that group.
For more information, see the following:
Best practices
By working with Amazon QuickSight, you can share analyses, dashboards, templates, and themes with up to 100 principals. A principal can be one of the following:
-
The Amazon Resource Name (ARN) of an Amazon QuickSight user or group associated with a data source or dataset. (This is common.)
-
The ARN of an Amazon QuickSight user, group, or namespace associated with an analysis, dashboard, template, or theme. (This is common.)
-
The ARN of an AWS account root: This is an IAM ARN rather than a QuickSight ARN. Use this option only to share resources (templates) across AWS accounts. (This is less common.)
To share these resources with more principals, consider assigning resource permissions at the group or namespace level. For example, if you add users into a group and share a resource to the group, the group counts as one principal. This is true even though it's shared to everyone in the group.