Help Center> VPC Endpoint> Getting Started> Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks> Step 1: Buy a VPC Endpoint for Connecting to DNS
Updated on 2024-05-15 GMT+08:00
View PDF

Step 1: Buy a VPC Endpoint for Connecting to DNS

Scenarios

This section describes how to buy a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.

Prerequisites

The required VPC endpoint service is available.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Click Service List and choose Networking > VPC Endpoint.
  1. On the VPC Endpoints page, click Buy VPC Endpoint.

    The Buy VPC Endpoint page is displayed.

    Figure 1 Buy VPC Endpoint (Service Category set to Cloud services)

  2. Configure VPC endpoint parameters.
    Table 1 VPC endpoint parameters

    Parameter

    Description

    Region

    Specifies the region where the VPC endpoint is to be located.

    Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.

    Billing Mode

    Specifies the billing mode of the VPC endpoint. VPC endpoints can be used or deleted at any time.

    VPC endpoints support only pay-per-use billing based on the usage duration.

    Service Category

    There are two options:

    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.

    In this example, select Cloud services.

    Service List

    This parameter is available only when you select Cloud services for Service Category.

    The VPC endpoint service has been created by the O&M personnel and you can directly use it.

    In this example, select com.myhuaweicloud.na-mexico-1.dns.

    Create a Private Domain Name

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name.

    This parameter is mandatory when the VPC endpoint will be used to access an interface VPC endpoint service.

    VPC

    Specifies the VPC where the VPC endpoint is to be deployed.

    Subnet

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    Specifies the subnet where the VPC endpoint is to be located.

    Private IP Address

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.

    This parameter needs to be configured only in some regions. For details, see the information displayed on the console.

    Access Control

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    It controls IP addresses and CIDR blocks that are allowed to access the VPC endpoint.

    • If Access Control is enabled, only IP addresses or CIDR blocks in the whitelist are allowed to access the VPC endpoint.
    • If Access Control is disabled, any IP address or CIDR block can access the VPC endpoint.

    Whitelist

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    Lists the IP addresses or CIDR blocks that are allowed to access the VPC endpoint. You can add a maximum of 20 records.

    Tag

    This parameter is optional.

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.

    Tag keys and values must meet requirements listed in Table 2.

    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    For details about predefined tags, see Overview.

    If you have configured tag policies for VPC endpoints, you need to add tags to this VPC endpoint based on the tag policies. If you add a tag that does not comply with the tag policies, VPC endpoints may fail to be created. Contact your administrator to learn more about tag policies.
    Table 2 Tag requirements for VPC endpoints

    Parameter

    Requirement

    Tag key
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).

    Tag value
    • Cannot be left blank.
    • Can contain a maximum of 43 characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
  3. Confirm the specifications and click Next.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
  4. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes to Accepted, the VPC endpoint for connecting to com.myhuaweicloud.na-mexico-1.dns is created.

  5. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.

    After a VPC endpoint for accessing interface VPC endpoint services is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name during creation.

    Figure 2 Summary of the VPC endpoint