Legacy Audit - no Elasticsearch

For best performance and access to new features, Immuta recommends deploying 2024.2 according to the recommendations on the official documentation site. For situations where some or all of the necessary infrastructure is unavailable, it is still possible to deploy the LTS release without all new functionality enabled.

This document addresses enabling Legacy Audit when no Elasticsearch cluster is available.

Legacy Audit - No Elasticsearch availability

Elasticsearch is a required infrastructure component for Immuta Detect and the Universal Audit Model (UAM).

When unavailable, the release can fallback to legacy audit capabilities by disabling the audit-service and disabling Immuta Detect.

immuta-legacy-audit-2024.2.yaml

global:
  imageRegistry: 231431240278.dkr.ecr.us-east-1.amazonaws.com
  imageTag: 2024.2.0
audit:
  enabled: false
secure:
  extraEnvVars:
    - name: FeatureFlag_AuditService
      value: "false"
    - name: FeatureFlag_detect
      value: "false"
    - name: FeatureFlag_auditLegacyViewHide
      value: "false"
  ingress:
    hostname: lts-no-elastic.immuta.us
    ingressClassName: alb
    annotations:
      alb.ingress.kubernetes.io/scheme: internet-facing
      alb.ingress.kubernetes.io/target-type: ip
      alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
      alb.ingress.kubernetes.io/ssl-redirect: '443'
      alb.ingress.kubernetes.io/backend-protocol: HTTP
    tls: true
  postgresql:
    host: immuta-lts.cfzynskvahpp.us-east-1.rds.amazonaws.com
    port: 5432
    database: noelastic
    username: noelastic
    password: secret
    ssl: true