Add an option to configure S3 repository to store snapshots out of the box #1222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The aim of this PR is to add an ability to use S3 compatible storage for snapshot management out of the box. It is made possible by allowing to build
wazuh-indexer
docker image with additional pluginrepository-s3
installed, via a new optional--s3-repository
parameter. Parameter--s3-repository
is set tofalse
by default. Onwazuh-indexer
container startup, ifrepository-s3
plugin is installed, the system will attempt to readAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
environment variables and add their values to the OpenSearch keystore.Example of changes to single-node/config/wazuh_indexer/wazuh.indexer.yml:
Example of changes to single-node/docker-compose.yml: