-
Notifications
You must be signed in to change notification settings - Fork 415
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add option to use s3 compatible storage for snapshot management
Allow to build `wazuh-indexer` docker image with additional plugin `repository-s3` installed, via a new optional `--s3-repository` parameter. Parameter `--s3-repository` is set to `false` by default. On `wazuh-indexer` container startup, if `repository-s3` plugin is installed, the system will attempt to read `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables and add their values to the OpenSearch keystore. For an S3 compatible storage to be configured as a snapshot repository correctly, some additional steps must be taken, mainly: 1. `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_REGION` environment variables must be added to `docker-compose.yml` for the `wazuh.indexer` service. E.g.: ```yaml ... wazuh.indexer: ... environment: ... - "AWS_ACCESS_KEY_ID=exampleAccessKeyID" - "AWS_SECRET_ACCESS_KEY=exampleSecretAccessKey" - "AWS_REGION=us-west-1" ... ``` 2. Additional settings for the S3 compatible storage must be added to `config/wazuh_indexer/wazuh.indexer.yml`. E.g.: ```yaml ... s3.client.default.endpoint: minio:9000 s3.client.default.protocol: http s3.client.default.max_retries: 3 s3.client.default.read_timeout: 50s s3.client.default.path_style_access: true s3.client.default.use_throttle_retries: true ``` See https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore/ for more information.
- Loading branch information
Showing
6 changed files
with
50 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters