This topic describes how to use network access control lists (ACLs) to manage the connections between a data center and a virtual private cloud (VPC).

Prerequisites

Before you start, make sure that the following conditions are met:

Background information

A company has created a public-facing Server Load Balancer (SLB) instance and multiple ECS instances. Static pages are hosted on the ECS instances. A listener has been configured for the SLB instance, and the ECS instances are specified as backend servers for the SLB instance. By default, Data Center 1 and Data Center 2 can access the static pages through the public IP address of the SLB instance. To meet business requirements, the company wants to allow Data Center 1 to access the static pages, and forbid Data Center 2 to access the static pages.

The following table lists the public IP addresses of the data centers and SLB instance.
Network Public IP address
Data Center 1 111.XX.XX.111
Data Center 2 222.XX.XX.222
SLB instance 33.XX.XX.33

The preceding figure shows that you can associate a network ACL with the vSwitch to which the ECS instances belong. You can configure network ACL rules to manage inbound and outbound network traffic transmitted through the vSwitch.

The following flowchart shows the configuration process.

Step 1: Create a network ACL

  1. Log on to the VPC console.
  2. In the left-side navigation pane, click Network ACL.
  3. In the top navigation bar, select the region where you want to create the network ACL.
  4. On the Network ACL page, click Create Network ACL.
  5. In the Create Network ACL dialog box, set the following parameters, and click OK.
    • VPC: Select the VPC for which you want to create the network ACL.
    • Name: Enter a name for the network ACL.

      The name must be 2 to 128 characters in length, and can contain digits, underscores (_), and hyphens (-). It must start with a letter.

    • Description: Enter a description for the network ACL.

      The description must be 2 to 256 characters in length, and cannot start with http:// or https://.

Step 2: Associate the network ACL with a vSwitch

  1. Log on to the VPC console.
  2. In the left-side navigation pane, click Network ACL.
  3. In the top navigation bar, select the region where the network ACL is created.
  4. On the Network ACL page, find the network ACL that you want to manage and click the ID of the network ACL.
  5. On the Resources tab, click Associate vSwitch.
  6. In the Associate vSwitch dialog box, select a vSwitch, and click Associate.

Step 3: Add rules to the network ACL

Add inbound and outbound rules to the network ACL.

  1. Log on to the VPC console.
  2. In the left-side navigation pane, click Network ACL.
  3. In the top navigation bar, select the region where the network ACL is created.
  4. On the Network ACL page, find the network ACL and click Inbound Rule in the Actions column.
  5. On the Inbound Rule tab, click Manage Inbound Rule.
  6. In the Manage Inbound Rule dialog box, set the following parameters, and click OK.
    Priority Rule Name Action Protocol Source IP Addresses Source Port Range
    1 Allow HTTP requests from Data Center 1 Allow TCP The public IP address of Data Center 1. 111.XX.XX.111 is used in this example. 80/80
    3 Drop HTTP requests from Data Center 2 Drop TCP The public IP address of Data Center 2. 222.XX.XX.222 is used in this example. 80/80
    You must add the following inbound rule if the health check feature is enabled for the SLB instance.
    Priority Rule Name Action Protocol Source IP Addresses Source Port Range
    2 Allow health checks Allow ALL The CIDR block used to perform health checks. Set the value to 100.64.0.0/10. -1/-1
  7. Click the Outbound Rule tab, and click Manage Outbound Rule.
  8. In the Manage Outbound Rule dialog box, set the following parameters, and click OK.
    Priority Rule Name Action Protocol Source IP Addresses Source Port Range
    1 Allow HTTP traffic destined for Data Center 1 Allow TCP The public IP address of Data Center 1. 111.XX.XX.111 is used in this example. 80/80
    3 Drop HTTP traffic destined for Data Center 2 Drop TCP The public IP address of Data Center 2. 222.XX.XX.222 is used in this example. 80/80
    You must add the following outbound rule if you enable the health check feature for the SLB instance.
    Priority Rule Name Action Protocol Source IP Addresses Source Port Range
    2 Allow health checks Allow ALL The CIDR block used to perform health checks. Set the value to 100.64.0.0/10. -1/-1

Step 4: Test the connectivity

To test the connectivity between the data centers and SLB instance, perform the following steps:

  1. Open the browser on a computer in Data Center 1.
  2. Enter http://33.XX.XX.33 in the address bar to test the connectivity.
    The result shows that the computer in Data Center 1 can access the static pages on the ECS instances.
  3. Open the browser on a computer in Data Center 2.
  4. Enter http://33.XX.XX.33 in the address bar to test the connectivity.
    The result shows that the computer in Data Center 2 cannot access the static pages on the ECS instances.