Access AWS B2B Data Interchange using an interface endpoint (AWS PrivateLink)

이 페이지는 귀하의 언어로 번역되지 않았습니다. 번역 요청

You can use AWS PrivateLink to create a private connection between your VPC and AWS B2B Data Interchange. You can access AWS B2B Data Interchange as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS B2B Data Interchange.

You establish this private connection by creating an interface endpoint, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for AWS B2B Data Interchange.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Considerations for AWS B2B Data Interchange

Before you set up an interface endpoint for AWS B2B Data Interchange, review Considerations in the AWS PrivateLink Guide.

AWS B2B Data Interchange supports making calls to all of its API actions through the interface endpoint.

VPC endpoint policies are not supported for AWS B2B Data Interchange. By default, full access to AWS B2B Data Interchange is allowed through the interface endpoint. Alternatively, you can associate a security group with the endpoint network interfaces to control traffic to AWS B2B Data Interchange through the interface endpoint.

Create an interface endpoint for AWS B2B Data Interchange

You can create an interface endpoint for AWS B2B Data Interchange using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Create an interface endpoint in the AWS PrivateLink Guide.

Create an interface endpoint for AWS B2B Data Interchange using the following service name:

com.amazonaws.region.b2bi

If you enable private DNS for the interface endpoint, you can make API requests to AWS B2B Data Interchange using its default Regional DNS name. For example, b2bi.us-east-1.amazonaws.com.

Create an endpoint policy for your interface endpoint

An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to AWS B2B Data Interchange through the interface endpoint. To control the access allowed to AWS B2B Data Interchange from your VPC, attach a custom endpoint policy to the interface endpoint.

For more information, see Control access to services using endpoint policies in the AWS PrivateLink Guide.

Example: VPC endpoint policy for AWS B2B Data Interchange actions

The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed AWS B2B Data Interchange actions for all principals on all resources.

{
   "Statement": [
      {
         "Principal": "*",
         "Effect": "Allow",
         "Action": [
            "servicename:action-1",
            "servicename:action-2",
            "servicename:action-3"
         ],
         "Resource":"*"
      }
   ]
}