As of February 21, 2022, new ApsaraDB for MongoDB instances cannot use classic network. For existing instances that use classic network, you can change the network type to VPC or continue to use classic network.

Release date

February 21, 2022

Coverage

ApsaraDB for MongoDB replica set and sharded cluster instances.
Note ApsaraDB for MongoDB standalone and serverless instances only can use VPC.

Changes

As of February 21, 2022, the following changes have been made to new ApsaraDB for MongoDB instances:
Item Original network type New network type
Network type Both classic network and VPC are available.
  • Classic network: In the classic network, you can block unauthorized traffic only by configuring security groups or IP address whitelists.
  • VPC: A VPC is an isolated virtual network that provides higher security and higher performance than the classic network.
Only VPC is available.

Impacts

  • New ApsaraDB for MongoDB replica set and sharded cluster instances cannot use classic network, but VPC.
  • Existing instances that use classic network are not affected. You can change the network type to VPC or continue to use classic network.

Suggestions

If you have applications deployed on an ECS instance, you must ensure that the ApsaraDB for MongoDB instance and ECS instance are of the same network type to implement network connectivity.

Operation Description
Create an instance When you purchase a new replica set instance and a sharded cluster instance, set network type to VPC.
Change the network type from classic network to VPC
Change the expiration period of the classic network endpoint for the ApsaraDB for MongoDB instance You can change the expiration period of the classic network endpoint for the ApsaraDB for MongoDB instance. For more information, see Change the retention period of internal endpoints on the classic network of an ApsaraDB for MongoDB instance.