Direct Connection/Cross-Region Access

Recent Pages

Direct Connection/Cross-Region Access

Last updated: 2024-08-19 16:20:04

Background
VPC access points provided by the TDMQ for Apache Pulsar only support client access in the same region VPC network. Users accessing through Direct Connect or across regions cannot directly access through the VPC access point.
For users in the above-mentioned access scenario, they need to configure the domain name parsing of the access point to gain access.
Access Through Direct Connect
Step 1: Obtaining the VIP Address of the Cluster Access Point
The current feature has not yet been productized, and the VIP Address can be accessed through submitting a ticket or post-sales architecture.
Step 2: Configuring Domain Name Parsing
Use Private DNS for domain name parsing, and configure the domain name to parse to the VIP provided by the product side.
1. Creating a Private Domain
Click to enter the Private DNS Console, and then click Private Domain List.
﻿
Enter the creation page.
﻿
In section 1, fill in the TDMQ for Apache Pulsar access point domain name.
In section 2, configure the region and VPC network where the client is located.
In section 3, enable recursive parsing of subdomains.
2. Adding Domain Name Parsing Records
After creation, click to enter the created private domain and set the domain name parsing records.
﻿
In section 1, fill in the domain name prefix. It is recommended that the field be cluster id.vpcid.pulsar.ap-region.qcloud.
In section 2, fill in the VIP provided by the product side.
After you fill in the information, save and submit. Then, the client will request verification.
Cross-Region Access
Cross-region access requires using the Cloud Connect Network product to establish a network access channel.
For details on the configuration, please see the Cloud Connect Network Operation Guide, and follow these directions:
1. Create a Cloud Connect Network instance
2. Associating a Network Instance
﻿