This topic describes how to use an Alibaba Cloud account to activate fully managed Flink and the precautions that you need to take note of before you activate the service.
Prerequisites
- You have an Alibaba Cloud account. If you do not have an Alibaba Cloud account, create one first.
- The Object Storage Service (OSS) and Virtual Private Cloud (VPC) services are activated.
- Fully managed Flink uses an architecture in which computing is decoupled from storage. This service needs to use OSS to store information, such as the uploaded Java Archive (JAR) files, the logs of Flink jobs, and the savepoints or checkpoints that are generated in fully managed Flink jobs. If you have not activated OSS, activate it first. For more information, see Activate OSS.
- For more information about how to activate VPC, see Create a VPC.
Server Load Balancer (SLB) and Application Real-Time Monitoring Service (ARMS) are automatically activated when you activate fully managed Flink. For more information about the billing rules of the involved cloud services, see Billing unit and billable items.
- Your Alibaba Cloud account balance has at least USD 100 or the voucher or coupon of the equivalent value before you activate the pay-as-you-go service.
Usage notes
When you select an OSS bucket, we recommend that you do not select a bucket for which
the versioning feature is enabled. If the versioning feature is enabled for your bucket,
an excessive number of delete markers reduces the speed of list processing. Therefore,
if you enable the versioning feature, you must configure lifecycle rules to periodically
remove delete markers and historical versions that you no longer use. This reduces
storage costs and improves OSS performance. For more information about how to remove
delete markers, see Configure lifecycle rules to manage object versions.
Note If you do not enable the versioning feature and you want to configure lifecycle rules,
we recommend that you do not configure a deletion policy for the related directories
of Flink, including artifacts, flink-jobs, flink-savepoints, sql-artifacts, plan,
and flink-sessionclusters. If you configure a deletion policy for one of the preceding
directories, Flink-related files may be deleted. As a result, Flink jobs cannot run
as expected.