How Amazon Nimble Studio works with IAM

Before you use IAM to manage access to Nimble Studio, learn what IAM features are available to use with Nimble Studio.

IAM features you can use with Amazon Nimble Studio
IAM feature	Nimble Studio support
Policy actions for Nimble Studio	Yes
Policy resources for Nimble Studio	Yes
Policy condition keys for Nimble Studio	Yes
Access control lists (ACLs) in Nimble Studio	No
Attribute-based access control (ABAC) with Nimble Studio	Yes
Using temporary credentials with Nimble Studio	Yes
Cross-service principal permissions for Nimble Studio	Yes
Service roles for Nimble Studio	Yes
Service-linked roles for Nimble Studio	No

To get a high-level view of how Nimble Studio and other AWS services work with most IAM features, see AWS services that work with IAM in the IAM User Guide.

Identity-based policies for Nimble Studio

Supports identity-based policies

Yes

Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as a user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and for what conditions. To learn how to create an identity-based policy, see Creating IAM policies in the IAM User Guide.

With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions for which actions are allowed or denied. You can’t specify the principal in an identity-based policy because it applies to the user or role to which it's attached. To learn about all of the elements that you can use in a JSON policy, see IAM JSON policy elements reference in the IAM User Guide.

Identity-based policy examples for Amazon Nimble Studio

To view examples of Nimble Studio identity-based policies, see Identity-based policy examples for Amazon Nimble Studio.

Resource-based policies within Nimble Studio

Supports resource-based policies

No

Nimble Studio doesn’t support resource-based policies or cross-account access. Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and for what conditions. Specify a principal in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.

Policy actions for Nimble Studio

Supports policy actions

Yes

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and for 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 AWS 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.

To see a list of Nimble Studio actions, see Actions defined by Amazon Nimble Studio in the Service Authorization Reference.

Policy actions in Nimble Studio use the following prefix before the action:

nimble

To specify multiple actions in a single statement, separate them with commas.

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

To view examples of Nimble Studio identity-based policies, see Identity-based policy examples for Amazon Nimble Studio.

Policy resources for Nimble Studio

Supports policy resources

Yes

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and for 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": "*"

To view examples of Nimble Studio identity-based policies, see Identity-based policy examples for Amazon Nimble Studio.

Policy condition keys for Nimble Studio

Supports policy condition keys

Yes

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and for 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, AWS evaluates them using a logical AND operation. If you specify multiple values for a single condition key, AWS 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 user permission to access a resource only if it's tagged with their username. For more information, see IAM policy elements: variables and tags in the IAM User Guide.

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

To view examples of Nimble Studio identity-based policies, see Identity-based policy examples for Amazon Nimble Studio.

Access control lists (ACLs) in Nimble Studio

Supports ACLs

No

Nimble Studio doesn’t support access control lists (ACLs). ACLs control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they don’t use the JSON policy document format.

Attribute-based access control (ABAC) with Nimble Studio

Supports ABAC (tags in policies)

Yes

Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes. In AWS, these attributes are called tags. You can attach tags to IAM entities (users or roles) and to many AWS resources. Tagging entities and resources is the first step of ABAC. Then you design ABAC policies to allow operations when the principal’s tag matches the tag on the resource that they're trying to access.

To control access based on tags, you provide tag information in the condition element of a policy using the aws:ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys.

For more information about ABAC, see What is ABAC? in the IAM User Guide. To view a tutorial with steps for setting up ABAC, see Use attribute-based access control (ABAC) in the IAM User Guide.

Using temporary credentials with Nimble Studio

Supports temporary credentials

Yes

Some AWS services don’t work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see AWS services that work with IAM in the IAM User Guide.

You're using temporary credentials if you sign in to the AWS Management Console using any method except a user name and password. For example, when you access AWS using your company’s single sign-on (SSO) link, that process automatically creates temporary credentials. You also automatically create temporary credentials when you sign in to the console as a user and then switch roles. For more information about switching roles, see Switching to a role (console) in the IAM User Guide.

You can manually create temporary credentials using the AWS CLI or AWS API. You can then use those temporary credentials to access AWS. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM.

Cross-service principal permissions for Nimble Studio

Supports principal permissions

Yes

Service roles for Nimble Studio

Supports service roles

Yes

A service role is an IAM role that a service assumes to perform actions on your behalf. Service roles provide access only within your account and can’t be used to grant access to services in other accounts. An administrator can create, modify, and delete a service role from within IAM. For more information, see Creating a role to delegate permissions to an AWS service in the IAM User Guide.

Warning

Changing the permissions for a service role might break Nimble Studio functionality. Edit service roles only when Nimble Studio provides guidance to do so.

Service-linked roles for Nimble Studio

Supports service-linked roles

No

Nimble Studio doesn’t support service-linked roles. A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An administrator can view, but not edit the permissions for service-linked roles.

For details about creating or managing service-linked roles, see AWS services that work with IAM. Find a service in the table that includes a Yes in the Service-linked role column. Choose the Yes link to view the service-linked role documentation for that service.