# Authentication and Access Control for AMB Access Hyperledger Fabric Authentication and Access Control AWS Identity and Access Management (IAM) permissions policies, VPC endpoint services powered by AWS PrivateLink, and Amazon EC2 security groups provide the primary means for you to control access to Amazon Managed Blockchain (AMB). In addition to these AWS services, open-source frameworks that run on AMB Access have authentication and access control features that you can configure. IAM permissions policies are associated with AWS users in your account and determine who has access to what. Permissions policies specify the actions that each user can perform using AMB Access and other AWS services. VPC endpoint services allow each AMB Access network member to connect privately to AMB Access resources. Amazon EC2 security groups act as virtual firewalls and determine the inbound and outbound network traffic that is allowed between AMB Access resources and other Amazon EC2 resources. In AMB Access, these security groups are associated with the VPC endpoint in your account and with any framework clients that run on AWS, such as a Hyperledger Fabric client running on an Amazon EC2 instance. Before you configure authentication and access control using AWS services and open-source features, we recommend that you review the following resources: + For more information about IAM and IAM permissions policies, see [Identity and Access Management for Amazon Managed Blockchain (AMB) Hyperledger Fabric](security-iam.md). We also recommend [What is IAM?](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) and [IAM JSON Policy Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html) in the *IAM User Guide*. + For more information about VPC endpoints, see [Create an Interface VPC Endpoint for Amazon Managed Blockchain (AMB) Hyperledger Fabric](managed-blockchain-endpoints.md) and [VPC Endpoints ](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html) in the *Amazon VPC User Guide*. + For more information about Amazon EC2 security groups, see [Configuring Security Groups for Amazon Managed Blockchain (AMB) Hyperledger Fabric](managed-blockchain-security-sgs.md) and [Amazon EC2 Security Groups for Linux Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) in the *Amazon EC2 User Guide*. + For more information about the Hyperledger Fabric Certificate Authority (CA), see [Certificate Authority (CA) Setup](https://hyperledger-fabric-ca.readthedocs.io/en/latest/) in the Hyperledger Fabric documentation. + For more information about the supported Hyperledger Fabric 2.2 application access control lists, see [Application Access Control Lists](https://hyperledger-fabric.readthedocs.io/en/release-2.2/access_control.html) in the Hyperledger Fabric documentation. # Identity and Access Management for Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity and Access Management AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use AMB Access Hyperledger Fabric resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [ ## Audience ](#security_iam_audience) + [ ## Authenticating with identities ](#security_iam_authentication) + [ ## Managing access using policies ](#security_iam_access-manage) + [ # How Amazon Managed Blockchain (AMB) Hyperledger Fabric works with IAM ](security_iam_service-with-iam.md) + [ # Troubleshooting Amazon Managed Blockchain (AMB) Hyperledger Fabric identity and access ](security_iam_troubleshoot.md) + [ # Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples ](security_iam_id-based-policy-examples.md) + [ # Example IAM Role Permissions Policy for Hyperledger Fabric Client EC2 Instance ](security_iam_hyperledger_ec2_client.md) + [ # Using Service-Linked Roles for AMB Access ](using-service-linked-roles.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting Amazon Managed Blockchain (AMB) Hyperledger Fabric identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How Amazon Managed Blockchain (AMB) Hyperledger Fabric works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### Federated identity As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials. A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials. For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples include 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. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # 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. **IAM features you can use with Amazon Managed Blockchain (AMB) Hyperledger Fabric** | IAM feature | AMB Access Hyperledger Fabric support | | --- | --- | | [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes | | [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No | | [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes | | [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes | | [Policy condition keys (service-specific)](#security_iam_service-with-iam-id-based-policies-conditionkeys) | No | | [ACLs](#security_iam_service-with-iam-acls) | No | | [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Yes | | [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes | | [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes | | [Service roles](#security_iam_service-with-iam-roles-service) | Yes | | [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes | 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Identity-based policies for AMB Access Hyperledger Fabric Identity-based policies **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) 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](security_iam_id-based-policy-examples.md). ## Resource-based policies within AMB Access Hyperledger Fabric Resource-based policies **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Policy actions for AMB Access Hyperledger Fabric Policy actions **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](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonmanagedblockchain.html#amazonmanagedblockchain-actions-as-permissions) 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 (\$1). 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](security_iam_id-based-policy-examples.md). ## Policy resources for AMB Access Hyperledger Fabric Policy resources **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)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) 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: + network + member + node + proposal + invitation 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 (\$1). ``` "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 (\$1). ``` "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](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonmanagedblockchain.html#amazonmanagedblockchain-resources-for-iam-policies) 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](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonmanagedblockchain.html#amazonmanagedblockchain-actions-as-permissions). To view examples of AMB Access Hyperledger Fabric identity-based policies, see [Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples](security_iam_id-based-policy-examples.md). ## Policy condition keys for AMB Access Hyperledger Fabric Policy condition keys **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. **Note** AMB Access Hyperledger Fabric does not provide any service-specific condition keys, but it does support using some AWS global condition keys. To see a list of the AWS global condition keys supported, see [Condition keys for Amazon Managed Blockchain (AMB) Hyperledger Fabric](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonmanagedblockchain.html#amazonmanagedblockchain-policy-keys) 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](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonmanagedblockchain.html#amazonmanagedblockchain-actions-as-permissions). To view examples of AMB Access Hyperledger Fabric identity-based policies, see [Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples](security_iam_id-based-policy-examples.md). ## ACLs in AMB Access Hyperledger Fabric ACLs **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 ABAC **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) 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](tagging.md). To view example identity-based policies for allowing or denying access to resources and actions based on tags, see [Controlling access using tags](security_iam_id-based-policy-examples.md#security_iam_id-based-policy-examples-tags). ## Using temporary credentials with AMB Access Hyperledger Fabric Temporary credentials **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. ## Cross-service principal permissions for AMB Access Hyperledger Fabric Principal permissions **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). ## Service roles for AMB Access Hyperledger Fabric Service roles **Supports service roles:** Yes A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. **Warning** Changing the permissions for a service role might break AMB Access Hyperledger Fabric functionality. Edit service roles only when AMB Access Hyperledger Fabric provides guidance to do so. ## Service-linked roles for AMB Access Hyperledger Fabric Service-linked roles **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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). 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. # Troubleshooting Amazon Managed Blockchain (AMB) Hyperledger Fabric identity and access Troubleshooting Use the following information to help you diagnose and fix common issues that you might encounter when working with AMB Access Hyperledger Fabric and IAM. **Topics** + [ ## I am not authorized to perform an action in AMB Access Hyperledger Fabric ](#security_iam_troubleshoot-no-permissions) + [ ## I am not authorized to perform iam:PassRole ](#security_iam_troubleshoot-passrole) + [ ## I want to allow people outside of my AWS account to access my AMB Access Hyperledger Fabric resources ](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in AMB Access Hyperledger Fabric If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-example-widget` resource but doesn't have the fictional `managedblockchain::GetWidget` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: managedblockchain::GetWidget on resource: my-example-widget ``` In this case, the policy for the `mateojackson` user must be updated to allow access to the `my-example-widget` resource by using the `managedblockchain::GetWidget` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to AMB Access Hyperledger Fabric. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in AMB Access Hyperledger Fabric. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. ``` User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole ``` In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I want to allow people outside of my AWS account to access my AMB Access Hyperledger Fabric resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether AMB Access Hyperledger Fabric supports these features, see [How Amazon Managed Blockchain (AMB) Hyperledger Fabric works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. # Amazon Managed Blockchain (AMB) Hyperledger Fabric Identity-Based Policy Examples Identity-Based Policy Examples By default, IAM users and roles don't have permission to create or modify AMB Access Hyperledger Fabric resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the specified resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions. To learn how to create an IAM identity-based policy using these example JSON policy documents, see [Creating Policies on the JSON Tab](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the *IAM User Guide*. **Topics** + [ ## Policy Best Practices ](#security_iam_service-with-iam-policy-best-practices) + [ ## Allow Users to View Their Own Permissions ](#security_iam_id-based-policy-examples-view-own-permissions) + [ ## Using the AMB Access Hyperledger Fabric Console ](#security_iam_id-based-policy-examples-console) + [ ## Performing All AMB Access Actions on All Accessible Networks for an AWS Account ](#security_iam_id-based-policy-examples-access-one-bucket) + [ ## Controlling access using tags ](#security_iam_id-based-policy-examples-tags) ## Policy Best Practices Identity-based policies determine whether someone can create, access, or delete AMB Access Hyperledger Fabric resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations: + **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## Allow Users to View Their Own Permissions This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "ViewOwnUserInfo", "Effect": "Allow", "Action": [ "iam:GetUserPolicy", "iam:ListGroupsForUser", "iam:ListAttachedUserPolicies", "iam:ListUserPolicies", "iam:GetUser" ], "Resource": ["arn:aws:iam::*:user/${aws:username}"] }, { "Sid": "NavigateInConsole", "Effect": "Allow", "Action": [ "iam:GetGroupPolicy", "iam:GetPolicyVersion", "iam:GetPolicy", "iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies", "iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers" ], "Resource": "*" } ] } ``` ## Using the AMB Access Hyperledger Fabric Console Using the Console To access the Amazon Managed Blockchain (AMB) Hyperledger Fabric console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AMB Access Hyperledger Fabric resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy. To ensure that those entities can still use the AMB Access Hyperledger Fabric console, also attach the following AWS managed policy to the entities. ``` AmazonManagedBlockchainConsoleFullAccess ``` For more information, see [Adding Permissions to a User](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*. You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that you're trying to perform. ## Performing All AMB Access Actions on All Accessible Networks for an AWS Account Performing All Actions The following example shows you how to grant an IAM user in AWS account `123456789012`access to all the network and member resources in the account in the `us-east-1` Region. This example shows how the user is permitted to list and create; manage networks, proposals, members, and nodes; and reject invitations to join other networks. **Note** `Deny` and `Allow` actions on a resource (for example `Network`) only affect actions on the resource itself and *do not* apply to child resources such as `Member` and `Node`. Child resources (such as nodes, members and invitations) must have AWS account ids in their policy so they can be enforced as shown in the following example. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Sid": "ManageNetworkResources", "Effect": "Allow", "Action": [ "managedblockchain:CreateNetwork", "managedblockchain:GetNetwork", "managedblockchain:CreateProposal", "managedblockchain:ListProposals", "managedblockchain:CreateMember", "managedblockchain:ListMembers" ], "Resource": [ "arn:aws:managedblockchain:us-east-1::networks/*" ] }, { "Sid": "ManageMemberResources", "Effect": "Allow", "Action": [ "managedblockchain:GetMember", "managedblockchain:DeleteMember", "managedblockchain:CreateNode", "managedblockchain:ListNodes" ], "Resource": [ "arn:aws:managedblockchain:us-east-1:123456789012:members/*" ] }, { "Sid": "ManageNodeResources", "Effect": "Allow", "Action": [ "managedblockchain:GetNode", "managedblockchain:DeleteNode", "managedblockchain:UpdateNode" ], "Resource": [ "arn:aws:managedblockchain:us-east-1:123456789012:nodes/*" ] }, { "Sid": "ManageProposalResources", "Effect": "Allow", "Action": [ "managedblockchain:GetProposal", "managedblockchain:ListProposalVotes", "managedblockchain:VoteOnProposal" ], "Resource": [ "arn:aws:managedblockchain:us-east-1::proposals/*" ] }, { "Sid": "ManageInvitationResources", "Effect": "Allow", "Action": [ "managedblockchain:RejectInvitation" ], "Resource": [ "arn:aws:managedblockchain:us-east-1:123456789012:invitations/*" ] } ] } ``` ------ ## Controlling access using tags The following example policy statements demonstrate how you can use tags to limit access to AMB Access Hyperledger Fabric resources and actions performed on those resources. To tag resources during creation, policy statements that allow the create action for the resource as well as the `TagResource` action must be attached to the IAM principal performing the operation. **Note** This topic includes examples of policy statements with a `Deny` effect. Each policy statement assumes that a statement with a broader `Allow` effect for the same actions exists; the `Deny` policy statement restricts that otherwise overly-permissive allow statement. **Example – Require a tag key with either of two values to be added during network creation** The following identity-based policy statements allow the IAM principal to create a network only if the network is created with the tags specified. The statement with the `Sid` set to `RequireTag` specifies that network creation is allowed only if the network is created with a tag that has a tag key of `department` and a value of either `sales` or `marketing`; otherwise, the create network operation fails. The statement with `Sid` set to `AllowTagging` allows the IAM principal to tag networks, which are not associated with an AWS account ID. It also allows tagging of members in the specified AWS account, `111122223333`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "RequireTag", "Effect": "Allow", "Action": [ "managedblockchain:CreateNetwork" ], "Resource": [ "*" ], "Condition": { "StringLike": { "aws:RequestTag/department": [ "sales", "marketing" ] } } }, { "Sid": "AllowTagging", "Effect": "Allow", "Action": [ "managedblockchain:TagResource" ], "Resource": [ "arn:aws:managedblockchain:us-east-1::networks/*", "arn:aws:managedblockchain:us-east-1:111122223333:members/*" ] } ] } ``` **Example – Deny access to networks that have a specific tag key** The following identity-based policy statement denies the IAM principal the ability to retrieve or view information for networks that have a tag with a tag key of `restricted`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyRestrictedNetwork", "Effect": "Deny", "Action": [ "managedblockchain:GetNetwork" ], "Resource": [ "*" ], "Condition": { "StringLike": { "aws:ResourceTag/restricted": [ "*" ] } } } ] } ``` **Example – Deny member creation for networks with a specific tag key and value** The following identity-based policy statement denies the IAM principal from creating a member on any network that has a tag with a tag key of `department` with the value of `accounting`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyMemberCreation", "Effect": "Deny", "Action": [ "managedblockchain:CreateMember" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/department": "accounting" } } } ] } ``` **Example – Allow member creation only if a specific tag key and value are added** The following identity-based policy statements allow the IAM principal to create members in the account `111122223333` only if the member is created with a tag that has the tag key of `department` and a tag value of `accounting`; otherwise, the create member operation fails. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "RestrictMemberCreation", "Effect": "Allow", "Action": [ "managedblockchain:CreateMember" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:RequestTag/department": "accounting" } } }, { "Sid": "AllowTaggingOfMembers", "Effect": "Allow", "Action": [ "managedblockchain:TagResource" ], "Resource": [ "arn:aws:managedblockchain:us-east-1:111122223333:members/*" ] } ] } ``` **Example – Allow access only to members that have a specified tag key** The following identity-based policy statement allows the IAM principal to retrieve or view information about members only if the member has a tag with a tag key of `unrestricted`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "", "Effect": "Allow", "Action": [ "managedblockchain:GetMember" ], "Resource": [ "*" ], "Condition": { "StringLike": { "aws:ResourceTag/unrestricted": [ "*" ] } } } ] } ``` **Example – Deny node creation if a specific tag key and value are added during creation** The following identity-based policy statement denies the IAM principal the ability to create a node if a tag with the tag key of `department` and a value of `analytics` is added during creation. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyCreateNodeWithTag", "Effect": "Deny", "Action": [ "managedblockchain:CreateNode" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:RequestTag/department": [ "analytics" ] } } } ] } ``` **Example – Deny node creation for members with a specific tag key and value** The following identity-based policy statement denies the IAM principal the ability to create a node if the member to which the node will belong has a tag with a tag key of `department` and a tag value of `analytics`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyCreateNodeForTaggedMember", "Effect": "Deny", "Action": [ "managedblockchain:CreateNode" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/department": [ "analytics" ] } } } ] } ``` **Example – Allow access only to nodes with a specific tag key and value** The following identity-based policy statement allows the IAM principal to retrieve or view information about nodes only if the node has a tag with a tag key of `department` and a tag value of `sales`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AllowTaggedNodeAccess", "Effect": "Allow", "Action": [ "managedblockchain:GetNode" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/department": [ "sales" ] } } } ] } ``` **Example – Deny access to nodes with a specific tag key** The following identity-based policy statement denies the IAM principal the ability to retrieve or view information about a node if the node has a tag with a tag key of `restricted`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyAccessToTaggedNodes", "Effect": "Deny", "Action": [ "managedblockchain:GetNode" ], "Resource": [ "*" ], "Condition": { "StringLike": { "aws:ResourceTag/restricted": [ "*" ] } } } ] } ``` **Example – Allow proposal creation only for networks with a specific tag key and value** The following identity-based policy statement allows the IAM principal to create a proposal only if the network for which the proposal is made has a tag with a tag key of `department` and a value of `accounting`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AllowCreateProposalOnlyForTaggedNetwork", "Effect": "Allow", "Action": [ "managedblockchain:CreateProposal" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/department": [ "accounting" ] } } } ] } ``` **Example – Allow proposal creation only if a specific tag key and value are added** The following identity-based policy statements allow the IAM principal to create a proposal for inviting the specified account `123456789012` to the network only if a tag with a tag key of `consortium` and a tag value of `exampleconsortium` is added during proposal creation. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "RequireTagWithProposal", "Effect": "Allow", "Action": [ "managedblockchain:CreateProposal" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:RequestTag/consortium": [ "exampleconsortium" ] } } }, { "Sid": "AllowProposalAndInvitationTagging", "Effect": "Allow", "Action": [ "managedblockchain:TagResource" ], "Resource": [ "arn:aws:managedblockchain:us-east-1::proposals/*", "arn:aws:managedblockchain:us-east-1:123456789012:invitations/*" ] } ] } ``` **Example – Allow access only to proposals with a specific tag key and value** The following identity-based policy statement allows the IAM principal to retrieve and view proposals only if the proposal has a tag with a tag key of `consortium` and a tag value of `exampleconsortium`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "AllowOnlyTaggedProposalAccess", "Effect": "Allow", "Action": [ "managedblockchain:GetProposal" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/consortium": [ "exampleconsortium" ] } } } ] } ``` **Example – Deny the ability to vote on proposals based on a specific tag key and value** The following identity-based policy statement denies the IAM principal the ability to vote on proposals that have a tag with the tag key of `consortium` and a tag value of `exampleconsortium`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "DenyVoteOnTaggedProposal", "Effect": "Deny", "Action": [ "managedblockchain:VoteOnProposal" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/consortium": [ "exampleconsortium" ] } } } ] } ``` **Example – Deny the ability to reject an invitation with a specific tag and value** The following identity-based policy statement denies the IAM principal the ability to reject on invitation that has a tag with the tag key of `consortium` and a tag value of `exampleconsortium`. **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "1", "Effect": "Deny", "Action": [ "managedblockchain:RejectInvitation" ], "Resource": [ "*" ], "Condition": { "StringEquals": { "aws:ResourceTag/consortium": [ "exampleconsortium" ] } } } ] } ``` # Example IAM Role Permissions Policy for Hyperledger Fabric Client EC2 Instance Hyperledger Fabric Client IAM Permissions When you administer, develop, and deploy chaincode using an EC2 instance as a Hyperledger Fabric client, the permissions policies attached to the AWS Identity and Access Management *instance profile* and *instance role* associated with the instance determine its permissions to interact with other AWS resources, including AMB Access. The permissions policy shown in the following procedure provides sufficient privileges when it is attached to the IAM role of the instance. The procedure demonstrates how to create a role with only this permissions policy attached and then attach that role to an EC2 instance. If you have an existing service role and instance profile attached to your EC2 instance, you can create an additional policy using the following example and then attach it to the existing role. Only one role can be attached to an EC2 instance. For more information, see [IAM roles for Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html) in the *Amazon EC2 User Guide*. **To create a permissions policy, attach it to an IAM role, and attach the role to a Hyperledger Fabric client EC2 instance** 1. Open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). 1. In the navigation pane, choose **Policies**, and then **Create policy**. 1. Choose the `JSON` tab, and then copy and paste the following policy statement. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "ListNetworkMembers", "Effect": "Allow", "Action": [ "managedblockchain:GetNetwork", "managedblockchain:ListMembers" ], "Resource": [ "arn:aws:managedblockchain:*:123456789012:networks/*" ] }, { "Sid": "AccessManagedBlockchainBucket", "Effect": "Allow", "Action": [ "s3:GetObject" ], "Resource": "arn:aws:s3:::us-east-1.managedblockchain/*" }, { "Sid": "ManageNetworkResources", "Effect": "Allow", "Action": [ "managedblockchain:CreateProposal", "managedblockchain:GetProposal", "managedblockchain:DeleteMember", "managedblockchain:VoteOnProposal", "managedblockchain:ListProposals", "managedblockchain:GetNetwork", "managedblockchain:ListMembers", "managedblockchain:ListProposalVotes", "managedblockchain:RejectInvitation", "managedblockchain:GetNode", "managedblockchain:GetMember", "managedblockchain:DeleteNode", "managedblockchain:CreateNode", "managedblockchain:CreateMember", "managedblockchain:ListNodes" ], "Resource": [ "arn:aws:managedblockchain:*::networks/*", "arn:aws:managedblockchain:*::proposals/*", "arn:aws:managedblockchain:*:123456789012:members/*", "arn:aws:managedblockchain:*:123456789012:invitations/*", "arn:aws:managedblockchain:*:123456789012:nodes/*" ] }, { "Sid": "WorkWithNetworksForAcct", "Effect": "Allow", "Action": [ "managedblockchain:ListNetworks", "managedblockchain:ListInvitations", "managedblockchain:CreateNetwork" ], "Resource": "*" } ] } ``` ------ 1. Replace *123456789012* with your AWS Account ID. If you are working in a different Region, replace *us-east-1* with the appropriate Region, and then choose **Review policy**. 1. Enter a **Name** for the policy, for example, `HyperledgerFabricClientAccess`. Enter an optional **Description**, and then choose **Create policy**. You now have a permissions policy that you can attach to an IAM role for an EC2 instance. 1. From the navigation pane, choose **Roles**, **Create role**. 1. Under **Select type of trusted entity**, leave **AWS service** selected. Under **Common use cases**, choose **EC2 - Allows EC2 instances to call AWS services on your behalf**, and then choose **Next: Permissions**. 1. Under **Attach permissions policies**, start typing the name of the permissions policy you created in the previous steps. Select that policy from the list, and then choose **Next: Tags**. 1. Leave the key-value fields blank or type key-value pairs for any tags that you want to apply to this role, and then choose **Next: Review**. 1. Enter a **Role name** that helps you identify this role, for example, **ServiceRoleForHyperledgerFabricClient**. Enter an optional **Description**, and then choose **Create role**. You now have a service role with appropriate permissions that you can associate with your Hyperledger Fabric EC2 instance. 1. Open the EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. From the navigation pane, choose **Instances**. 1. From the list of instances, select the instance that you are using as a Hyperledger Fabric client. 1. Choose **Actions**, **Security**, **Modify IAM role**. 1. For **IAM role** begin typing the name of the role you created, for example, **ServiceRoleForHyperledgerFabricClient**. Select it from the list, and then choose **Apply**. # Using Service-Linked Roles for AMB Access Using Service-Linked Roles Amazon Managed Blockchain (AMB) uses AWS Identity and Access Management (IAM)[ service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AMB Access. Service-linked roles are predefined by AMB Access and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role can make setting up AMB Access easier because you don’t have to manually add the necessary permissions. AMB Access defines the permissions of its service-linked roles, and, unless defined otherwise, only AMB Access can assume its roles. The defined permissions include the trust policy and the permissions policy. The permissions policy cannot be attached to any other IAM entity. You can delete a service-linked role only after first deleting its related resources. This protects your AMB Access resources because you can't inadvertently remove permission to access the resources. For information about other services that support service-linked roles, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and look for the services that have **Yes **in the **Service-Linked Role** column. Choose a **Yes** with a link to view the service-linked role documentation for that service. ## Service-Linked Role Permissions for AMB Access AMB Access uses the service-linked role named **AWSServiceRoleForAmazonManagedBlockchain**. This role enables access to AWS Services and Resources used or managed by Amazon Managed Blockchain. The AWSServiceRoleForAmazonManagedBlockchain service-linked role trusts the following services to assume the role: + `managedblockchain.amazonaws.com` The role permissions policy allows AMB Access to complete actions on the specified resources shown in the following example policy. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Action": [ "logs:CreateLogGroup" ], "Effect": "Allow", "Resource": "arn:aws:logs:*:*:log-group:/aws/managedblockchain/*" }, { "Effect": "Allow", "Action": [ "logs:CreateLogStream", "logs:PutLogEvents", "logs:DescribeLogStreams" ], "Resource": [ "arn:aws:logs:*:*:log-group:/aws/managedblockchain/*:log-stream:*" ] } ] } ``` ------ You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see [Service-Linked Role Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*. ## Creating a Service-Linked Role for AMB Access You don't need to manually create a service-linked role. When you create a network, a member, or a peer node, AMB Access creates the service-linked role for you. It doesn't matter if you use the AWS Management Console, the AWS CLI, or the AWS API. The IAM entity performing the action must have permissions to create the service-linked role. After the role is created in your account, AMB Access can use it for all networks and members. If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create a network, member, or node, AMB Access creates the service-linked role for you again. ## Editing a Service-Linked Role for AMB Access AMB Access does not allow you to edit the AWSServiceRoleForAmazonManagedBlockchain service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a Service-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*. ## Deleting a Service-Linked Role for AMB Access If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it. **Note** If the AMB Access service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. **To manually delete the service-linked role** Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAmazonManagedBlockchain service-linked role. For more information, see [Deleting a Service-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*. ## Supported Regions for AMB Access Service-Linked Roles AMB Access supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html).