Identity and access management for AWS B2B Data Interchange

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 AWS B2B Data Interchange resources. IAM is an AWS service that you can use with no additional charge.

How AWS B2B Data Interchange works with IAM

Before you use IAM to manage access to AWS B2B Data Interchange, learn what IAM features are available to use with AWS B2B Data Interchange.

To get a high-level view of how B2B Data Interchange 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 B2B Data Interchange

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 B2B Data Interchange

To view examples of AWS B2B Data Interchange identity-based policies, see Identity-based policy examples for AWS B2B Data Interchange.

Resource-based policies within B2B Data Interchange

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 B2B Data Interchange

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 B2B Data Interchange actions, see Actions, resources, and condition keys for AWS B2B Data Interchange in the Service Authorization Reference.

Policy actions in B2B Data Interchange use the following prefix before the action:

 *what is "b2bi"?

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

"Action": [
      " *what is "b2bi"?:action1",
      " *what is "b2bi"?:action2"
         ]

To view examples of AWS B2B Data Interchange identity-based policies, see Identity-based policy examples for AWS B2B Data Interchange.

Policy resources for B2B Data Interchange

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": "*"

To see a list of B2B Data Interchange resource types and their ARNs, see GT-RESOURCES-URL in the Service Authorization Reference. To learn with which actions you can specify the ARN of each resource, see GT-ACTIONS-URL.

To view examples of AWS B2B Data Interchange identity-based policies, see Identity-based policy examples for AWS B2B Data Interchange.

Policy condition keys for B2B Data Interchange

Supports service-specific 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 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 B2B Data Interchange condition keys, see GT-CONDITIONS-URL in the Service Authorization Reference. To learn with which actions and resources you can use a condition key, see GT-ACTIONS-URL.

To view examples of AWS B2B Data Interchange identity-based policies, see Identity-based policy examples for AWS B2B Data Interchange.

ACLs in B2B Data Interchange

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.