Realtime Compute for Apache Flink:Activate Realtime Compute for Apache Flink

Precautions

• Creating a Flink workspace involves other cloud products, such as VPC, OSS, and monitoring services. For more information about the fees, see Billable items.

• Realtime Compute for Apache Flink uses a storage-compute disaggregation architecture when you attach it, note the following points:

  • For information about how to activate OSS, see Activate OSS Service. The OSS bucket must be in the same region as the Flink workspace, and its storage class must be Standard.

  • Do not set any policies, such as versioning or retention policies, for the associated OSS bucket. Setting these policies can affect the normal operation of Flink jobs.

    If you enable versioning for your OSS bucket, too many delete markers can slow down list operations. Therefore, if you enable versioning, you must configure lifecycle rules to periodically clean up delete markers and unnecessary historical versions. This reduces storage costs and improves OSS performance. For more information about how to clean up delete markers, see Use lifecycle rules based on the last modified time to reduce storage costs for versioning-enabled buckets.

    Warning

    If you do not enable versioning for your OSS bucket but need to set lifecycle rules, do not configure a purge policy for Flink-related directories, such as artifacts, flink-jobs, flink-savepoints, sql-artifacts, plan, and flink-sessionclusters. Configuring a purge policy can delete Flink-related files and cause Flink jobs to run abnormally.

  • If you use an OSS bucket for storage when you create a workspace, you must ensure that the associated bucket is a zone-redundant storage (ZRS) bucket to achieve high availability (HA) for the Flink workspace. For information about how to configure a ZRS bucket, see Change the storage redundancy type of a bucket. Otherwise, if a zone becomes unavailable, the state data cannot be accessed, and Flink cannot guarantee stateful job startup.

    Note

    If a workspace contains both HA and single-zone projects, directly upgrading the associated bucket to ZRS may increase storage costs. You can create a new workspace exclusively for HA and associate a ZRS bucket with it. This provides an optimal balance between cost and reliability. For more information about OSS storage fees, see Storage fees.

  • If you use an OSS bucket for storage, make sure to disable the Malicious File Detection SDK in Security Center. Enabling this feature can trigger OSS traffic throttling, which causes Flink jobs to get stuck in the initialization state.

Create a subscription workspace

1. Log on to the Realtime Compute for Apache Flink console.

2. Next to Fully Managed Flink, click Purchase.

3. The first time you make a purchase, you must grant Flink permissions to access the required cloud resources.

   Click Go To RAM For Authorization. On the Cloud Resource Access Authorization page, click Agree To Authorization. After the automated authorization is complete, Flink is granted the required permissions to access cloud resources.

4. On the purchase page, specify the configuration information.

   

   Category	Configuration item	Description	Example
   Basic configuration	Billing Method	Set this to Subscription. For more information about billing, see Subscription.	Subscription
   	Subscription Duration	Select the subscription duration.	1 Month
   	Auto-renewal	If you do not select Enable, you can modify the renewal policy later. To do this, go to the Alibaba Cloud Management Console. In the top navigation bar, choose Expenses > Renewal Management.	-
   	Processor Architecture	The Intel X86 and YiTian ARM architectures are available to meet your requirements. Note Currently, the YiTian ARM architecture is supported only for subscription workspaces in the China (Beijing), China (Ulanqab), and China (Hangzhou) regions. The information on the purchase page prevails.	Intel X86 architecture
   	Region	Select the same Region as your upstream and downstream storage.	Beijing
   Network configuration	Deployment Mode	This parameter is available only for Subscription workspaces that use the Intel X86 architecture in specific regions. The following Deployment Modes are supported: Single Zone (Cost-effective): Flink automatically allocates the optimal computing zone in the selected region and shares the resource inventory across zones. This enables imperceptible resource scheduling and improves elastic load balancing capabilities. Cross Zone (High business availability): This mode provides high availability (HA). If the zone where a job in a cross-zone project is running fails, the job is automatically rescheduled to another stable zone in the same region to recover. This effectively prevents service interruptions caused by single-zone failures and ensures job continuity and HA. Important To achieve end-to-end HA, you must ensure that your upstream and downstream systems are also highly available. If you do not select Cross Zone for Deployment Mode when you create the workspace, you can enable HA later using other methods. However, you must ensure that the workspace has sufficient cross-zone CU resources. For more information, see Method 2 and Method 3 in High availability.	-
   	CU info	If you set Deployment mode to Single Zone, you only need to configure computing resources for a Single Zone. If you set Deployment mode to Cross Zone, you can select whether to Enable Hybrid Purchase For Single Zone as needed. If you do not select this checkbox, you only need to configure computing resources for a Cross Zone. If you select this checkbox, you must set the Computing Resource Quota for the Single Zone and Cross Zone. Note Each development console and its necessary components require an additional 2 CU-hours of management resources. These resources are automatically configured and do not require manual operations. For more information, see Billable items.	-
   	VPC	Select a virtual private cloud (VPC) in the corresponding region. After the workspace is created, you cannot change the VPC. For more information about how to create a VPC, see Create a VPC and a vSwitch. If the target upstream and downstream storage is in a VPC, the Flink workspace must be in the same VPC. Only the 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 standard private CIDR blocks and their subnets are supported.	flink-test-vpc
   	VSwitch	If you set Deployment Mode to Cross Zone, you must select two vSwitches in different zones. Each workspace requires two to three IP addresses. Select at least one vSwitch for each zone and plan the CIDR blocks based on the scale of your Flink jobs. Note Only created vSwitches in the target VPC and Flink-supported zones are displayed. You can modify the vSwitch after the workspace is created. The zone of the selected vSwitch is irrelevant to the zone where the job runs. The vSwitch is used only for network connectivity to ensure that your jobs can access network resources. Do not modify or delete the configurations of these vSwitches. This may affect network connectivity and the normal operation of jobs.	flinktest
   Workspace configuration	Workspace Name	The name must start with a lowercase letter, contain only lowercase letters, digits, and hyphens (-), and cannot end with a hyphen. The name must be 1 to 60 characters in length. Important The Workspace Name must be globally unique, including across workspaces created by other users. If the name is already in use, the system prompts that the Workspace Name Already Exists. You must change the name. The name cannot be changed after the workspace is created.	flinktestnamespace
   Storage configuration	OSS Storage	An OSS bucket is used to store information such as system checkpoints, job snapshots, logs, and JAR packages. For more information about the content of each directory in an OSS bucket, see Manage files. Important When you associate an OSS bucket, see the Precautions section. If you set Deployment Mode to Cross Zone, the system verifies the OSS configuration and displays only zone-redundant storage buckets. You cannot change the OSS bucket after the Flink workspace is created.	flink-test-oss
   Tags and tag values		A tag consists of a tag key and a tag value. It is an identifier for a cloud resource. Tags help you categorize, search for, and aggregate cloud resources that have the same characteristics from different dimensions, which simplifies cloud resource management. You can manage tags in the Tag Management console.	-
   Monitoring service	Monitoring Service	You can select Free Monitoring Service or Pay-as-you-go Prometheus Service. For a comparison of features, see Comparison of features between CloudMonitor and ARMS alerting service. Free monitoring service: After you create a Flink workspace, CloudMonitor provides basic monitoring and alerting capabilities. For more information, see Free of charge. Prometheus Service: After you create a Flink workspace, Application Real-Time Monitoring Service (ARMS) is automatically activated to provide commercial Prometheus monitoring and alerting capabilities. For more information about billing, see Billing of Prometheus Service.	Free monitoring service

5. Select Terms of Service, click Purchase, and complete the payment.

   After the payment is complete, click Management Console to view your workspace, which is typically created within 5 to 10 minutes.

Create a pay-as-you-go workspace

1. Log on to the Realtime Compute for Apache Flink console.

2. For Fully Managed Flink, click Purchase.

3. If this is your first purchase, you must grant Flink permissions to access the required cloud resources.

   Click Go To RAM For Authorization. On the Cloud Resource Access Authorization page, click Agree To Authorization. After the authorization is complete, Flink is granted the required permissions to access cloud resources.

   Note

   If you have purchased before, skip this step.

4. On the purchase page, specify the configuration information.

   

   Category	Configuration item	Description	Example
   Basic configuration	Billing Method	Set this to Pay-as-you-go. For more information about billing, see Pay-as-you-go.	Pay-as-you-go
   	Region	Select the same Region as your upstream and downstream storage.	Beijing
   Network configuration	VPC	Select a virtual private cloud (VPC) in the corresponding region. After the workspace is created, you cannot change the VPC. For more information about how to create a VPC, see Create a VPC and a vSwitch. If the target upstream and downstream storage is in a VPC, the Flink workspace must be in the same VPC. Only the 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 standard private CIDR blocks and their subnets are supported.	flink-test-vpc
   	VSwitch	If you set Deployment Mode to Cross Zone, you must select two vSwitches in different zones. Each workspace requires two to three IP addresses. Select at least one vSwitch for each zone and plan the CIDR blocks based on the scale of your Flink jobs. Note Only created vSwitches in the target VPC and Flink-supported zones are displayed. You can modify the vSwitch after the workspace is created. The zone of the selected vSwitch is irrelevant to the zone where the job runs. The vSwitch is used only for network connectivity to ensure that your jobs can access network resources. Do not modify or delete the configurations of these vSwitches. This may affect network connectivity and the normal operation of jobs.	flinktest
   Workspace configuration	Workspace Name	The name must start with a lowercase letter, contain only lowercase letters, digits, and hyphens (-), and cannot end with a hyphen. The name must be 1 to 60 characters in length. Important The Workspace Name must be globally unique, including across workspaces created by other users. If the name is already in use, the system prompts that the Workspace Name Already Exists. You must change the name. The name cannot be changed after the workspace is created.	flinktestnamespace
   	Computing resource Quota Ceiling	The default value is 1,000 CU-hours. You can change the value. The maximum value is 9,999,999. Note Each development console and its necessary components require an additional 2 CU-hours of management resources. These resources are automatically configured and do not require manual operations. For more information, see Billable items.	100
   Storage configuration	OSS Storage	An OSS bucket is used to store information such as system checkpoints, job snapshots, logs, and JAR packages. For more information about the content of each directory in an OSS bucket, see Manage files. Important When you associate an OSS bucket, see the Precautions section. If you set Deployment Mode to Cross Zone, the system verifies the OSS configuration and displays only zone-redundant storage buckets. You cannot change the OSS bucket after the Flink workspace is created.	flink-test-oss
   Tags and tag values		A tag consists of a tag key and a tag value. It is an identifier for a cloud resource. Tags help you categorize, search for, and aggregate cloud resources that have the same characteristics from different dimensions, which simplifies cloud resource management. You can manage tags in the Tag Management console.	-
   Monitoring service	Monitoring Service	You can select Free Monitoring Service or Pay-as-you-go Prometheus Service. For a comparison of features, see Comparison of features between CloudMonitor and ARMS alerting service. Free monitoring service: After you create a Flink workspace, CloudMonitor provides basic monitoring and alerting capabilities. For more information, see Free of charge. Prometheus Service: After you create a Flink workspace, Application Real-Time Monitoring Service (ARMS) is automatically activated to provide commercial Prometheus monitoring and alerting capabilities. For more information about billing, see Billing of Prometheus Service.	Free monitoring service

5. Select Terms of Service, click Purchase, and complete the payment.

   After the payment is complete, click Management Console to view your workspace, which is typically created within 5 to 10 minutes.

What to do next

After the Flink workspace is created, you can perform the following operations.

References

• Why is my activated Flink workspace not displayed in the Realtime Compute for Apache Flink console?

• How do I view information such as the workspace ID?

• Can I change the workspace name?

• Can I change the VPC and vSwitch?