Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Using Quick Suite with IAM

Before you use IAM to manage access to Amazon Quick Suite, you should understand what IAM features are available to use with Amazon Quick Suite. To get a high-level view of how Amazon Quick Suite and other Amazon services work with IAM, see Amazon Services That Work with IAM in the IAM User Guide.

Amazon Quick Suite Policies (identity-based)

With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Amazon Quick Suite supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see IAM JSON Policy Elements Reference in the IAM User Guide.

You can use Amazon root credentials or IAM user credentials to create an Amazon Quick Suite account. Amazon root and administrator credentials already have all of the required permissions for managing Amazon Quick Suite access to Amazon resources.

However, we recommend that you protect your root credentials, and instead use IAM user credentials. To do this, you can create a policy and attach it to the IAM user and roles that you plan to use for Amazon Quick Suite. The policy must include the appropriate statements for the Amazon Quick Suite administrative tasks you need to perform, as described in the following sections.

Actions

Administrators can use Amazon JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually have the same name as the associated Amazon API operation. There are some exceptions, such as permission-only actions that don't have a matching API operation. There are also some operations that require multiple actions in a policy. These additional actions are called dependent actions.

Include actions in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon Quick Suite use the following prefix before the action: quicksight:. For example, to grant someone permission to run an Amazon EC2 instance with the Amazon EC2 RunInstances API operation, you include the ec2:RunInstances action in their policy. Policy statements must include either an Action or NotAction element. Amazon Quick Suite defines its own set of actions that describe tasks that you can perform with this service.

To specify multiple actions in a single statement, separate them with commas as follows:

"Action": [
	      "quicksight:action1",
	      "quicksight:action2"]

You can specify multiple actions using wildcards (*). For example, to specify all actions that begin with the word Create, include the following action:

"Action": "quicksight:Create*"

Amazon Quick Suite provides a number of Amazon Identity and Access Management (IAM) actions. All Amazon Quick Suite actions are prefixed with quicksight:, such as quicksight:Subscribe. For information about using Amazon Quick Suite actions in an IAM policy, see IAM policy examples for Amazon Quick Suite.

To see the most up-to-date list of Amazon Quick Suite actions, see Actions Defined by Amazon Quick Suite in the IAM User Guide.

Resources

Administrators can use Amazon JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Resource JSON policy element specifies the object or objects to which the action applies. Statements must include either a Resource or a NotResource element. As a best practice, specify a resource using its Amazon Resource Name (ARN). You can do this for actions that support a specific resource type, known as resource-level permissions.

For actions that don't support resource-level permissions, such as listing operations, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

Following is an example policy. It means that the caller with this policy attached, is able to invoke the CreateGroupMembership operation on any group, provided that the user name they are adding to the group is not user1.

{
    "Effect": "Allow",
    "Action": "quicksight:CreateGroupMembership",
    "Resource": "arn:aws-cn:quicksight:us-east-1:aws-account-id:group/default/*",
    "Condition": {
        "StringNotEquals": {
            "quicksight:UserName": "user1"
        }
    }
}

Some Amazon Quick Suite actions, such as those for creating resources, cannot be performed on a specific resource. In those cases, you must use the wildcard (*).

"Resource": "*"

Some API actions involve multiple resources. To specify multiple resources in a single statement, separate the ARNs with commas.

"Resource": [
	      "resource1",
	      "resource2"

To see a list of Amazon Quick Suite resource types and their Amazon Resource Names (ARNs), see Resources Defined by Amazon Quick Suite in the IAM User Guide. To learn with which actions you can specify the ARN of each resource, see Actions Defined by Amazon Quick Suite.

Condition keys

Administrators can use Amazon JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Condition element (or Condition block) lets you specify conditions in which a statement is in effect. The Condition element is optional. You can create conditional expressions that use condition operators, such as equals or less than, to match the condition in the policy with values in the request.

If you specify multiple Condition elements in a statement, or multiple keys in a single Condition element, Amazon evaluates them using a logical AND operation. If you specify multiple values for a single condition key, Amazon evaluates the condition using a logical OR operation. All of the conditions must be met before the statement's permissions are granted.

You can also use placeholder variables when you specify conditions. For example, you can grant an IAM user permission to access a resource only if it is tagged with their IAM user name. For more information, see IAM policy elements: variables and tags in the IAM User Guide.

Amazon supports global condition keys and service-specific condition keys. To see all Amazon global condition keys, see Amazon global condition context keys in the IAM User Guide.

Amazon Quick Suite does not provide any service-specific condition keys, but it does support using some global condition keys. To see all Amazon global condition keys, see Amazon Global Condition Context Keys in the IAM User Guide.

Examples

To view examples of Amazon Quick Suite identity-based policies, see Amazon Quick Suite Policies (identity-based).

Amazon Quick Suite policies (resource-based)

Amazon Quick Suite doesn't support resource-based policies. However, you can use the Amazon Quick Suite console to configure access to other Amazon resources in your Amazon Web Services account.

Authorization based on Amazon Quick Suite tags

Amazon Quick Suite does not support tagging resources or controlling access based on tags.

Amazon Quick Suite IAM roles

An IAM role is an entity within your Amazon account that has specific permissions. You can use IAM roles to group permissions together to make it easier to manage user's access to Amazon Quick Suite actions.

Amazon Quick Suite doesn't support the following role features:

For more information on how Amazon Quick Suite uses IAM roles, see Using Amazon Quick Suite with IAM and IAM policy examples for Amazon Quick Suite.