Skip to content

Conversation

@rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Sep 19, 2025

"node to node" encryption is currently configurable for ElasticSearch domains, but not "encryption at rest".

Add a parameter for that option, and turn it on by default for E2E tests.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Python 3.8 and 3.9 are end of life, upgrade to a recent
supported Python version.
@rix0rrr rix0rrr requested a review from a team as a code owner September 19, 2025 10:15
@rix0rrr rix0rrr changed the title Huijbers/node encryption configurable feat: make node encryption configurable Sep 19, 2025
@rix0rrr rix0rrr changed the title feat: make node encryption configurable feat: make ElasticSearch server-side encryption configurable Sep 19, 2025
@mrgrain
Copy link
Contributor

mrgrain commented Sep 25, 2025

Closing in favor of #3340

@mrgrain mrgrain closed this Sep 25, 2025
@rix0rrr rix0rrr reopened this Sep 26, 2025
@rix0rrr
Copy link
Contributor Author

rix0rrr commented Sep 26, 2025

Closing in favor of #3340

No that isn't the entire story yet. We do need this as well.

That PR configures a currently available setting (node to node encryption). This adds a new setting (server-side encryption).

@rix0rrr rix0rrr changed the title feat: make ElasticSearch server-side encryption configurable feat: ElasticSearch server-side encryption Oct 10, 2025
@rix0rrr rix0rrr requested a review from a team as a code owner October 13, 2025 08:20
@rix0rrr rix0rrr merged commit 51b67e0 into main Oct 14, 2025
8 checks passed
@rix0rrr rix0rrr deleted the huijbers/node-encryption-configurable branch October 14, 2025 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants