EOL notice for Alibaba Cloud resources in the classic network
Jul 26, 2024
Elastic Compute Service
Since the Alibaba Cloud public cloud was released in 2011, the classic network architecture is used to host various Alibaba Cloud services, such as Elastic Compute Service (ECS), Server Load Balancer (SLB), ApsaraDB RDS, ApsaraDB for Redis, and ApsaraDB for MongoDB, and serve numerous users in the cloud. In 2014, Alibaba Cloud released Virtual Private Cloud (VPC) based services, which are more secure, consistent, flexible, and performant than classic network-based services. After years, the VPC network architecture increasingly became the default choice for Alibaba Cloud users. In light of this, Alibaba Cloud starts the end of life (EOL) process for Alibaba Cloud services in the classic network.
To help minimize the impacts on your workloads, Alibaba Cloud provides sufficient time prior to the EOL dates to allow you to devise, test, and execute plan for migrating Alibaba Cloud resources from the classic network to VPCs. Alibaba Cloud provides the necessary migration tools, help documents, and technical support to assist in your migration.
Take note that the EOL does not affect Alibaba Cloud resources, such as ECS instances, that are deployed in VPCs.
Schedule and impacts
00:00:00 on August 27, 2024 (UTC+8): start time of limited sales. Subscription resources that are deployed in the classic network in all regions will reach end of sale (EOS) at 00:00:00 on August 27, 2024 (UTC+8). You can continue to purchase subscription resources that are deployed in VPCs or pay-as-you-go resources that are deployed in the classic network.
00:00:00 on September 24, 2024 (UTC+8): EOS. Alibaba Cloud resources, including pay-as-you-go resources, that are deployed in the classic network in all regions will reach EOS at 00:00:00 on September 24, 2024 (UTC+8). No Alibaba Cloud accounts can create resources in the classic network since then.
00:00:00 on October 30, 2024 (UTC+8): end of configuration change. Starting 00:00:00 on October 30, 2024 (UTC+8), you can no longer renew or change the configurations of resources that are deployed in the classic network in any regions.
00:00:00 on February 28, 2025 (UTC+8): EOL. Pay-as-you-go and expired subscription resources that are deployed in the classic network in all regions will be forcefully stopped and released at 00:00:00 on February 28, 2025 (UTC+8). At the same time, unexpired subscription resources that are deployed in the classic network will be stopped. All business hosted on the preceding resources will be stopped.
Affected resources
Check for and migrate all the following Alibaba Cloud resources from the classic network to VPCs:
● ECS instances in the classic network that are in the Running or Stopped state
● NAS file systems in the classic network that are mounted and are in the Running or Stopped state
● ApsaraDB RDS instances in the classic network that are in the Running or Stopped state
● PolarDB for MySQL clusters in the classic network that are in the Running or Stopped state
● PolarDB for Xscale instances in the classic network that are in the Running or Stopped state
● ApsaraDB for Redis instances in the classic network that are in the Running or Stopped state
● ApsaraDB for MongoDB instances in the classic network that are in the Running or Stopped state
● ApsaraDB for HBase clusters in the classic network that are in the Running or Stopped state
EOL option
To prevent your business from being affected, we recommend that you migrate Alibaba Cloud services from the classic network to VPCs. Compared with Alibaba Cloud services that are deployed in the classic network, Alibaba Cloud services that are deployed in VPCs are more secure, support more features and instance types, and are more flexible to use in cloud computing scenarios.
The following table lists the Alibaba Cloud services that you must migrate from the classic network to VPCs. To view the EOL dates and migration methods for each service, click the link in the References column.
ECS:https://www.alibabacloud.com/help/en/ecs/product-overview/end-of-sale-announcement-for-ecs-instances-of-the-classic-network-type
Apsara File Storage NAS:https://www.alibabacloud.com/help/en/nas/user-guide/switch-the-nas-instance-from-a-classic-network-to-a-vpc-mount-point
ApsaraDB RDS:https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/eol-for-apsaradb-rds-instances-of-the-classic-network-type
ApsaraDB for Redis:https://www.alibabacloud.com/help/en/redis/product-overview/notice-apsaradb-for-redis-instances-deployed-in-classic-network-discontinued
ApsaraDB for MongoDB:https://www.alibabacloud.com/help/en/mongodb/product-overview/eol-notice-for-apsaradb-for-mongodb-instances-in-the-classic-network
PolarDB for MySQL:https://www.alibabacloud.com/help/en/polardb/polardb-for-mysql/polardb-product-offline-classic-network-announcement
PolarDB for Xscale:https://www.alibabacloud.com/help/en/polardb/polardb-for-xscale/polardb-product-offline-classic-network-announcement
ApsaraDB for HBase:https://www.alibabacloud.com/help/en/hbase/product-overview/notice
To help minimize the impacts on your workloads, Alibaba Cloud provides sufficient time prior to the EOL dates to allow you to devise, test, and execute plan for migrating Alibaba Cloud resources from the classic network to VPCs. Alibaba Cloud provides the necessary migration tools, help documents, and technical support to assist in your migration.
Take note that the EOL does not affect Alibaba Cloud resources, such as ECS instances, that are deployed in VPCs.
Schedule and impacts
00:00:00 on August 27, 2024 (UTC+8): start time of limited sales. Subscription resources that are deployed in the classic network in all regions will reach end of sale (EOS) at 00:00:00 on August 27, 2024 (UTC+8). You can continue to purchase subscription resources that are deployed in VPCs or pay-as-you-go resources that are deployed in the classic network.
00:00:00 on September 24, 2024 (UTC+8): EOS. Alibaba Cloud resources, including pay-as-you-go resources, that are deployed in the classic network in all regions will reach EOS at 00:00:00 on September 24, 2024 (UTC+8). No Alibaba Cloud accounts can create resources in the classic network since then.
00:00:00 on October 30, 2024 (UTC+8): end of configuration change. Starting 00:00:00 on October 30, 2024 (UTC+8), you can no longer renew or change the configurations of resources that are deployed in the classic network in any regions.
00:00:00 on February 28, 2025 (UTC+8): EOL. Pay-as-you-go and expired subscription resources that are deployed in the classic network in all regions will be forcefully stopped and released at 00:00:00 on February 28, 2025 (UTC+8). At the same time, unexpired subscription resources that are deployed in the classic network will be stopped. All business hosted on the preceding resources will be stopped.
Affected resources
Check for and migrate all the following Alibaba Cloud resources from the classic network to VPCs:
● ECS instances in the classic network that are in the Running or Stopped state
● NAS file systems in the classic network that are mounted and are in the Running or Stopped state
● ApsaraDB RDS instances in the classic network that are in the Running or Stopped state
● PolarDB for MySQL clusters in the classic network that are in the Running or Stopped state
● PolarDB for Xscale instances in the classic network that are in the Running or Stopped state
● ApsaraDB for Redis instances in the classic network that are in the Running or Stopped state
● ApsaraDB for MongoDB instances in the classic network that are in the Running or Stopped state
● ApsaraDB for HBase clusters in the classic network that are in the Running or Stopped state
EOL option
To prevent your business from being affected, we recommend that you migrate Alibaba Cloud services from the classic network to VPCs. Compared with Alibaba Cloud services that are deployed in the classic network, Alibaba Cloud services that are deployed in VPCs are more secure, support more features and instance types, and are more flexible to use in cloud computing scenarios.
The following table lists the Alibaba Cloud services that you must migrate from the classic network to VPCs. To view the EOL dates and migration methods for each service, click the link in the References column.
ECS:https://www.alibabacloud.com/help/en/ecs/product-overview/end-of-sale-announcement-for-ecs-instances-of-the-classic-network-type
Apsara File Storage NAS:https://www.alibabacloud.com/help/en/nas/user-guide/switch-the-nas-instance-from-a-classic-network-to-a-vpc-mount-point
ApsaraDB RDS:https://www.alibabacloud.com/help/en/rds/apsaradb-rds-for-mysql/eol-for-apsaradb-rds-instances-of-the-classic-network-type
ApsaraDB for Redis:https://www.alibabacloud.com/help/en/redis/product-overview/notice-apsaradb-for-redis-instances-deployed-in-classic-network-discontinued
ApsaraDB for MongoDB:https://www.alibabacloud.com/help/en/mongodb/product-overview/eol-notice-for-apsaradb-for-mongodb-instances-in-the-classic-network
PolarDB for MySQL:https://www.alibabacloud.com/help/en/polardb/polardb-for-mysql/polardb-product-offline-classic-network-announcement
PolarDB for Xscale:https://www.alibabacloud.com/help/en/polardb/polardb-for-xscale/polardb-product-offline-classic-network-announcement
ApsaraDB for HBase:https://www.alibabacloud.com/help/en/hbase/product-overview/notice