- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Creating Instance
- Naming with Consecutive Numeric Suffixes or Designated Pattern String
- Viewing Instance
- Upgrading Instance
- Downgrading Instance Configuration
- Terminating/Returning Instances
- Change from Pay-as-You-Go to Monthly Subscription
- Upgrading Instance Version
- Adding Routing Policy
- Public Network Bandwidth Management
- Connecting to Prometheus
- AZ Migration
- Setting Maintenance Time
- Setting Message Size
- Topic Management
- Consumer Group
- Monitoring and Alarms
- Smart Ops
- Permission Management
- Tag Management
- Querying Message
- Event Center
- Migration to Cloud
- Data Compression
- Instance Management
- CKafka Connector
- Best Practices
- Connector Best Practices
- Connecting Flink to CKafka
- Connecting Schema Registry to CKafka
- Connecting Spark Streaming to CKafka
- Connecting Flume to CKafka
- Connecting Kafka Connect to CKafka
- Connecting Storm to CKafka
- Connecting Logstash to CKafka
- Connecting Filebeat to CKafka
- Multi-AZ Deployment
- Production and Consumption
- Log Access
- Replacing Supportive Route (Old)
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- DataHub APIs
- ACL APIs
- Topic APIs
- BatchModifyGroupOffsets
- BatchModifyTopicAttributes
- CreateConsumer
- CreateDatahubTopic
- CreatePartition
- CreateTopic
- CreateTopicIpWhiteList
- DeleteTopic
- DeleteTopicIpWhiteList
- DescribeDatahubTopic
- DescribeTopic
- DescribeTopicAttributes
- DescribeTopicDetail
- DescribeTopicProduceConnection
- DescribeTopicSubscribeGroup
- FetchMessageByOffset
- FetchMessageListByOffset
- ModifyDatahubTopic
- ModifyTopicAttributes
- DescribeTopicSyncReplica
- Instance APIs
- Route APIs
- Other APIs
- Data Types
- Error Codes
- SDK Documentation
- General References
- FAQs
- Service Level Agreement (New Version)
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Creating Instance
- Naming with Consecutive Numeric Suffixes or Designated Pattern String
- Viewing Instance
- Upgrading Instance
- Downgrading Instance Configuration
- Terminating/Returning Instances
- Change from Pay-as-You-Go to Monthly Subscription
- Upgrading Instance Version
- Adding Routing Policy
- Public Network Bandwidth Management
- Connecting to Prometheus
- AZ Migration
- Setting Maintenance Time
- Setting Message Size
- Topic Management
- Consumer Group
- Monitoring and Alarms
- Smart Ops
- Permission Management
- Tag Management
- Querying Message
- Event Center
- Migration to Cloud
- Data Compression
- Instance Management
- CKafka Connector
- Best Practices
- Connector Best Practices
- Connecting Flink to CKafka
- Connecting Schema Registry to CKafka
- Connecting Spark Streaming to CKafka
- Connecting Flume to CKafka
- Connecting Kafka Connect to CKafka
- Connecting Storm to CKafka
- Connecting Logstash to CKafka
- Connecting Filebeat to CKafka
- Multi-AZ Deployment
- Production and Consumption
- Log Access
- Replacing Supportive Route (Old)
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- DataHub APIs
- ACL APIs
- Topic APIs
- BatchModifyGroupOffsets
- BatchModifyTopicAttributes
- CreateConsumer
- CreateDatahubTopic
- CreatePartition
- CreateTopic
- CreateTopicIpWhiteList
- DeleteTopic
- DeleteTopicIpWhiteList
- DescribeDatahubTopic
- DescribeTopic
- DescribeTopicAttributes
- DescribeTopicDetail
- DescribeTopicProduceConnection
- DescribeTopicSubscribeGroup
- FetchMessageByOffset
- FetchMessageListByOffset
- ModifyDatahubTopic
- ModifyTopicAttributes
- DescribeTopicSyncReplica
- Instance APIs
- Route APIs
- Other APIs
- Data Types
- Error Codes
- SDK Documentation
- General References
- FAQs
- Service Level Agreement (New Version)
- Contact Us
- Glossary
A region is the physical location of an IDC. Availability zone (AZ) refers to the physical IDC of Tencent Cloud in the same region with independent power supplies and network resources. For more information, see Regions and AZs.
Supported Regions
China
Region | Code | |
South China | Guangzhou | ap-guangzhou |
| Shenzhen | ap-shenzhen |
| | |
East China | Shanghai | ap-shanghai |
| | |
| Nanjing | ap-nanjing |
| Hangzhou | ap-hangzhou |
North China | Beijing | ap-beijing |
| | |
| Tianjin | ap-tianjin |
Central China | Changsha | ap-changsha |
Southwest China | Chengdu | ap-chengdu |
| Chongqing | ap-chongqing |
Hong Kong/Macao/Taiwan (China) | Taipei (China) | ap-taipei |
| Hong Kong (China) | ap-hongkong |
Other countries and regions
Region | Code | |
Southeast Asia | Singapore | ap-singapore |
| Bangkok | ap-bangkok |
| Jakarta | ap-jakarta |
South Asia | Mumbai | ap-mumbai |
Northeast Asia | Seoul | ap-seoul |
| Tokyo | ap-tokyo |
West US | Silicon Valley | na-siliconvalley |
East US | Virginia | na-ashburn |
North America | Toronto | na-toronto |
South America | São Paulo | sa-saopaulo |
Europe | Frankfurt | eu-frankfurt |
Selection of Regions and AZs
When selecting a region and AZ, take the following into consideration:
The geographic locations of CKafka instances, your business, and your target users:
We recommend that you choose the region closest to your end users when purchasing CKafka instances to minimize access latency and improve access speed.
Relationship between CKafka and other Tencent Cloud services:
When you select other Tencent Cloud services, we recommend that you try to locate them all in the same region and AZ to allow them to communicate with each other through the private network, reducing access latency and increasing access speed.
High availability and disaster recovery.
Even if you have just one VPC, we still recommend that you deploy your businesses in different AZs to prevent a single point of failure and enable cross-AZ disaster recovery.
There may be network latency among different AZs. We recommend that you assess your business requirements and find the optimal balance between high availability and low latency.
If you need access to CKafka instances in other countries or regions, we recommend that you select an instance in those other countries or regions. If you use a CKafka instance in China to access servers in other countries or regions, you may encounter a high higher network latency.
Resource Availability
The following table describes global, regional, and AZ-specific CKafka resources.
Resource | Resource ID Format (8-Digit String of Numbers and Letters) | Type | Description |
User account | Unlimited | Globally unique | Users can use the same account to access Tencent Cloud resources from around the world. |
CKafka instance | ckafka-xxxxxxxx | CKafka instances can only be used in a single AZ of a single region. | CKafka instances can only be created in a specific AZ. |
Related Operations
Migrating instance to another AZ
CKafka supports instance migration across AZs in the same region. If you need this, submit a ticket for assistance.
Yes
No
Was this page helpful?