New features for Elasticsearch image: S3 repository plugin and configure_s3.sh #140
Conversation
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
jesuslinares
suggested changes
Mar 27, 2019
manuasir
approved these changes
Mar 27, 2019
|
|
||
| } | ||
|
|
||
|
|
There was a problem hiding this comment.
Please, write a comment about this function.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi team!
This PR adds
S3 repository pluginandconfigure_s3.shto Elasticsearch image. This features allow us to create a S3 repository on AWS to perform backup operations.The plugin provides a S3 repository type. The repository defaults to using ECS IAM Role or EC2 IAM Role credentials for authentication, but we recommend to add the necessary policy to write on the S3 repository into the instance where Elasticsearch is hosted.
The configure_s3.sh script is launched by load_settings.sh. By default, the environment variable ENABLE_CONFIGURE_S3 is set to false, so it will not create any repository. To successfully create a S3 repository some environment variables are needed:
Optionally, S3_ELASTIC_MAJOR can be set to add the specified version to the path bucket. By default, current Elasticsearch version is checked and added at the end of the path and the repository name.
Best regards,
Mayte Ariza