Since 2011, Alibaba Cloud has used the classic network to host Elastic Compute Service (ECS) instances and serve many cloud customers. In 2014, Virtual Private Cloud (VPC)-based cloud services were introduced, which are more secure, stable, and flexible. The VPC network has since become the preferred choice for many cloud users. As a result, ApsaraDB for MongoDB will stop offering MongoDB instances on the classic network.
ApsaraDB for MongoDB ended the purchase of new instances on the classic network on February 21, 2022. This change affects all existing instances configured with the classic network. To help minimize the impacts of this change, Alibaba Cloud gives you time to plan, test, and migrate your ApsaraDB for MongoDB instances from the classic network to VPCs before the end of life (EOL) date. Alibaba Cloud also provides tools, guides, and support to help you with the migration.
Dates and impacts
End of renewal, configuration change, and billing method change on October 30, 2024
You cannot renew all ApsaraDB for MongoDB instances in the classic network, change their specifications, or change their billing methods.
NoteAll ApsaraDB for MongoDB instances on the classic network, including instances that allow access over the classic network and VPCs, are affected, even if the instances are not connected by using their classic network endpoints.
Discontinuation of services from 00:00 on February 28, 2025
The system will delete classic network endpoints. If your business is still using classic network endpoints at this time, your business connections will be disconnected and cannot be automatically restored.
If your instance only has classic network endpoints and your account has VPCs, when the classic network endpoints are deleted the network connection may be switched to a random VPC.
The forced disabling of classic networks will be implemented in batches. You will be notified of the specific time of this by SMS, email, and internal message. Before this happens, instances will still be in the stage where you cannot renew or change their configurations.
On February 28, 2025, or after the forced disabling of classic network endpoints, the instances will continue to be billed normally. Release the affected instances if you no longer need them.
ApsaraDB for MongoDB instances deployed solely in VPCs will not be affected by the aforementioned changes.
If you switch the network type of your ApsaraDB for MongoDB instances from classic network to VPC and release the classic network endpoints of the instances before the preceding dates, the instances will not be affected by the aforementioned changes.
Query the affected instances
Query the ApsaraDB for MongoDB instances in the classic network using one of the following methods:
Use the console
Log on to the ApsaraDB for MongoDB console.
In the navigation pane on the left, click Replica Set Instances or Sharded Cluster Instances.
In the upper-left corner of the page, select the resource group and region to which the desired instances belong.
In the instance list, filter by Network Type, select Classic Network, and then click OK.
Use the API
Call the DescribeInstances operation and set the NetworkType parameter to
CLASSICto query all ApsaraDB for MongoDB instances in the classic network in a region.
For instances in hybrid access mode, check your internal messages and emails for the details of the affected instances. After you receive the notification, switch the network type in the console to prevent impacts on your instances. See more details below.
Note: The Network Type value for these instances is displayed as VPC.
Switch the network type of an instance from classic network to VPC
The following methods only apply to ApsaraDB for MongoDB instances that use local disks. If your ApsaraDB for MongoDB instances use cloud disks, submit a ticket to contact technical support personnel for migration assistance.
To avoid business disruption, switch the network type of existing ApsaraDB for MongoDB instances from classic network to VPC before the EOL date.
Method 1: Use this method if you do not want to retain the original classic network endpoint during switching. You will not need to modify the connection string of your client, and the VPC where your instance resides uses the original classic network endpoint. For more information, see Switch the network type of an instance from classic network to VPC.
ImportantThis solution eliminates the need to modify the client connection string for an instance. However, the instance experiences a transient disconnection.
Method 2: Enable the hybrid access feature for your instance. This method lets you can smoothly migrate an instance from the classic network to a VPC without transient disconnections or access interruptions. See Configure a hybrid access solution to switch the network type of an instance from classic network to VPC.
ImportantAlthough your instance does not experience transient disconnections, you must modify the connection string on your client and use the endpoint of the VPC where the instance resides.
If you enabled the hybrid access feature for your instance, release the classic network endpoint of the instance after you complete the service switchover. Here are the methods to release the classic network connection endpoints of your instances:
Console: See Change the retention period of internal endpoints on the classic network of an instance.
API: Call the ModifyDBInstanceNetExpireTime operation and set the ClassicExpendExpiredDays parameter to 0.
FAQ
Why do I receive a notification indicating that the classic network of an instance expires but is not released after I switch the instance to a VPC?
The system does not automatically release the classic network of the instance after the classic network expires. Go to the ApsaraDB for MongoDB console to manually release it. For more information, see Change the retention period of internal endpoints on the classic network of an instance.
Why can't I renew my instance after I switch the instance to a VPC?
You cannot renew an instance that contains classic network endpoints. You can renew the instance only after you release its classic network. For more information, see Change the retention period of internal endpoints on the classic network of an instance.