Billing for PolarDB for MySQL edge clusters-Edge Node Service(ENS)-阿里云帮助中心

Billing method

PolarDB for MySQL on ENS supports only one billing method: subscription.

Subscription: This is a prepaid method. When you create a cluster, you select a fixed resource configuration and pay for the cluster in advance. The longer the subscription period, the greater the discount. This method is ideal for stable, long-term workloads.

Billable items

Charges for a PolarDB for MySQL edge cluster include compute nodes, storage space, and backup storage.

Compute node

Pricing for a single compute node:

Haikou telecom

CPU architecture	Specification code CPU and memory	Price (CNY/month)
X86 (general-purpose)	polar.mysql.g1.tiny.c 1 core 1 GB	11
	polar.mysql.g1.small.c 1 core 2 GB	18
	polar.mysql.g2.small.c 2 cores 4 GB	225
	polar.mysql.g4.medium.c 2 cores 8 GB	260
	polar.mysql.g8.medium.c 2 cores 16 GB	440
	polar.mysql.g2.large.c 4 cores 8 GB	450
	polar.mysql.g4.large.c 4 cores 16 GB	660
	polar.mysql.g8.large.c 4 cores 32 GB	880
	polar.mysql.g2.xlarge.c 8 cores 16 GB	1,035
	polar.mysql.g4.xlarge.c 8 cores 32 GB	1,330
	polar.mysql.g8.xlarge.c 8 cores 64 GB	1,760
	polar.mysql.g2.2xlarge.c 16 cores 32 GB	2,070
	polar.mysql.g4.2xlarge.c 16 cores 64 GB	2,660
	polar.mysql.g8.2xlarge.c 16 cores 128 GB	3,520
X86 (dedicated)	polar.mysql.x4.medium.c 2 cores 8 GB	270
	polar.mysql.x8.medium.c 2 cores 16 GB	490
	polar.mysql.x2.large.c 4 cores 8 GB	605
	polar.mysql.x4.large.c 4 cores 16 GB	765
	polar.mysql.x8.large.c 4 cores 32 GB	980
	polar.mysql.x2.xlarge.c 8 cores 16 GB	1,200
	polar.mysql.x4.xlarge.c 8 cores 32 GB	1,520
	polar.mysql.x8.xlarge.c 8 cores 64 GB	1,930
	polar.mysql.x2.2xlarge.c 16 cores 32 GB	2,400
	polar.mysql.x4.2xlarge.c 16 cores 64 GB	3,000
	polar.mysql.x8.2xlarge.c 16 cores 128 GB	3,800
	polar.mysql.x2.4xlarge.c 32 cores 64 GB	4,730
	polar.mysql.x4.4xlarge.c 32 cores 128 GB	5,880
	polar.mysql.x8.4xlarge.c 32 cores 256 GB	7,610
	polar.mysql.x4.8xlarge.c 64 cores 256 GB	11,600
	polar.mysql.x8.8xlarge.c 64 cores 512 GB	14,880

China (Macao)

CPU architecture	Instance type CPU and memory	Price (CNY/month)
X86 (dedicated)	polar.mysql.x4.medium.c 2 cores 8 GB	513
	polar.mysql.x8.medium.c 2 cores 16 GB	931
	polar.mysql.x2.large.c 4 cores 8 GB	1,150
	polar.mysql.x4.large.c 4 cores 16 GB	1,454
	polar.mysql.x8.large.c 4 cores 32 GB	1,862
	polar.mysql.x2.xlarge.c 8 cores 16 GB	2,280
	polar.mysql.x4.xlarge.c 8 cores 32 GB	2,888
	polar.mysql.x8.xlarge.c 8 cores 64 GB	3,667
	polar.mysql.x2.2xlarge.c 16 cores 32 GB	4,560
	polar.mysql.x4.2xlarge.c 16 cores 64 GB	5,700
	polar.mysql.x8.2xlarge.c 16 cores 128 GB	7,220
	polar.mysql.x2.4xlarge.c 32 cores 64 GB	8,987
	polar.mysql.x4.4xlarge.c 32 cores 128 GB	11,172
	polar.mysql.x8.4xlarge.c 32 cores 256 GB	14,459
	polar.mysql.x4.8xlarge.c 64 cores 256 GB	22,070
	polar.mysql.x8.8xlarge.c 64 cores 512 GB	28,272
X86 (general-purpose)	polar.mysql.g1.tiny.c 1 core 1 GB	18
	polar.mysql.g1.small.c 1 core 2 GB	34
	polar.mysql.g2.small.c 2 cores 4 GB	427.5
	polar.mysql.g4.medium.c 2 cores 8 GB	494
	polar.mysql.g8.medium.c 2 cores 16 GB	836
	polar.mysql.g2.large.c 4 cores 8 GB	855
	polar.mysql.g4.large.c 4 cores 16 GB	1,254
	polar.mysql.g8.large.c 4 cores 32 GB	1,672
	polar.mysql.g2.xlarge.c 8 cores 16 GB	1,967
	polar.mysql.g4.xlarge.c 8 cores 32 GB	2,527
	polar.mysql.g8.xlarge.c 8 cores 64 GB	3,344
	polar.mysql.g2.2xlarge.c 16 cores 32 GB	3,933
	polar.mysql.g4.2xlarge.c 16 cores 64 GB	5,054
	polar.mysql.g8.2xlarge.c 16 cores 128 GB	6,688

Turkey (Istanbul)

CPU architecture	Parameter CPU and memory	Price (CNY/month)
X86 (dedicated)	polar.mysql.x4.medium.c 2 cores 8 GB	459
	polar.mysql.x8.medium.c 2 cores 16 GB	833
	polar.mysql.x2.large.c 4 cores 8 GB	1,028.50
	polar.mysql.x4.large.c 4 cores 16 GB	1,300.50
	polar.mysql.x8.large.c 4 cores 32 GB	1,666
	polar.mysql.x2.xlarge.c 8 cores 16 GB	2,040
	polar.mysql.x4.xlarge.c 8 cores 32 GB	2,584
	polar.mysql.x8.xlarge.c 8 cores 64 GB	3,281
	polar.mysql.x2.2xlarge.c 16 cores 32 GB	4,080
	polar.mysql.x4.2xlarge.c 16 cores 64 GB	5,100
	polar.mysql.x8.2xlarge.c 16 cores 128 GB	6,460
	polar.mysql.x2.4xlarge.c 32 cores 64 GB	8,041
	polar.mysql.x4.4xlarge.c 32 cores 128 GB	9,996
	polar.mysql.x8.4xlarge.c 32 cores 256 GB	12,937
	polar.mysql.x4.8xlarge.c 64 cores 256 GB	19,720
	polar.mysql.x8.8xlarge.c 64 cores 512 GB	25,296
X86 (general-purpose)	polar.mysql.g1.tiny.c 1 core 1 GB	18.70
	polar.mysql.g1.small.c 1 core 2 GB	30.60
	polar.mysql.g2.small.c 2 cores 4 GB	382.50
	polar.mysql.g4.medium.c 2 cores 8 GB	442
	polar.mysql.g8.medium.c 2 cores 16 GB	748
	polar.mysql.g2.large.c 4 cores 8 GB	765
	polar.mysql.g4.large.c 4 cores 16 GB	1,122
	polar.mysql.g8.large.c 4 cores 32 GB	1,496
	polar.mysql.g2.xlarge.c 8 cores 16 GB	1,759.5
	polar.mysql.g4.xlarge.c 8 cores 32 GB	2,261
	polar.mysql.g8.xlarge.c 8 cores 64 GB	2,992
	polar.mysql.g2.2xlarge.c 16 cores 32 GB	3,519
	polar.mysql.g4.2xlarge.c 16 cores 64 GB	4,522
	polar.mysql.g8.2xlarge.c 16 cores 128 GB	5,984

Vietnam (Hanoi) zone C

CPU architecture	Instance type CPU and memory	Price (CNY/month)
X86 (dedicated)	polar.mysql.x4.medium.c 2 cores 8 GB	513
	polar.mysql.x8.medium.c 2 cores 16 GB	931
	polar.mysql.x2.large.c 4 cores 8 GB	1,150
	polar.mysql.x4.large.c 4 cores 16 GB	1,454
	polar.mysql.x8.large.c 4 cores 32 GB	1,862
	polar.mysql.x2.xlarge.c 8 cores 16 GB	2,280
	polar.mysql.x4.xlarge.c 8 cores 32 GB	2,888
	polar.mysql.x8.xlarge.c 8 cores 64 GB	3,667
	polar.mysql.x2.2xlarge.c 16 cores 32 GB	4,560
	polar.mysql.x4.2xlarge.c 16 cores 64 GB	5,700
	polar.mysql.x8.2xlarge.c 16 cores 128 GB	7,220
	polar.mysql.x2.4xlarge.c 32 cores 64 GB	8,987
	polar.mysql.x4.4xlarge.c 32 cores 128 GB	11,172
	polar.mysql.x8.4xlarge.c 32 cores 256 GB	14,459
	polar.mysql.x4.8xlarge.c 64 cores 256 GB	22,070
	polar.mysql.x8.8xlarge.c 64 cores 512 GB	28,272
X86 (general-purpose)	polar.mysql.g1.tiny.c 1 core 1 GB	18
	polar.mysql.g1.small.c 1 core 2 GB	34
	polar.mysql.g2.small.c 2 cores 4 GB	427.5
	polar.mysql.g4.medium.c 2 cores 8 GB	494
	polar.mysql.g8.medium.c 2 cores 16 GB	836
	polar.mysql.g2.large.c 4 cores 8 GB	855
	polar.mysql.g4.large.c 4 cores 16 GB	1,254
	polar.mysql.g8.large.c 4 cores 32 GB	1,672
	polar.mysql.g2.xlarge.c 8 cores 16 GB	1,967
	polar.mysql.g4.xlarge.c 8 cores 32 GB	2,527
	polar.mysql.g8.xlarge.c 8 cores 64 GB	3,344
	polar.mysql.g2.2xlarge.c 16 cores 32 GB	3,933
	polar.mysql.g4.2xlarge.c 16 cores 64 GB	5,054
	polar.mysql.g8.2xlarge.c 16 cores 128 GB	6,688

Storage space

Storage type		Price (CNY/GB/month)
		Haikou Telecom	China (Macao)	Türkiye (Istanbul)	Vietnam (Hanoi)
ESSD PL0	dual-availability zone (hot standby storage cluster enabled)	0.80	0.80	1.36	0.80
	dual-availability zone (hot standby storage and compute clusters enabled)
	three-availability zone (hot standby storage cluster and logger node enabled)
	single-availability zone (hot standby storage cluster disabled)	0.50	0.50	0.85	0.50
ESSD PL1	dual-availability zone (hot standby storage cluster enabled)	1.60	1.60	2.72	1.60
	dual-availability zone (hot standby storage and compute clusters enabled)
	three-availability zone (hot standby storage cluster and logger node enabled)
	single-availability zone (hot standby storage cluster disabled)	1.00	1.00	1.70	1.00

Backup storage

Backup storage for a PolarDB for MySQL edge cluster is currently free of charge.

Expiration policy

Renew your PolarDB for MySQL edge cluster before it expires to avoid service disruptions. You can perform a manual renewal or enable auto-renewal.

Time point	Cluster status	Billing and retention	Recovery options
On the expiration date	The cluster is shut down, locked, and cannot be accessed.	Compute nodes, storage space, and backup storage: No fees are charged.	You can perform a manual renewal to unlock the cluster.
8 days after expiration (7 days after shutdown)	The cluster is released. Note Alibaba Cloud sends you a reminder by SMS or email one day before the cluster is released.	After the cluster is released, the data retention policy is as follows: If your cluster's backup policy is set to Retain This Backup Set For A Long Term (a full backup is performed before release) or Retain All Backup Sets For A Long Term, the cluster's data is retained in the cluster recycle bin, and corresponding backup storage fees will apply. If the cluster's backup policy is set to Immediately Delete All Backup Sets, the cluster and its data are permanently deleted and cannot be recovered. No fees are charged.	If the cluster is moved to the cluster recycle bin after release, you can recover a released cluster using its backup set.

Renewal

Subscription clusters have an expiration date. Failure to renew a cluster before it expires can cause service interruptions or data loss. To continue using the cluster, you must renew it within the specified timeframe.

Considerations

Type	Description
auto-renewal	With auto-renewal enabled, the system extends the subscription for the same duration as the original purchase term. For example, a cluster purchased with a three-month subscription is renewed for three-month periods. The first payment attempt occurs at 08:00 (UTC+8), nine days before the cluster expires. If the payment fails, the system retries daily until the payment is successful or until one day before expiration. Ensure your account has a sufficient balance. Note If your cluster expires tomorrow, the system will not trigger auto-renewal. You must use manual renewal. If you manually renew your cluster before the first automatic payment attempt, the next auto-renewal cycle will align with the new expiration date. If you enable auto-renewal today, it takes effect the next day.
manual renewal	You can manually renew your cluster at any time before it expires to prevent service interruptions. If a cluster has already expired, you can still manually renew it before it is released to restore the service.

Auto-renewal

Enable auto-renewal

When you purchase a subscription cluster, select the Auto-renewal checkbox.
Navigate to Expenses and Costs > Order > Resource Renewal. On the Manual Renewal or Nonrenewal tab, find the cluster, and in the Operation column, click Enable Auto-renewal.

Note
If you cannot find the cluster, check the Auto tab. Auto-renewal may already be enabled for the cluster.

Modify auto-renewal period

Navigate to Expenses and Costs > Order > Resource Renewal. On the Auto tab, find the cluster, and in the Operation column, click Edit Auto-renewal.

Disable auto-renewal

Navigate to Expenses and Costs > Order > Resource Renewal. On the Auto tab, find the cluster, and in the Operation column, click Enable Manual Renewal.

Manual renewal

Go to the PolarDB for ENS console. Find the target cluster, and in the Operation column, click More > Renew.
Navigate to Expenses and Costs > Order > Resource Renewal. On the Manual Renewal, Auto-renewal, or Disable Renewal tab, find the cluster, and in the Operation column, click Renew.