Skip to main content

OpenSearch

You can configure Chef Automate to use OpenSearch clusters that are not deployed via Chef Automate itself.

Configure External OpenSearch

These configuration directions are intended for the initial deployment of Chef Automate.

Automate supports OpenSearch connection over HTTPS or HTTP

Add the following to your config.toml for HTTPS connection:

Warning

The following characters aren’t allowed in passwords:

  • ‘
  • `
  • "
  • '
  • \
  • ;
  • $
[global.v1.external.opensearch]
  enable = true
  nodes = ["https://opensearch1.example:9200", "https://opensearch2.example:9200", "..." ]

# Uncomment and fill out if using external opensearch with SSL and/or basic auth
[global.v1.external.opensearch.auth]
  scheme = "basic_auth"
[global.v1.external.opensearch.auth.basic_auth]
## Create this opensearch user before starting the Chef Automate deployment;
## Chef Automate assumes it exists.
  username = "<admin username>"
  password = "<admin password>"
[global.v1.external.opensearch.ssl]
# Specify either a root_cert or a root_cert_file
  root_cert = """$(cat </path/to/cert_file.crt>)"""
# server_name = "<opensearch server name>"

# Uncomment and fill out if using external OpenSearch that uses hostname-based routing/load balancing
# [esgateway.v1.sys.ngx.http]
#  proxy_set_header_host = "<your external es hostname>:1234"

# Uncomment and add to change the ssl_verify_depth for the root cert bundle
#  ssl_verify_depth = "2"

Add the following to your config.toml for HTTP connection:

Warning

The following characters aren’t allowed in passwords:

  • ‘
  • `
  • "
  • '
  • \
  • ;
  • $
[global.v1.external.opensearch]
  enable = true
  nodes = ["http://opensearch1.example:9200", "http://opensearch2.example:9200", "..." ]

# Uncomment and fill out if using external opensearch with SSL and/or basic auth
[global.v1.external.opensearch.auth]
  scheme = "basic_auth"
[global.v1.external.opensearch.auth.basic_auth]
## Create this opensearch user before starting the Chef Automate deployment;
## Chef Automate assumes it exists.
  username = "<admin username>"
  password = "<admin password>"

Because externally-deployed OpenSearch nodes will not have access to Chef Automate’s built-in backup storage services, you must configure OpenSearch backup settings separately from Chef Automate’s primary backup settings. You can configure backups to use either the local filesystem or S3.

Add Resolvers for OpenSearch

In case you want to resolve the OpenSearch node IPs dynamically using DNS servers, you can add resolvers/nameservers to the configuration.

Name Servers can be added in two ways:

  1. Add nameserver IPs: Add the nameservers to your config.toml file to resolve the OpenSearch nodes.

    [esgateway.v1.sys.ngx.main.resolvers]
  # Multiple resolvers can be specified by adding the resolvers in the list.
  nameservers = ["192.0.2.0:24", "198.51.100.0:24"]

  2. Set system DNS entries: To use existing system nameserver entries from /etc/resolv.conf, add the following setting to config.toml:

    [esgateway.v1.sys.ngx.main.resolvers]
  enable_system_nameservers = true

If both options are set, nameserver IPs takes precedence over the system nameserver entries.

Apply the changes:

sudo chef-automate config patch config.toml

If you wish to reset to the default configuration or to modify the configuration:

  1. Run chef-automate config show config.toml.
  2. Open config.toml and remove the esgateway.v1.sys.ngx.main.resolvers configuration or change the values.
  3. Run chef-automate config set config.toml to apply your changes.

Backup External OpenSearch

Backup External OpenSearch to a Local Filesystem

To configure local filesystem backups of Chef Automate data stored in an externally-deployed OpenSearch cluster:

  1. Ensure that the filesystems you intend to use for backups are mounted to the same path on all OpenSearch master and data nodes.
  2. Configure the OpenSearch path.repo setting on each node as described in the OpenSearch documentation.
  3. Add the following to your config.toml:
[global.v1.external.opensearch.backup]
enable = true
location = "fs"

[global.v1.external.opensearch.backup.fs]
# The `path.repo` setting you've configured on your OpenSearch nodes must be
# a parent directory of the setting you configure here:
path = "/var/opt/chef-automate/backups"

Backup External OpenSearch to AWS S3

To configure AWS S3 backups of Chef Automate data stored in an externally-deployed OpenSearch cluster:

  1. Install the repository-s3 on all nodes in your OpenSearch cluster.

  2. If you wish to use IAM authentication to provide your OpenSearch nodes access to the S3 bucket, you must apply the appropriate IAM policy to each host system in the cluster.

  3. Configure each OpenSearch node with a S3 client configuration containing the proper S3 endpoint, credentials, and other settings as described in the OpenSearch documentation.

  4. Enable S3 backups by adding the following settings to your config.toml:

    [global.v1.external.opensearch.backup]
enable = true
location = "s3"

[global.v1.external.opensearch.backup.s3]

  # bucket (required): The name of the bucket
  bucket = "<bucket name>"

  # base_path (optional):  The path within the bucket where backups should be stored
  # If base_path is not set, backups will be stored at the root of the bucket.
  base_path = "<base path>"

  # name of an s3 client configuration you create in your opensearch.yml
  # for full documentation on how to configure client settings on your
  # OpenSearch nodes
  client = "<client name>"

[global.v1.external.opensearch.backup.s3.settings]
## The meaning of these settings is documented in the S3 Repository Plugin
## documentation.

## Backup repo settings
# compress = false
# server_side_encryption = false
# buffer_size = "100mb"
# canned_acl = "private"
# storage_class = "standard"
## Snapshot settings
# max_snapshot_bytes_per_sec = "40mb"
# max_restore_bytes_per_sec = "40mb"
# chunk_size = "null"
## S3 client settings
# read_timeout = "50s"
# max_retries = 3
# use_throttle_retries = true
# protocol = "https"

Backup External OpenSearch to GCS

To configure Google Cloud Storage Bucket (GCS) backups of Chef Automate data stored in an externally-deployed OpenSearch cluster:

  1. Install the repository-gcs plugin on all nodes in your OpenSearch cluster.

  2. Create a storage bucket and configure a service account to access it per the steps described in the OpenSearch documentation.

  3. Configure each OpenSearch node with a GCS client configuration that contains the proper GCS settings as described in the OpenSearch documentation.

  4. Enable GCS backups by adding the following settings to your config.toml:

    [global.v1.external.opensearch]
  enable = true
  nodes = ["https://my-es.cluster"]
  ## If multiple
  # nodes = ["https://my-es.node-1", "https://my-es.node-2", "etc..."]

## The following settings are required if you have OpenSearch setup with basic auth
#[global.v1.external.opensearch.auth]
#  scheme = "basic_auth"
#
#[global.v1.external.opensearch.auth.basic_auth]
#  username = "everyuser"
#  password = "pass123"

[global.v1.external.opensearch.backup]
  enable = true
  location = "gcs"

[global.v1.external.opensearch.backup.gcs]
  bucket = "<bucket name>"
  # Client name is normally default, but can be set here if you have generated service
  # account credentials with a different client name
  client = "default"

## GCS Bucket Settings:
# type = nearline
# access control = uniform

Configure Embedded OpenSearch

Default configuration applied for OpenSearch:

[opensearch]
  [opensearch.v1]
    [opensearch.v1.sys]
      [opensearch.v1.sys.proxy]
      [opensearch.v1.sys.cluster]
        name = "chef-insights"
        max_shards_per_node = 1000
        [opensearch.v1.sys.cluster.routing]
          [opensearch.v1.sys.cluster.routing.allocation]
            node_concurrent_recoveries = 2
            node_initial_primaries_recoveries = 4
            same_shard_host = false
      [opensearch.v1.sys.node]
        max_local_storage_nodes = 1
        master = true
        data = true
      [opensearch.v1.sys.path]
        logs = "logs"
      [opensearch.v1.sys.indices]
        [opensearch.v1.sys.indices.recovery]
          max_bytes_per_sec = "20mb"
        [opensearch.v1.sys.indices.fielddata]
        [opensearch.v1.sys.indices.breaker]
          total_limit = "95%"
          fielddata_limit = "60%"
          fielddata_overhead = "1.03"
          request_limit = "40%"
          request_overhead = "1"
      [opensearch.v1.sys.bootstrap]
        memory_lock = false
      [opensearch.v1.sys.network]
        host = ""
        port = 10168
      [opensearch.v1.sys.transport]
        port = "10169"
      [opensearch.v1.sys.discovery]
        ping_unicast_hosts = "[]"
        minimum_master_nodes = 1
        zen_fd_ping_timeout = "30s"
      [opensearch.v1.sys.gateway]
        expected_nodes = 0
        expected_master_nodes = 0
        expected_data_nodes = 0
      [opensearch.v1.sys.action]
        destructive_requires_name = true
      [opensearch.v1.sys.logger]
        level = "info"
      [opensearch.v1.sys.plugins]
      [opensearch.v1.sys.runtime]
        max_locked_memory = "unlimited"
        os_java_opts = ""
        heapsize = "8g"
      [opensearch.v1.sys.s3]
        [opensearch.v1.sys.s3.client]
          name = "default"
          read_timeout = "50s"
          max_retries = 3
          use_throttle_retries = true
      [opensearch.v1.sys.index]
        number_of_replicas = 0
        refresh_interval = "1s"

You can choose to override the default configuration by modifying any of the above settings in your config.toml file. Then patch this configuration into your Chef Automate installation by running:

chef-automate config patch </path/to/config.toml>
Edit this page on GitHub

Thank you for your feedback!

×











Search Results