Skip to content
Data Platform Infrastructure

Polaris

Polaris runs in each env-dataops data-platform EKS cluster and federates the environment Glue catalog through the Iceberg REST catalog API. The current service root is terraform/polaris/env/<env>.

Current Shape

Polaris is deployed in the polaris namespace with PostgreSQL persistence, ExternalSecrets-backed credentials, and an IRSA role named data-platform-<env>-polaris.

The current host pattern is:

polaris.data-platform.us-east-1.<env>-dataops.fetchrewards.com

The NLB host is also configured for catalog consumers that need the load balancer path:

polaris-nlb.data-platform.us-east-1.<env>-dataops.fetchrewards.com

Snowflake Integration

Polaris creates or supports the Snowflake LH_POLARIS_<ENV> catalog-linked database. Snowflake authenticates to Polaris with an OAuth2 service principal stored in Secrets Manager as <env>/polaris/snowflake-principal.

LH_GLUE_<ENV> is managed through the Lakehouse service root, not the Polaris root.

Cross-Env Access

Polaris has same-env Glue federation plus remote Glue catalog definitions for cross-env reads. Lake Formation grants, S3 policies, and Polaris/Spark catalog config must all line up; Polaris alone is not the full access-control layer.

Legacy Reference

The older Polaris catalog architecture has useful architecture background, but it predates the full env-dataops rollout and still contains test-dataops examples.

Checked Against

  • terraform/polaris/env/dev/main.tf, stage, preprod, and prod on origin/main.
  • terraform/modules/polaris.
  • implementations/2026-05-21-dl-419-prod-dataops-runtime-progress.md.