Skip to main content

​
Overview

Use this page when exposing Arize AX from EKS through the AWS load-balancing pattern your platform team supports. The exact controller and annotations vary by environment, so treat this page as the AWS-specific planning companion to Configuring ingress and endpoints. If you provisioned AWS load-balancer-controller roles or networking with Terraform, keep those outputs aligned with the ingress manifests you apply.

​
Endpoint planning

Before applying ingress manifests, decide:
  • The hostname users will use for the Arize AX UI.
  • Whether the cluster uses one endpoint or multiple endpoint hostnames.
  • Where TLS terminates.
  • Which ingress controller or AWS load balancer integration your platform supports.
Set appBaseUrl in values.yaml to the UI hostname users will keep: 
appBaseUrl: "https://<arize-app.domain>"

​
Example manifests

Review the endpoint examples included in the extracted distribution under examples/endpoints/. Use the example that matches your ingress controller, then replace placeholder hosts, TLS references, and service names as needed for your AWS environment. For NGINX, Istio, Kong, and other non-cloud-specific controllers, use Ingress - NGINX, Istio, Kong, and others.

​
DNS and validation

After applying ingress resources: 
kubectl -n arize get ingress
kubectl -n arize describe ingress
Point DNS at the load balancer address and verify resolution: 
nslookup arize-app.<my-organization-domain>
Then open the UI hostname and continue with Validate deployment.