LogoLogo
Public Knowledge Base
Public Knowledge Base
  • Self-hosted Immuta
    • Official Immuta Self-Managed Deployment Documentation
    • What's new in 2024.2?
    • Deployment Options
      • AWS Immuta Deployment
      • Azure Immuta Deployment
      • K3s Deployment
      • SUSE Rancher Kubernetes Engine (RKE2) Deployment
      • In-cluster PostgreSQL using Crunchydata
      • In-cluster Elasticsearch using Elastic Cloud on Kubernetes (ECK)
      • Production Linkerd with AWS Private CA issuer
      • Deploying Linkerd via Open Source Linkerd
      • Deploying Linkerd Service Mesh via Buoyant Enterprise for Linkerd
      • Uninstalling Linkerd
      • Upgrading to Immuta 2024.2 LTS
      • LTS Upgrade via Legacy Chart
      • Legacy Audit - no Elasticsearch
      • Temporal with RDS
      • Setting Up OpenSearch User Pemissions
    • Air gapped installations
      • Immuta Installation on k3s in Air Gapped environment
      • Air-gapped Installation Artifact Transfer
  • Excessive failed jobs in pgboss impacting system performance
  • Example Trino installation via Open Source Helm Chart
  • Immuta Installation on Self Managed Infrastructure Overview
  • Repeatable k3s stack deployment on AWS EC2
  • Trino OAuth2 and JWT via Okta
  • Copy of Okta Attribute Mapping
Powered by GitBook
On this page
  1. Self-hosted Immuta
  2. Deployment Options

Setting Up OpenSearch User Pemissions

PreviousTemporal with RDSNextAir gapped installations

Last updated 4 months ago

On Immuta 2024.2 LTS and newer, users should deploy and manage their own Elasticsearch or AWS OpenSearch for audit. For users utilizing AWS OpenSearch, use this how-to to set up the proper permissions needed for the install.

  1. In the AWS console, and create a master user: This user will set up the permissions for the audit user.

  2. In the OpenSearch console, : This user will be the audit user. You will enter the username and password for this user when installing Immuta.

  3. for the audit user.

  4. Add the audit user to the role.

  5. Create the two additional roles to hold the following permission groups: Immuta recommends permission groups for a smooth configuration, but just ensure the user has the all the following permissions.

    • immuta_cluster_permission_grp with the following permissions:

      • cluster:monitor/health

      • indices:data/write/bulk*

      • indices:data/write/bulk

    • immuta_index_permission_grp with the following permissions:

      • indices:data/read/search

      • indices:admin/exists

      • indices:admin/create

      • indices:admin/delete

      • indices:admin/settings/update

      • indices:admin/get

      • indices:data/write/delete/byquery

      • indices:data/write/index

      • indices:admin/mapping/put

      • indices:data/write/bulk

      • indices:data/write/bulk*

  6. Add the additional roles with the permission to the audit user's role.

After these steps are complete, your audit user should have the required permissions and you can complete the Immuta install like normal.

create an OpenSearch domain
create a new user
Create a role