This topic provides answers to some frequently asked questions about the billing of fully managed Flink clusters.

What are the default billable items for renewal?

The following table describes the billable items of fully managed Flink.
Billable item Description
Management resource When you create a cluster, the system deploys a console for the cluster. The console and its components require about 2 CUs of management resources.
Computing resource Computing resources are the resources that are used for computing. You are charged for the computing resources based on the subscription or pay-as-you-go billing method. The billing unit is CU.
To activate a fully managed Flink cluster, you must pay for the fees of fully managed Flink. If you use other cloud services when you activate and use fully managed Flink, you are charged based on the billing method that is described in the following table.
Service Billing method
VPC For more information about the billing method, see Billing.
OSS For more information about the billing method, see Overview.
SLB After you activate a fully managed Flink cluster, the Server Load Balancer (SLB) service is automatically activated. You are charged for the use of SLB after you create a fully managed Flink cluster. For more information, see Pay-as-you-go.
Notice SLB allows you to access the console of fully managed Flink over the Internet. After you create an SLB instance, we recommend that you do not delete the instance or modify the configurations of the instance. Otherwise, the fully managed Flink cluster may become unavailable.
ARMS After you activate a fully managed Flink cluster, Application Real-Time Monitoring Service (ARMS) is automatically activated to provide Prometheus Service of the Pro Edition. For more information about the billing of ARMS, see Billing.

In the standard metric template that is provided, you are charged only for operator-related metrics. Operator-related metrics are mainly described in the IO and Connectors section of "System metrics" in the official Apache Flink documentation. For more information, see Flink V1.11, Flink V1.12, and Flink V1.13.

How do I renew a fully managed Flink cluster?

Fully managed Flink clusters support manual renewal and auto-renewal. For more information, see Renewal.

How do I apply for a refund when I no longer need to use a cluster?

The following table describes the refund rules of fully managed Flink clusters. For more information, see Refund.

When you purchase a subscription fully managed Flink cluster, you must complete the payment based on the subscription duration. If you no longer need to use the cluster due to changes in your business requirements, you can submit a ticket to unsubscribe from the cluster and apply for a refund.

Is an amount of fee deducted from my account balance if a cluster fails to be created?

No, no fee is deducted from your account balance if a cluster fails to be created. You can view the billing details for the deduction items. For more information, see View billing details.

Am I still charged after I create a pay-as-you-go cluster but do not run a job on the cluster?

Yes, you are charged for the cluster. If you create a pay-as-you-go fully managed Flink cluster, you are charged for the cluster based on the billing rules regardless of whether you run jobs on the cluster. If you do not run jobs on the cluster, you are still charged for 2 CUs that are used as management resources. For more information, see Billing formulas.

Can fully managed Flink clusters run as expected if my SLB instance has an overdue payment?

No, fully managed Flink clusters cannot run as expected if your Server Load Balancer (SLB) instance has an overdue payment. SLB allows you to access fully managed Flink clusters over the Internet. If you do not renew your SLB instance within seven days after an overdue payment is generated, the SLB instance is released, and you cannot access fully managed Flink clusters over the Internet. In this case, you must purchase a fully managed Flink cluster again. For more information, see SLB overdue payments.