Enabling GenAI Builder on Hybrid Manager

GenAI Builder is EDB's integration of Griptape, a tool that allows you to build AI agents.

To enable the GenAI Builder launchpad application in your Hybrid Manager instance, you must create a secret for the application and configure dedicated object storage.

Creating a secret for GenAI Builder

For EKS installations using the eks-install-secrets.sh script, you can skip key and secret creation and go to Configure DataLake object storage, CORS configuration, and Backing up the Fernet key. Other EKS setups and operating systems require manual secret creation with the Fernet key.

1. Create a Fernet key and store it in a variable:

   → WrapCopy

   FERNET_KEY=$(dd if=/dev/urandom bs=32 count=1 2>/dev/null | base64)

   Note

   Fernet is a cryptographic library used by Python. It provides symmetric encryption/decryption and is required to store secret data.

2. Create a namespace for the integration:

   → WrapCopy

   kubectl create namespace upm-griptape

3. Create a secret that references the new Fernet key and is stored in the dedicated namespace:

   → WrapCopy

   kubectl apply -f - <<EOF
   apiVersion: v1
   kind: Secret
   metadata:
      name: fernet-secret
      namespace: upm-griptape
   stringData:
      FERNET_KEY: ${FERNET_KEY}
   EOF

Configuring DataLake object storage for GenAI builder

1. Create a DataLake bucket in the object storage you're using for your Hybrid Manager deployment. GenAI Builder uses it to store structures, tools, and indexed data.

   • AWS S3
   • Google Cloud Storage (GCS)
   • Other S3-compatible storage

   → WrapCopy

   aws s3 mb s3://<your-griptape-datalake-bucket-name> –region     <your-region>

   → WrapCopy

   gsutil mb -l <your-region> gs://<your-griptape-datalake-bucket-name>

   Use your provider’s management console or CLI to create a bucket with a unique name for your Griptape DataLake bucket.

2. Capture the following information for your bucket. You will need it later when you first use the GenAI launchpad application. The console will prompt you for your DataLake bucket configuration, which requires:

   • DATA_LAKE_ROOT_BUCKET: The name of the bucket for use with DataLake.

   • DATA_LAKE_S3_ACCESS_KEY: The access_key used to connect to the DataLake bucket.

   • DATA_LAKE_S3_SECRET_ACCESS_KEY: The secret_access_key used to connect to the DataLake bucket.

   • DATA_LAKE_S3_ENDPOINT_UR: The endpoint URL used to connect to the DataLake bucket.

Configuring CORS

[
    {
        "AllowedHeaders": [
            "*"
        ],
        "AllowedMethods": [
            "PUT",
            "POST",
            "DELETE",
            "GET",
            "HEAD"
        ],
        "AllowedOrigins": [
            "https://${PORTAL_DOMAIN_NAME}"
        ],
        "ExposeHeaders": []
    }
]

After you've configured the secret and created a dedicated bucket, continue with Hybrid Manager installation.

Backing up the Fernet key

The Hybrid Manager administrator must keep the Fernet key safe and back it up.

Fetch the key:

kubectl get secret -n upm-griptape fernet-secret -o yaml

Store the key safely.