Quickstart for Anycast EIP

Procedure

Quick deployment

To quickly create an Anycast EIP instance and bind a resource to it, you can use Terraform.

Step 1: Create an Anycast EIP instance

After you create an Anycast EIP instance, the system assigns it a public IP address. Users can access your services through this IP address.

1. Log on to the Anycast EIP console.

2. On the Anycast Elastic IP Addresses page, click Purchase Anycast EIP.

3. If this is your first time purchasing an Anycast EIP, the billing of Anycast EIP is managed by Cloud Data Transfer (CDT). You must first activate CDT.

   1. Read and select the Terms of Service, and then click Activate Now.

   2. In the dialog box that appears, click Continue to Purchase.

   Note

   If you used Anycast elastic IP addresses (Anycast EIPs) and did not activate Cloud Data Transfer (CDT) before 00:00:00 (UTC+8) on June 1, 2023, Anycast EIPs use the pay-by-data-transfer metering method by default. For more information, see Billing.

   To activate CDT, go to the CDT page. For more information about CDT, see Internet traffic and Inter-region traffic.

4. On the purchase page, configure the parameters and click Activate Now.

   Parameter	Description
   Region	Select a region. The default value is Areas Outside Chinese Mainland.
   Instance type	Select an instance type. The default type is Standard.
   Billing method	Select a billing method. The default method is pay-by-data-transfer. For more information, see Billing.
   Maximum bandwidth	Specify the maximum bandwidth for the instance. Note The maximum bandwidth is a limit, not a guarantee. Bandwidth may be throttled during periods of high resource contention.
   Resource Group	Select the resource group to which the Anycast EIP belongs. The resource group must be created in Resource Management by the current Alibaba Cloud account. For more information, see Create a resource group.
   Name	Enter a name for the Anycast EIP.
   Quantity	Specify the number of Anycast EIPs that you want to purchase.

Step 2: Bind a resource

After creating the instance, you must bind it to a backend resource. Once bound, client traffic sent to the Anycast EIP is routed to the resource.

1. Log on to the Anycast EIP console.

2. On the Anycast Elastic IP Addresses page, find the Anycast EIP and click Actions in the Manage column.

3. On the Anycast EIP details page, on the Bound Instances tab, click Associate with Resource.

4. In the Associate Anycast EIP with Resource dialog box, configure the parameters and click OK.

   Parameter	Description
   Instance Type	Select the type of cloud resource. SLB Instance (default) ENI Important You can associate an Anycast EIP with only one cloud resource in a region. You can associate an Anycast EIP only with Classic Load Balancer (CLB) instances deployed in a VPC. If you select ENI, the elastic network interface must be attached to an ECS instance and not associated with a public IP address. Otherwise, the association fails.
   Resource Group	Select the cloud resource's resource group.
   Set as Default	Determines if the cloud resource is the default endpoint. Requests from unmapped access points are routed to the default endpoint. Yes: Sets this cloud resource as the default endpoint. No: Sets this cloud resource as a regular endpoint.
   Region	Select the cloud resource's region. This is the endpoint region. Supported endpoint regions include China (Hong Kong), Japan (Tokyo), Singapore, US (Silicon Valley), US (Virginia), and Germany (Frankfurt).
   Areas	Specifies the access points for the endpoint region. This allows you to map access points to an endpoint. This parameter is available only when you set Set as Default to No.
   Select an instance to associate	Select the target resource instance.

Step 3: Test the configuration

After completing the configuration, you can test the public network performance.

1. Open the command-line interface (CLI) on a computer in an access location.

2. Run the following command to check the packet latency.

   curl -o /dev/null -s -w "time_connect: %{time_connect}\ntime_starttransfer: %{time_starttransfer}\ntime_total: %{time_total}\n" "<IP_address_to_access>"

   Description of parameters:

   • time_connect: The time, in seconds, from the start until the TCP connection is established.

   • time_starttransfer: The time, in seconds, from the start of the request until the first byte is received from the backend server.

   • time_total: The total time, in seconds, from the start of the request until the entire response is received.

   The test result shows that using an Anycast EIP reduces the latency when you access the application service on the server in Singapore.

   C:\Users\wb-zxxx>curl -o /dev/null -s -w "time_connect: %{time_connect}\ntime_starttransfer: %{time_starttransfer}\ntime_total: %{time_total}\n" "139.xxx.184"
   time_connect: 0.563000
   time_starttransfer: 2.297000
   time_total: 2.297000