Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
opensearch_service_domains_node_to_node_encryption_enabledProvider: AWS
Service:
opensearchSeverity: HIGH
Categories:
encryptionResource type:
AwsOpenSearchServiceDomainWhat this check verifies
Amazon OpenSearch domains with node-to-node encryption use TLS to protect traffic between cluster nodes. The finding evaluates the domain’snode_to_node_encryption configuration for intra-cluster communications.
Risk
Unencrypted intra-cluster traffic enables interception and manipulation by anyone with network foothold.- Confidentiality: exposure of documents, credentials, metadata
- Integrity: tampering with queries and shard replication
- Availability: spoofing/MITM can disrupt coordination and cause outages
Recommendation
Enable node-to-node encryption (node_to_node_encryption: true) to enforce TLS for inter-node traffic. Apply defense in depth: require HTTPS for clients, restrict network exposure, and use least privilege. Validate performance in staging and plan carefully, as the setting is effectively irreversible.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/ntn.html
- https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ntn.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/Elasticsearch/node-to-node-encryption.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = opensearch_service_domains_node_to_node_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks