ApsaraDB for MongoDB discontinues classic network for new instances - ApsaraDB for MongoDB

As of February 21, 2022, ApsaraDB for MongoDB has optimized its network types. You can no longer create new instances in the classic network. Existing instances that run in the classic network are not affected and can either be switched to a Virtual Private Cloud (VPC) or continue to operate in the classic network.

Effective date

February 21, 2022

Scope

ApsaraDB for MongoDB replica set instances and sharded cluster instances.

Note

ApsaraDB for MongoDB standalone instances and serverless instances support only VPCs.

Changes

As of February 21, 2022, the available network type for new ApsaraDB for MongoDB instances has changed:

Item

Before

After

Network type

Both Classic Network and VPC were supported.

Classic Network: Relies on security groups or an IP address whitelist to block unauthorized access.
VPC: An isolated network environment that provides greater security and better performance than the classic network.

Only VPC is supported.

Impact

When you create new ApsaraDB for MongoDB replica set instances or sharded cluster instances, you can no longer select the classic network. Only VPC is available.
This change does not affect your existing classic network instances. You can continue to use them in the classic network or switch their network type to VPC.

Recommendations

If your application is deployed on an ECS instance, you must ensure that your ApsaraDB for MongoDB instance and the ECS instance use the same network type (both in a VPC or both in the classic network) to ensure connectivity.

Actions	Description
Create an instance	When you purchase a new replica set instance or sharded cluster instance, the Network Type is set to VPC.
Switch the network type of an instance from classic network to VPC	We recommend switching existing instances from the classic network to a more secure VPC. For detailed instructions, see Switch the network type of an instance from classic network to VPC. The ApsaraDB for MongoDB hybrid access feature lets you smoothly migrate from the classic network to a VPC without service interruptions. For detailed instructions, see Configure a hybrid access solution to switch the network type of an instance from classic network to VPC.
Modify the expiration time of a classic network endpoint	During the hybrid access period, you can modify the expiration time of the classic network endpoint. For detailed instructions, see Modify the expiration time of a classic network endpoint.