Add prompts for security on OpenSearch and ElasticSearch services #288
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.
Using the search services without security is not simply a case of changing client config, the services need to be configured as well.
This makes using Opensearch and Elasticsearch without security or SSL possible. The defaults are set to secure.
Note that the opensearch change enables HTTP access, which is less troublesome than HTTPS.
The Elasticsearch change enables access without having to provide username and password like:
HTTPS access on Elasticsearch is only available to paid subscriptions and requires a license key, which I dont think this tool would use.