Create Apache Flink

To create Flink, follow these steps:

Step 1: In the menu bar, select Data Platform > select Workspace Management > select Workspace name

Step 2: Click Create > the New Service popup is displayed > select Flink > Create

Step 3: In the Flink creation form, enter the information on the Basic Information screen:

• Name (required): Service name

Note: The Apache name can contain lowercase letters a-z, uppercase letters A-Z, or digits 0-9. In particular, spaces are not allowed; you can use "-" or "_" instead of a space.

• Description (optional): Description
• Version (required): Select the version

Step 4: Click Next Step to move to the Nodes Configuration information screen

Enter the following information:

Job manager

• Storage policy (required): Select the Storage Policy
• Type: Default is Medium-4 (2 CPU – 4 GB RAM)
• Number of nodes: Default value is 2

Task manager

• Storage policy (required): Select the Storage Policy
• Type (required): Select the configuration
• Number of nodes: Enter the number of nodes

warning

The number of nodes must be greater than or equal to 1 and less than or equal to 10

If you want to automatically scale up the Worker configuration of Flink, check Enable worker auto scaling > enter the maximum number of nodes for the Worker

warning

The max node value must be greater than Number of nodes and less than or equal to 10

Step 5: Click Next Step to move to the Additional Properties screen

Enter the following information:

Checkpoint/Savepoint storage stores the state of the streaming application:

• Enpoint: enter the endpoint information
• Access key: enter the access key
• Secret: enter the password
• Bucket name: enter the bucket name
• Path: enter the path

Click Test Connection to check the connection from the Workspace to the Storage

Job Storage holds the job *.jar file, and jobs can be uploaded directly to S3:

• Job Storage: Select the Storage already mounted on the Workspace
• Path: Enter the path containing the file

Task slot

• Slot per task: Enter the Slot per task value

warning

The Slot per task value must be greater than or equal to 1 and less than or equal to 4

• Total slot: The total slot value depends on the slot per task value

Custom Domain

• Purpose: Allows configuring a custom domain to access services.

  • For Public Workspace: Used to assign a domain and certificate without needing to enable/disable TLS (HTTPS is always available).
  • For Private Workspace: In addition to domain and certificate, users can optionally enable or disable TLS/SSL to decide whether to use HTTPS or HTTP.

• When the Workspace is Public

  • Custom domain: Check to enable a custom domain.
  • Domain: Enter the domain name (e.g., abc.local, jupyter.example.com).
  • Certificate name: Select from the list of certificates already imported in Certificate Manager.
  • Buttons:
  • Manage certificate: Open the certificate management screen.
  • Validate: Check whether the certificate is valid for the domain.
  note

  On a Public Workspace, the TLS/SSL certificate option is not displayed — the system supports HTTPS by default.

• When the Workspace is Private

  • Custom domain: Check to enable a custom domain.
  • Domain: Enter the domain name.
  • TLS/SSL certificate: Check to enable HTTPS for services.
  • Certificate name: Select from the certificate list.
  • Buttons:
  • Manage certificate: Open certificate management.
  • Validate: Check the certificate.
  note

  If TLS/SSL certificate is unchecked, the service will run over HTTP and no certificate is required.

Step 6: Click Next Step to move to the Review & Create screen

Step 7. Review the entered information, then click Create to complete the initialization of Apache Flink

Apache Flink completes initialization when Worker Status is Succeeded and the Status of Flink is Healthy (~10 minutes)