Some ApsaraDB services support hybrid access, which allows access from Elastic Compute Service (ECS) instances in classic networks and in virtual private clouds (VPCs). When you use the hybrid access solution to migrate services from classic networks to VPCs, you must switch the ApsaraDB service to the hybrid access mode. In this mode, the endpoints of classic networks and VPCs are retained, which prevents service interruptions during the migration.
When you switch the network type, you can specify the time period during which the endpoints of classic networks are retained. The endpoints of classic networks are automatically deleted upon expiration.
Type | Note | |
ApsaraDB services support hybrid access | ApsaraDB RDS for MySQL, SQL Server, and PostgreSQL in enhanced whitelist mode | You can use the console or call API operations to switch the network type. The domain name of the classic network remains unchanged during the switch. A VPC domain name is added after the switch. You can view the endpoints of the classic network and VPC in the console. |
Tair (Redis OSS-compatible) | ||
ApsaraDB for MongoDB (replica set architecture) | ||
ApsaraDB for Memcache (purchased after May 12, 2017) | To switch the network type, call an API operation. If you switch the network type in the console, the endpoints of classic networks cannot be retained. The domain name of the classic network remains unchanged during the switch. A VPC domain name is added after the switch. You can view only the endpoints of VPCs in the console. To view the endpoints of classic networks, call an API operation. | |
ApsaraDB services do not support hybrid access | ApsaraDB RDS in standard network mode | Before you switch the network type, switch to the enhanced whitelist mode. |
ApsaraDB for MongoDB (cluster architecture) | ||
ApsaraDB for Memcache (purchased before May 12, 2017) | To switch the network type, use ApsaraDB for Memcache purchased after May 12, 2017. |