Create Apache Superset

Apache Superset is an open-source Business Intelligence (BI) platform that makes it easy to visualize data, create dashboards, and analyze data. It is a powerful alternative to Tableau and Power BI in systems using large data platforms such as Druid, Presto, Trino, BigQuery, ClickHouse, MySQL, PostgreSQL, and many others.

To create Apache Superset, follow these steps:

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

Step 2: In the My services section, click Create > the New Service popup appears, select Apache Superset > Create

Step 3: In the Apache Superset creation form, enter the Basic Information:

• Name (required): Service name

Note: The service name must be between 1 and 30 characters. It can contain lowercase letters a-z, uppercase letters A-Z, or digits 0-9.

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

Step 4. Click Next to proceed to the Node configuration screen

Enter the following information:

• Storage policy (required): Select the Storage Policy

• Type (required): Select the resource configuration

• Number of nodes (required): Enter the number of nodes for Superset to enable HA

Step 5. Click Next to proceed to the Advanced screen

• Database (Database information for storing Apache Superset data; users can use a Database created on the FPT Database Engine service or any other user-managed Database)

  • Type: Default is PostgreSQL

  • Host name (required): Hostname or IP of the Postgres server

  • Port (required): Connection port, default is 5432

  • Database name (required): Database name

  • Username (required): Username for accessing Postgres

  • Password (required): Password for accessing Postgres

After entering the Database information, click Test connection to verify the connection from the Workspace to the entered Database.

• Redis (Redis information for Apache Superset; users can use a Database created on the FPT Database Engine service or any other user-managed Database)

  • Host (required): Hostname or IP of the Redis server

  • Port (required): Connection port

  • Username (required): Username

  • Password (required): Password

Click Test connection to verify the connection from the Workspace to Redis.

• Cache (required): Select the index for caching

• Celery (required): Select the index for task processing

• Single Sign On

  • If Single Sign On is not selected, Superset uses Basic authentication

  • If Single Sign On is selected:

  • Provider: FPT ID

Enter the following information:

 * **Username**: Username

 * **Email**: FPT email address

• Provider: Google

Enter the following information:

 * **Client ID**: An ID code used to authenticate the client with Google

 * **Client Secret**: Password used to authenticate the client with Google

 * **Email**: Email address

• Provider: Keycloak

Enter the following information:

 * **Auth Provider name**: Provider name

 * **Realm**: A management space in which all users, groups, roles, clients, and other objects are managed and secured independently

 * **Auth server url**: The base URL of the Keycloak server, used by clients to perform authentication

 * **Client ID**: An ID code used to authenticate the client with Keycloak

 * **Client Secret**: Password used to authenticate the client with Keycloak

 * **Username**: Username in Keycloak

 * **Email**: Email address in Keycloak

• 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 between HTTPS or HTTP.

  • Public Workspace

    • 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 imported in Certificate Manager.

    • Buttons:

    • Manage certificate: Open the certificate management screen.

    • Validate: Verify the certificate is valid for the domain.

note

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

• Private Workspace

  • 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: Verify the certificate.

note

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

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

Step 7. Review the information, then click Create to complete the Apache Superset initialization.

Superset is fully initialized when Worker Status is Succeeded and the Status of Apache Superset is Healthy (~10 minutes).