Create Superset

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

To create Apache Superset, follow these steps:

Step 1: On 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: On the Apache Superset creation form, enter the information on the Basic Information screen:

• 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 move 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 so the service is HA

Step 5. Click Next to move to the Advanced screen

• Database (Database information used to store data for Apache Superset; you can use a Database already created on the FPT Database Engine service, or any other Database of your own)
• Type: defaults to PostgreSQL
• Host name (required): hostname or IP of Postgres
• Port (required): connection port, default is 5432
• Database name (required): database name
• Username (required): username to access Postgres
• Password (required): password to access Postgres

After entering the Database information, click Test connection to check the connection from the Workspace to the Database you entered

• Redis (Database information used to store data for Apache Superset; you can use a Database already created on the FPT Database Engine service, or any other Database of your own)
• Host (required): hostname or IP of Redis

Port (required): connection port

• Username (required): username
• Password (required): password

Click Test connection to check the connection from the Workspace to Redis

• Cache (required): select the index used to store cache
• Celery (required): select the index used for processing

• Single Sign On

  • If Single Sign On is not enabled, Superset is initialized with Basic authen

  • If Single Sign On is enabled:

  • Provider: FPT ID

    Enter the following information:

    • Username: your username
    • Email: your FPT email address

• Provider: Google

  Enter the following information:

  • Client ID: an ID code used to authenticate the client with Google
  • Client Secret: the secret used to authenticate the client with Google
  • Email: your email address

• Provider: Keycloak

  Enter the following information:

  • Auth Provider name: the 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: the secret used to authenticate the client with Keycloak
  • Username: the username in Keycloak
  • Email: the email address in Keycloak

• Custom Domain

  • Purpose: allows you to configure a custom domain to access the service.

    • For a Public Workspace: used to assign a domain and certificate without needing to turn TLS on/off (HTTPS is always available).
    • For a Private Workspace: besides the domain and certificate, you can also choose to 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: choose from the list of certificates already imported in Certificate Manager.
    • Buttons:
      • Manage certificate: opens the certificate management screen.
      • Validate: checks whether the certificate is valid for the domain.
    note

    For a Public Workspace, the TLS/SSL certificate option is not shown — 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 the service.

  • Certificate name: choose from the certificate list.

  • Buttons:

    • Manage certificate: opens certificate management.
    • Validate: checks the certificate.
    note

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

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

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

Superset finishes initializing when Worker Status is Succeeded and the Status of Apache Superset is Healthy (~10 minutes)