How Amazon Managed Blockchain (AMB) Hyperledger Fabric works with IAM

Before you use IAM to manage access to AMB Access Hyperledger Fabric, learn what IAM features are available to use with AMB Access Hyperledger Fabric.

To get a high-level view of how AMB Access Hyperledger Fabric 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 AMB Access Hyperledger Fabric

Supports identity-based policies: Yes

Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Define custom IAM permissions with customer managed 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 under which actions are allowed or denied. 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 AMB Access Hyperledger Fabric

To view examples of AMB Access Hyperledger Fabric identity-based policies, see Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples.

Resource-based policies within AMB Access Hyperledger Fabric

Supports resource-based policies: No

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 under what conditions. You must specify a principal in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.

To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see Cross account resource access in IAM in the IAM User Guide.

Policy actions for AMB Access Hyperledger Fabric

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 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. Include actions in a policy to grant permissions to perform the associated operation.

To see a list of AMB Access Hyperledger Fabric actions, see Actions defined by Amazon Managed Blockchain (AMB) Hyperledger Fabric in the Service Authorization Reference.

Policy actions in AMB Access Hyperledger Fabric use the following prefix before the action:

managedblockchain:

For example, to grant someone permission to create a node with the AMB Access CreateNode API operation, you include the managedblockchain:CreateNode action in their policy. Policy statements must include either an Action or NotAction element. AMB Access Hyperledger Fabric 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.

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

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

"Action": "managedblockchain::List*"

To view examples of AMB Access Hyperledger Fabric identity-based policies, see Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples.

Policy resources for AMB Access Hyperledger Fabric

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 under what conditions.

The Resource JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its Amazon Resource Name (ARN). For actions that don't support resource-level permissions, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

AMB Access resource types that can be used in IAM permissions policy statements for resources on Ethereum networks include the following:

Members, nodes, and invitations are associated with your account. Networks and proposals, on the other hand, are scoped to the entire blockchain network and are not associated with a particular account.

For example a network resource on AMB Access has the following ARN.

arn:${Partition}:managedblockchain:${Region}::networks/${NetworkId}

For example, to specify the n-MWY63ZJZU5HGNCMBQER7IN6OIU network in your statement, use the following ARN.

"Resource": "arn:aws:managedblockchain:us-east-1::networks/n-MWY63ZJZU5HGNCMBQER7IN6OIU"

To specify any network that is visible to your account, use the wildcard (*).

"Resource": "arn:aws:managedblockchain:us-east-1::networks/*"

Some AMB Access Hyperledger Fabric actions, such as CreateNetwork, ListInvitations, and ListNetworks cannot be performed on a specific resource. In those cases, you must use the wildcard (*).

"Resource": "*"

To see a list of AMB Access Hyperledger Fabric resource types and their ARNs, see Resources defined by Amazon Managed Blockchain (AMB) Hyperledger Fabric in the Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see Actions defined by Amazon Managed Blockchain (AMB) Hyperledger Fabric.

To view examples of AMB Access Hyperledger Fabric identity-based policies, see Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples.

Policy condition keys for AMB Access Hyperledger Fabric

Supports service-specific policy condition keys: No

Administrators can use AWS 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 specifies when statements execute based on defined criteria. 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. To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide.

To see a list of the AWS global condition keys supported, see Condition keys for Amazon Managed Blockchain (AMB) Hyperledger Fabric in the Service Authorization Reference. To learn with which actions and resources you can use a condition key, see Actions defined by Amazon Managed Blockchain (AMB) Hyperledger Fabric.

To view examples of AMB Access Hyperledger Fabric identity-based policies, see Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples.

ACLs in AMB Access Hyperledger Fabric

Supports ACLs: No

Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.

ABAC with AMB Access Hyperledger Fabric

Supports ABAC (tags in policies): Yes

Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.

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.

If a service supports all three condition keys for every resource type, then the value is Yes for the service. If a service supports all three condition keys for only some resource types, then the value is Partial.

For more information about ABAC, see Define permissions with ABAC authorization 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.

To control access based on tags, you provide tag information in the condition element of a policy using the managedblockchain::ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys. For more information about tagging AMB Access Hyperledger Fabric resources, see Tagging Amazon Managed Blockchain (AMB) resources.

To view example identity-based policies for allowing or denying access to resources and actions based on tags, see Controlling access using tags.

Using temporary credentials with AMB Access Hyperledger Fabric

Supports temporary credentials: Yes

Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM and AWS services that work with IAM in the IAM User Guide.

Cross-service principal permissions for AMB Access Hyperledger Fabric

Supports forward access sessions (FAS): Yes

Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see Forward access sessions.

Service roles for AMB Access Hyperledger Fabric

Supports service roles: Yes

A service role is an IAM role that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Create a role to delegate permissions to an AWS service in the IAM User Guide.

Service-linked roles for AMB Access Hyperledger Fabric

Supports service-linked roles: Yes

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 AWS account and are owned by the service. An IAM 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.