Learn about the billing methods, overdue payment policies, and billing FAQ for Container Service for Kubernetes (ACK) Edge cluster.
Billing
|
Cluster type |
Cluster management fee |
Node management fee |
Cloud resource fees |
|
ACK Edge Pro cluster |
|
|
|
|
ACK Edge Basic cluster |
|
|
|
The billing examples in this topic are for reference only. Actual fees are subject to the prices on the purchase page in the console.
Cluster management fee
ACK Edge integrates Alibaba Cloud capabilities in virtualization, storage, networking, and security to simplify cluster O&M, allowing you to focus on developing and managing containerized applications. Therefore, a cluster management fee is charged for each ACK Edge Pro cluster.
|
Billing method |
Price |
|
Pay-as-you-go |
CNY 0.64/hour per cluster |
Node management fee
ACK Edge supports a wide range of heterogeneous edge node resources, including on-premises data centers, ENS instances, IoT devices, and nodes that use the x86 or ARM architecture. ACK Edge also supports hybrid scheduling of heterogeneous resources. Therefore, a management fee is charged for non-ECS nodes. For example, if a cluster has three nodes with 4 vCPUs and 8 GB of memory (one ECS instance and two ENS instances or on-premises nodes), the management fee is
By default, node management fees are billed on a pay-as-you-go basis. You can also purchase an ACK Edge resource plan to offset these fees.
Pay-as-you-go
|
Billing method |
Price |
|
Pay-as-you-go |
CNY 0.2/vCPU/day |
ACK Edge resource plan
Cloud resource fees
If you use other Alibaba Cloud resources with an ACK Edge cluster, you are charged for these resources based on their respective billing rules. The fees are charged by the providers of these cloud services.
|
Cloud service |
Type |
Description |
Subscription |
Resource plan |
Billing |
|
Required |
Used to create nodes for an ACK Edge cluster. |
Supported |
Not supported |
||
|
Optional |
Used to add edge nodes to an ACK Edge cluster. |
Supported |
Not supported |
||
|
Required |
Used to build the cluster network environment and routing rules. |
Not supported |
Not supported |
||
|
Required |
Used to create a load balancer for the ACK Edge cluster. |
Not supported Note
Starting from December 1, 2024, the subscription billing method is no longer supported for the CLB instances that are associated with the API servers of newly created ACK Edge clusters. For more information, see [Product Announcement] Discontinuation of Subscription Billing for CLB Instances Associated with API Servers of New Clusters. |
Not supported |
||
|
Required |
Used to create nodes and implement auto scaling for an ACK Edge cluster. |
Not supported |
Not supported |
||
|
Recommended |
Provides secure hosting and full lifecycle management for cloud-native assets. |
Supported Note
Container Registry Enterprise Edition instances support only subscription billing. For more information, see Billing of Enterprise Edition instances. |
Not supported |
||
|
Recommended |
Enables communication between cloud resources and the internet. |
Not supported |
Not supported |
||
|
Recommended |
Used to deploy clusters. |
Not supported |
Not supported |
||
|
Recommended |
You can use Service Mesh to implement unified traffic management for applications across multiple clusters. |
Not supported |
Supported Note
See Billing of mesh management (resource plans) and purchase a resource plan that meets your business requirements. |
||
|
Recommended |
Collects and retrieves logs for cluster components and applications. |
Not supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: Purchase resource plans. |
||
|
Recommended |
Monitors the status of cluster nodes and applications. |
Not supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: Billing overview |
||
|
Recommended |
Monitors clusters and generates alerts based on Prometheus. |
Not supported |
Not supported |
||
|
Optional |
Enables internet access for clusters and allows them to pull images over the internet. |
Not supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: NAT Gateway resource plans. |
||
|
Optional |
Monitors runtime security events and alerts for cluster applications. |
Not supported |
Not supported |
||
|
Optional |
Provides file storage for cluster application data. |
Not supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: Purchase resource plans. |
Billing of General-purpose NAS file systems and Billing of Extreme NAS file systems |
|
|
Optional |
Provides object storage for cluster application data. |
Not supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: Purchase resource plans. |
||
|
Optional |
Manages application keys and enables at-rest encryption for ACK Edge Pro clusters. |
Not supported |
Not supported |
||
|
Optional |
Provides backup, disaster recovery, and policy-based archive management. |
Supported |
Supported Note
See the following document and purchase a resource plan that meets your business requirements: Purchase resource plans. |
||
|
Optional |
Builds private network communication channels between VPCs across regions and between VPCs and on-premises data centers. |
Supported Note
Bandwidth plans support the subscription billing method. |
Bandwidth plans are supported. Note
See the following document and select a bandwidth plan that meets your requirements: Use bandwidth plans. |
Overdue payments
If your account balance is insufficient to cover your bill, your ACK Edge cluster becomes overdue. You can no longer access the cluster's API server, but workloads on the nodes can continue to run. If your account remains overdue for more than 15 days, Alibaba Cloud suspends the service. Alibaba Cloud removes the associated nodes from the cluster but does not release them, and deletes the ACK Edge cluster and its container instances. You cannot restore container instances that are deleted along with the ACK Edge cluster.
Alibaba Cloud provides the extended suspension-free benefit. When a pay-as-you-go resource is overdue, you can continue to use cloud services for a certain amount or duration. Normal fees apply during the extended period. For more information, see Extended Suspension-Free Benefit.
Refund policy
The pay-as-you-go billing method is non-refundable.
Billing cycle
The billing cycle for ACK Edge is 24 hours. Each day, Alibaba Cloud generates an invoice for the service usage from the previous day, typically within 8 to 10 hours after a billing cycle ends. Alibaba Cloud then deducts the service fees from your Alibaba Cloud account.
View bills
For details, see View bills.
Billing FAQ
-
Why do my daily charges suddenly increase or decrease?
-
Your bill is calculated based on the total number of vCPUs in the nodes managed by the cluster. If you scale your nodes up or down, the change will be reflected on the next day's bill.
-
When a node is removed without using the ACK console (for example, by using
kubectl delete nodeto remove the node), the removed node may still incur charges on the day of removal. Therefore, always remove nodes by using the ACK console.
-
-
I deleted my ACK Edge cluster yesterday. Why was I still charged today?
Management fees for an ACK Edge cluster are billed daily (from 00:00:00 to 23:59:59) and charged on the following day. If you deleted an ACK Edge cluster yesterday, the billing system had already recorded the fees for that day. Therefore, a final bill is generated today. You will not receive any further bills for the deleted cluster.
-
How do I stop billing for an ACK Edge cluster?
Delete all of your ACK Edge clusters in all regions. Before you delete a cluster, make sure to back up your applications and data.
-
Are nodes in a NotReady state still billed?
Yes. An ACK Edge cluster manages nodes in both Ready and NotReady states. Therefore, nodes in the NotReady state still incur charges. To stop billing for a node, you must remove it from the cluster using the ACK console.