Help Center> API Gateway> Best Practices> Exposing Backend Services Across VPCs> Implementation Procedure
Updated on 2023-04-06 GMT+08:00
View PDF

Implementation Procedure

Creating a VPC

  1. Log in to the network console.
  2. In the navigation pane, choose Virtual Private Cloud > My VPCs.
  3. On the Virtual Private Cloud page, click Create VPC, and configure the parameters by referring to Table 1 and Table 2. For details, see sections "Creating a VPC" and "Creating a Subnet for the VPC" in the Virtual Private Cloud User Guide.

    Table 1 Configuration information

    Parameter

    Description

    Region

    Select a region.

    Name

    Enter VPC1. This VPC will be used to run a gateway.

    Enterprise Project

    Select default.

    AZ

    The AZ to which the subnet belongs. Select AZ1.

    Name

    A subnet is automatically created when you create a VPC.
    Table 2 VPC CIDR block planning

    VPC 1

    VPC of APIG

    VPC 2

    10.X

    172.31.0.0/16

    Must be different from VPC 1 and the VPC of the gateway.

    172.X

    192.168.0.0/16

    192.X

    172.31.0.0/16

  4. Click Create Now.
  5. Repeat 3 to 4 to create VPC2 for running your backend service.

Creating a Gateway

  1. Log in to the APIG console.
  2. In the navigation pane, choose Dedicated Gateways.
  3. Click Create Dedicated Gateway.

    Table 3 Gateway information

    Parameter

    Description

    Billing Mode

    Billing mode of the gateway. Select Pay-per-use.

    Region

    Select the region where the gateway is located. It must be the same as the region of VPC 1.

    AZ

    The AZ where the gateway is located. Select AZ1.

    Gateway Name

    Enter a name that conforms to specific rules to facilitate search.

    Edition

    Select Professional. The edition cannot be changed after the gateway is created.

    Scheduled Maintenance

    Select a time period when the gateway can be maintained by technical support engineers. A period with low service traffic is recommended. For this example, retain the default value 22:00:00---02:00:00.

    Enterprise Project

    Select the enterprise project to which the gateway belongs. For this example, retain the default value default.

    Network

    Select VPC 1 and a subnet.

    Security Group

    Click Manage Security Groups and create a security group. Ensure that you have selected default for Enterprise Project.

    Description

    Description of the gateway.

  4. Click Next.
  5. If the gateway configurations are correct, read and confirm your acceptance of the customer agreement and privacy statement, and click Pay Now.

Buying a Load Balancer

  1. Log in to the network console.
  2. In the navigation pane, choose Elastic Load Balance > Load Balancers.
  3. Click Buy Elastic Load Balancer.
  4. Configure the load balancer information. For details, see section Load Balancer in the Elastic Load Balance User Guide.

    Table 4 Load balancer parameters

    Parameter

    Description

    Type

    Type of the load balancer.

    Billing Mode

    By default, Pay-per-use is selected.

    Region

    Select the region where the load balancer is located. It must be the same as the region of VPC 2.

    AZ

    The AZ where the load balancer is located. Select AZ1.

    Network Type

    Select Private IPv4 Network.

    VPC

    Select VPC 2.

    Subnet

    Select a subnet.

    Specification

    Select Network load balancing.

    Name

    Enter a load balancer name that conforms to specific rules to facilitate search.

    Enterprise Project

    Select default.

  5. Click Next.
  6. Confirm the configuration and click Submit.
  7. Add a listener.

    1. Click the name of the load balancer. On the Listeners tab page, click Add Listener.
    2. Configure the listener name, frontend protocol, and port, and click Next.
    3. Configure the backend server group name, backend protocol, and load balancing algorithm. Then click Next.
    4. Add backend servers and click Next.
    5. Click Submit The following figure shows the configuration.
    Figure 1 Listener information
    Figure 2 Backend server group information

Creating a VPC Peering Connection

  1. Log in to the network console.
  2. In the navigation pane, choose Virtual Private Cloud > VPC Peering Connections.
  3. Click Create VPC Peering Connection and configure the parameters.

    Table 5 Configuring a VPC peering connection

    Parameter

    Description

    Name

    Enter a VPC peering connection name that conforms to specific rules to facilitate search.

    Local VPC

    Select VPC 1.

    Account

    By default, My account is selected.

    Peer Project

    Select a project

    Peer VPC

    Select VPC 2.

  4. Click OK.
  5. In the displayed dialog box, click Add Route to go to the VPC peering connection details page.
  6. On the Local Routes tab page, click Route Tables.

    1. Under Routes, click Add Route.
    2. In the displayed dialog box, enter the route information.
      • Destination: Enter the service address displayed on the details page of the load balancer.
      • Next Hop Type: Select VPC peering connection.
    3. Click OK.
    Figure 3 Local routes

  7. Go to the Peer Routes tab page, and click Route Tables.

    1. Under Routes, click Add Route.
    2. In the displayed dialog box, enter the route information.
      • Destination: Enter the private outbound address displayed on the details page of the dedicated gateway.
      • Next Hop Type: Select VPC peering connection.
    3. Click OK.
    Figure 4 Peer routes

Configuring a Route

  1. Log in to the APIG console.
  2. In the navigation pane, choose Dedicated Gateways.
  3. Click the name of the created dedicated gateway or click Access Console.
  4. Click Change in the Routes area, enter the IPv4 CIDR block of VPC 2 where the load balancer you purchased is located.

  5. Click Save.

Creating an API

  1. Log in to the APIG console.
  2. In the navigation pane, choose Dedicated Gateways. Then click a gateway name or click Access Console.
  3. In the navigation pane, choose API Publishing > APIs. Then click Create API.
  4. Configure the basic information and click Next.

    Table 6 Frontend configuration

    Parameter

    Description

    API Name

    Enter a name that conforms to specific rules to facilitate search.

    Group

    The default option is DEFAULT.

    Gateway Response

    Select a response to be displayed if the gateway fails to process an API request.

    The default gateway response is default.

    Authentication Mode

    API authentication mode. Select None.

  5. Define the API request parameters and click Next.

    Table 7 Parameters for defining API requests

    Parameter

    Description

    Domain Name

    The system automatically allocates a debugging domain name to each API group for internal testing. The domain name can be accessed 1000 times a day.

    Protocol

    Request protocol of the API. Set this parameter to HTTPS.

    Path

    Path for requesting the API.

    Method

    Request method of the API. Set this parameter to GET.

  6. Define the backend service parameters and click Next.

    Table 8 Parameters for defining an HTTP/HTTPS backend service

    Parameter

    Description

    Protocol

    Set this parameter to HTTP.

    Method

    Request method of the API. Set this parameter to GET.

    VPC Channel

    Select Skip, and enter the service address of the load balancer you created.

    Path

    Path of the backend service.

  7. Define the response and click Finish.

Buying an ECS

  1. Log in to the cloud server console.
  2. Click Buy ECS.
  3. Configure the basic settings and click Next: Configure Network.

    Table 9 Basic settings

    Parameter

    Description

    Billing Mode

    Select Pay-per-use.

    Region

    Select the region where the ECS is located. It must be the same as the region of VPC 2.

    AZ

    Select the AZ where the ECS is located.

    Specifications

    Select specifications that match your service planning.

    Image

    Select an image that matches your service planning.

  4. Configure the network settings and click Next: Configure Advanced Settings.

    Table 10 Network settings

    Parameter

    Description

    Network

    Select VPC 2 and a subnet.

    Security Group

    Select the security group created for the dedicated gateway.

    EIP

    Select Not required.

  5. Configure advanced settings and click Next: Confirm.

    Table 11 Advanced settings

    Parameter

    Description

    ECS Name

    Enter a name that conforms to specific rules to facilitate search.

    Login Mode

    Credential for logging in to the ECS. The default option is Password.

    Username

    The default user is root.

    Password

    Set a password for logging in to the ECS.

    Confirm Password

    Enter the password again.

  6. Confirm the configuration and select enterprise project default.
  7. Read and confirm your acceptance of the agreement. Then click Submit.

Debugging the API

  1. On the Backend Server Groups tab page of the load balancer, add the ECS.

  2. Start the ECS.
  3. Go to the APIs page of the dedicated gateway, choose API Publishing > APIs, and then choose More > Debug in the row that contains the API you created.
  4. Enter the request parameters and click Send Request.

    If the status code is 200, the debugging is successful.