OpenSearch domains should encrypt data sent between nodes
Checks that the OpenSearch domain has node-to-node encryption on, so traffic between its nodes is TLS 1.2 encrypted and data stays encrypted as OpenSearch distributes it across the cluster. AWS notes it can cost some performance, so test the trade-off before turning it on.
- service
- Opensearch
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Can't be undone: Node-to-node encryption cannot be turned off once on; going back means a new domain built from a manual snapshot of this one.
- Interrupts service: Turning it on runs a blue/green deployment, so latency and rejected requests can rise while data copies; apply it at low traffic.
In the console
OpenSearch Service → Domains → the domain → Actions → Edit security configuration → Encryption
- Node-to-node encryption
- Selected
With the AWS CLI
aws opensearch update-domain-config --domain-name <domain-name> --node-to-node-encryption-options '{"Enabled":true}' --region <region>With Terraform
resource "aws_opensearch_domain" "this" {
domain_name = var.domain_name
node_to_node_encryption {
enabled = true
}
}
See which of your accounts this check is failing on.
Book a live scan