OpenSearch domain does not encrypt traffic between its nodes
- Severity
- Medium
- Service
- OpenSearch
- Check ID
- ES_NODE_TO_NODE_NOT_ENCRYPTED
What this check finds
Node-to-node encryption is off, so data moving between the domain's nodes inside the VPC or AWS network is not protected by TLS.
Passing looks like: OpenSearch domains encrypt node-to-node traffic.
How to fix it
Enable node-to-node encryption.
AWS console
Amazon OpenSearch Service → Domains → select domain → Security configuration → Edit → Node-to-node encryption.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs