Skip to main content

​
Before you start

  • Complete Download and extract the distribution. Work from the extracted folder that contains arize.sh, arize-operator-chart.tgz, and your values.yaml.
  • Align your cluster with EKS cluster and AWS resources, or provision it with Terraform.
  • Contact Arize AI for clusterSizing. It must match your cluster capacity.
  • Keep the AWS quick start open as a template.
  • Treat values.yaml as sensitive. Store generated passwords and keys in your secret manager, not in git history.
For every field that must be base64-encoded, use:

​
1. Verify cluster access and clusterName

Configure kubectl for your EKS cluster:
Set clusterName to the EKS cluster ARN:

​
2. Seed hubJwt

Store the runtime registry JWT Arize AI provided under hubJwt, base64-encoded:

​
3. Set cloud and region

Use the same region as the EKS cluster and S3 buckets.

​
4. Point to S3 buckets

Set the bucket names you prepared for Gazette and ArizeDB:
If your buckets use server-side encryption, set serverSideEncryption to the value approved by your AWS platform team. Leave it empty only when that is intentional.

​
5. Configure IAM

If using IRSA, set the role ARN that has read/write access to the Gazette and ArizeDB buckets:
If not using IRSA, omit awsServiceAccountRoleRwBucket and make sure the node role has the required S3 and KMS permissions from EKS cluster and AWS resources.

​
6. Set secrets, organization, and sizing

Choose a Postgres password and a cipher key, then base64-encode both. Example for a random 32-character cipher source then base64 (adjust to your security process):
Use echo -n '<your-password>' | base64 | tr -d '\n' for postgresPassword if you pick the password yourself. Set the secrets along with the organization and sizing values:

​
7. Set appBaseUrl

Set the URL users will use for the Arize AX UI after ingress and DNS exist:
You can update this after ingress is finalized, but the installed application should eventually advertise the hostname users will keep.

​
8. Optional private registry

If the cluster must pull images from your registry, set both registry values:

​
9. Optional: storage performance tiers

SSD volumes default to gp3-2000 and standard ones default to gp3-400. EKS cluster and AWS resources
To manage the StorageClasses yourself instead of letting the helm chart create them, set storageClassCreationEnabled: false and make sure any class you reference already exists in the cluster.

​
10. Install with arize.sh or Helm

Using arize.sh:
Using Helm directly:
Both approaches install the operator chart using the same values.yaml.

​
Next steps