E-MapReduce:Use a node endpoint to access an EMR cluster

Step 1: Create a VPC peering connection

1. Log on to the VPC peering connection console. In the top navigation bar, select the region where the requester VPC is located, which is China (Beijing) in this example. In the left-side navigation pane, click VPC Peering Connection.

2. If you have not used VPC peering connection before, click Activate CDT on the VPC Peering Connection page, and then click OK in the dialog box.

   Note

   To create a VPC peering connection across accounts, ensure that the accepter has enabled the Cloud Data Transfer (CDT) feature.

3. Go to the VPC Peering Connection page, click Create VPC Peering Connection, and set the parameters as follows:

   

   Inter-region scenarios allow you to select the Link Type based on business latency requirements.

   • Gold (default): Meet general requirements for latency and connection quality.

   • Platinum: Best suited for scenarios that require lower latency and more stable connections, such as securities trading and real-time gaming.

   Note

   • You can create four types of VPC peering connections: intra-region same-account, inter-region same-account, intra-region cross-account, and inter-region cross-account.

   • When the accepter account is Same-Account, the system automatically establishes the connection after the requester initiates the request. No action is required from the accepter.

   • When the accepter account is Cross-Account, the accepter needs to accept the peering request before the VPC peering connection can be created. The accepter may reject the request and terminate the VPC peering connection process. The steps that need to be taken by the accepter are as follows :

     1. Log on to the VPC console with the accepter account. In the left-side navigation pane, click VPC Peering Connection.

     2. Find the target VPC peering connection on the VPC Peering Connection page. Currently, the status of the connection is Accepting. Decide whether to accept the request:

        • Accept: The status changes from Accepting to Updating.

          When the status changes to Activated, it indicates the connection is ready for use.

        • Reject: The status changes from Accepting to Rejected.

          A Rejected VPC peering connection cannot be used. You can Delete it from either the requester or the accepter end.

        • If the accepter takes no action on a cross-account VPC peering connection request, the connection status changes to Expired after 7 days.

Step 2: Configure routes

After a VPC peering connection has been created and Activated, you need to add route entries that point to the peer VPC on both ends to enable the connection.

1. Find the VPC peering connection on the VPC Peering Connection page and click Configure Route in either the Requester VPC or Accepter VPC column.

   

2. Configure the IPv4 or IPv6 route entries for both the requester and accepter VPCs. Below is an example of configuring an IPv4 route entry.

   

   Parameter description

   Parameter	Description
   VPC	The requester VPC instance is automatically displayed.
   Route Table	Select the route table associated with the VPC from the drop-down list.
   Destination CIDR Block	Configure an IPv4 route for the VPC peering connection Select IPv4 as the destination CIDR block type and enter the IPv4 CIDR block of the accepter VPC. Configure an IPv6 route for the VPC peering connection Select IPv6 as the destination CIDR block type and enter the IPv6 CIDR block of the accepter VPC.
   Next Hop	The peering connection is automatically displayed.

Step 3: Associate the VPC of a service with the private zone to which the cluster VPC belongs

EMR does not allow you to associate the VPC of a service with the private zone to which a cluster VPC belongs. You must submit a ticket on the official website to contact the EMR product after-sales team to associate the VPC of a service with the private zone to which the cluster VPC belongs. After association, the resolution capability of the EMR cluster is empowered to the VPC of the service.

Step 4: Use the node endpoint to access the EMR cluster

1. Log on to the service from which you want to access the EMR cluster. In this example, you need to log on to the desired ECS instance.

2. Run the ping master-1-1.<Cluster-ID>.<Region-ID>.emr.aliyuncs.com command to access the EMR cluster.

If information in the preceding figure is returned, the node endpoint is successfully resolved, and the VPC of the ECS instance and the VPC of the EMR cluster are connected.