The virtual private cloud (VPC) data channel is a solution of the Data Transmission Service (DTS) that accesses a data source by specifying an elastic network interface (ENI) within the VPC, which can access a database instance by using a private IP address.
Overview
When you connect a database instance in a VPC to DTS over Express Connect, VPN Gateway, or Smart Access Gateway and specify primary and secondary vSwitches, DTS automatically binds an ENI on the primary and secondary vSwitches, during which each ENI occupies one vSwitch IP address. In this way, a VPC data channel is created. You can access the database instance by using the ENI.
Benefits
The network architecture is simpler.
You only need to plan your network and configure the CIDR block of the vSwitch to which an ENI is bound into a route table for the Express Connect circuit and IP address whitelist of a database. In this way, DTS is connected to the database and a VPC data channel is created.
The specified range of the whitelist is narrower.
You only need to configure the CIDR block of the vSwitch to which an ENI is bound into a route table for the Express Connect circuit and the security settings (such as firewall, whitelist, and security group) of the database.
The network troubleshooting is easier.
If a Express Connect circuit is down during connectivity check when you configure a DTS instance, you can use an Elastic Compute Service (ECS) instance on the vSwitch to which an ENI is bound to troubleshoot the connectivity of the database.
Billing
You are not charged for the VPC data channel created by DTS.
Limits
Supported database types
The Database Type that supports the VPC data channel include MySQL, PostgreSQL, SQL Server, Tair/Redis, and Oracle.
Supported access methods
Only Express Connect, VPN Gateway, or Smart Access Gateway is supported.
Supported regions and zones
Region | Zone | ||
Name | ID | Name | ID |
Region | Zone | ||
Name | ID | Name | ID |
China (Hangzhou) | cn-hangzhou | Zone I, Zone J, Zone K | cn-hangzhou-i, cn-hangzhou-j, cn-hangzhou-k |
China (Shanghai) | cn-shanghai | Zone B, Zone G, Zone M, Zone N | cn-shanghai-b, cn-shanghai-g, cn-shanghai-m, cn-shanghai-n |
China (Shenzhen) | cn-shenzhen | Zone D, Zone E | cn-shenzhen-d, cn-shenzhen-e |
China (Qingdao) | cn-qingdao | Zone B, Zone C | cn-qingdao-b, cn-qingdao-c |
China (Zhangjiakou) | cn-zhangbei | Zone A, Zone B, Zone C | cn-zhangbei-a, cn-zhangbei-b, cn-zhangbei-c |
China (Ulanqab) | cn-wulanchabu | Zone A, Zone B | cn-wulanchabu-a, cn-wulanchabu-b |
China (Chengdu) | cn-chengdu | Zone A, Zone B | cn-chengdu-a, cn-chengdu-b |
China (Hong Kong) | cn-hongkong | Zone B, Zone C | cn-hongkong-b, cn-hongkong-c |
Singapore | ap-southeast-1 | Zone A, Zone B | ap-southeast-1a, ap-southeast-1b |
Germany (Frankfurt) | eu-central-1 | Zone A, Zone B | eu-central-1a, eu-central-1b |
US (Virginia) | us-east-1 | Zone A, Zone B | us-east-1a, us-east-1b |
US (Silicon Valley) | us-west-1 | Zone A, Zone B | us-west-1a, us-west-1b |
Japan (Tokyo) | ap-northeast-1 | Zone A, Zone B | ap-northeast-1a, ap-northeast-1b |
Other limits and usage notes
This feature is in canary release and available only to specific customers.
Only the new configuration page supports this feature.
If the Database Type, Access Method, and Instance Region of a database instance to be configured in DTS all meet the requirements of a VPC data channel, and the primary and secondary vSwitches are configured, DTS only supports accessing the database instance over the VPC data channel.
Make sure that the primary and secondary vSwitches reside in different zones to implement disaster recovery for DTS.
