Other Articles
- IAM - Enable User MFA
- IAM - Enforce Key Rotation
- IAM - Enforce Active Key Limit
- IAM - Disable Unused User Credentials
- IAM - Enforce Group Permission
- IAM - Enforce Password Length
- IAM - Prohibit Password Reuse
- IAM - Check Root Access Keys Existence
- IAM - Enable Root MFA
- IAM - Establish Support Role
- IAM - Enable Key Rotation
- Purge Expired Certificates
- EC2 Volume – Enable EBS Volume Backup
- EC2 Volume – Enable EBS Encryption
- EFS – Enable EFS Storage Backup
- S3 Bucket – Enable S3 Bucket Versioning
- S3 Bucket – Enable S3 Bucket Encryption
- S3 Bucket – Block S3 Bucket Public Access
- RDS DB Instance – Encryption of Storage
- RDS DB Instance – Enable Deletion Protection
- RDS DB Instance – Enable Auto Minor Version Upgrade
- DynamoDB Table – Enable Table Encryption
- DynamoDB Table – Enable Table Point In Time Recovery
- DynamoDB Table – Enable Table Deletion Protection
- EKS Cluster – Enable Secrets Encryption
- OpenSearch Domain – Enable Encryption at Rest
- RDS DB Cluster – Retain Backups for 7 Days
- RDS DB Cluster – Encryption of Storage
- RDS DB Cluster – Enable Deletion Protection
- EC2 Instance – Monitor CPU Utilization
- ECS Service – Monitor CPU Utilization
- ECS Service – Monitor Memory Utilization
- RDS DB Instance – Monitor Free Storage Space
- RDS DB Instance – Monitor CPU Utilization
- SQS Queue – Monitor Message Age
- SQS Queue – Monitor Message Visibility
- DynamoDB Table – Monitor Table Read Capacity
- DynamoDB Table – Monitor Table Write Capacity
- DynamoDB Table – Monitor Table Latency
- Enable CloudTrail
- Encrypt CloudTrail Logs
- EC2 VPC – Ensure Flow Logs are Enabled
- EKS Cluster – Enable Control Plane Logging
- CloudWatch Log Group – Enable KMS Encryption
- CloudWatch Log Group – Configure Retention
- Load Balancer – Enable Access Logs
- RDS DB Instance – Block Public Access
- EC2 Security Group – Restrict Public SSH and RDP Access
- EC2 Security Group – Restrict Public Database Access
- EKS Cluster – Restrict Public Endpoint
- EC2 VPC – Restrict Default Security Group Traffic
- Load Balancer – Redirect HTTP Traffic to HTTPS
- Load Balancer – Use Strong TLS Policies
- OpenSearch Domain – Enforce HTTPS
- OpenSearch Domain – Restrict Public Access
- RDS DB Cluster – Block Public Access
- EC2 Instance – Enable Deletion Protection
- ECS Service – Enable Auto Scaling
- Load Balancer – Enable Deletion Protection
- Enable AWS Security Hub
- Enable GuardDuty
- CloudFront Distribution – Enforce HTTPS for Viewers
- CloudFront Distribution – Require TLS 1.2 for Viewers
- CloudFront Distribution – Associate a WAF Web ACL
- CloudFront Distribution – Protect S3 Origin Access
- KMS Key – Avoid Pending Deletion
- SNS Topic – Enable Encryption
- SNS Topic – Restrict Topic Policy Access
OpenSearch Domain – Enable Node-to-Node Encryption
Secure Configuration Checks > AWS
This check ensures that node-to-node encryption is enabled for Amazon OpenSearch Service domains. With it, all traffic between the nodes of the domain is encrypted with TLS. Without it, data that moves inside the cluster, such as replicated documents and search requests, travels in clear text.
Check Details
- Resource: OpenSearch Service Domain
- Check: Enable OpenSearch domain node-to-node encryption (
NodeToNodeEncryptionEnabled) - Risk: Anyone who can observe network traffic inside the VPC can read or capture data that moves between the nodes
Remediation via AWS Console
-
Log in to the AWS Management Console and open the Amazon OpenSearch Service console.
- In the left navigation pane, click Domains and select the affected domain.
-
Open the Security configuration tab and click Edit.
-
Under Encryption, select Enable node-to-node encryption.
- Click Save changes. Wait until the domain status is Active and the change is complete.
- Repeat steps 2 to 5 for every domain without node-to-node encryption.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the CloudShell icon (
>_) in the top-right corner.
-
List the domains where node-to-node encryption is not enabled. The output shows the domain name and the setting:
for d in $(aws opensearch list-domain-names \ --query 'DomainNames[].DomainName' --output text); do aws opensearch describe-domain --domain-name "$d" \ --query 'DomainStatus.[DomainName,NodeToNodeEncryptionOptions.Enabled]' \ --output text done | awk '$2 != "True"'The command covers one region. Add
--region <region>to eachawscommand to check another. -
Enable node-to-node encryption:
aws opensearch update-domain-config \ --domain-name <domain-name> \ --node-to-node-encryption-options Enabled=true
-
Check the progress. Wait until
ProcessingisFalse:aws opensearch describe-domain \ --domain-name <domain-name> \ --query 'DomainStatus.Processing'
-
Verify the setting:
aws opensearch describe-domain \ --domain-name <domain-name> \ --query 'DomainStatus.NodeToNodeEncryptionOptions'
Enabledmust betrue.
Replace <domain-name> with the name of the domain, for example my-search-domain.
Repeat steps 3 to 5 for each domain that step 2 lists.
Updated on 04 November, 2026