Skip to main content

Triage and Remediation

Remediation

Using Console

To remediate the misconfiguration of Node-to-Node Encryption not being enabled on an AWS OpenSearch Service domain, you can follow these step-by-step instructions using the AWS Management Console:
  1. Navigate to AWS OpenSearch Service Console:
    • Go to the AWS Management Console (https://console.aws.amazon.com/)
    • In the “Find services” search bar, type “OpenSearch Service” and select it from the dropdown.
  2. Select the OpenSearch Service Domain:
    • From the list of OpenSearch Service domains, select the domain for which you want to enable Node-to-Node Encryption.
  3. Enable Node-to-Node Encryption:
    • In the domain dashboard, click on the domain name to go to the domain details page.
    • In the left-hand navigation pane, click on the “Configure domain” tab.
  4. Edit the Security Configuration:
    • Scroll down to the “Security” section and click on the “Edit” button next to the “Node-to-Node Encryption” setting.
  5. Enable Node-to-Node Encryption:
    • Toggle the switch to enable Node-to-Node Encryption.
    • You may also have the option to provide a custom encryption key or use the default AWS managed key.
  6. Save Changes:
    • Once you have enabled Node-to-Node Encryption, click on the “Save changes” button to apply the configuration.
  7. Verify Node-to-Node Encryption:
    • To ensure that Node-to-Node Encryption is successfully enabled, you can check the domain status or perform a test query to confirm the encryption is in place.
  8. Monitor the Domain:
    • After enabling Node-to-Node Encryption, monitor the domain for any issues and ensure that all nodes are communicating securely.
By following these steps, you can successfully remediate the misconfiguration of Node-to-Node Encryption not being enabled on an AWS OpenSearch Service domain using the AWS Management Console.

To remediate the misconfiguration of enabling Node-to-Node Encryption for AWS OpenSearch Service domains using AWS CLI, you can follow these steps:
  1. Enable Node-to-Node Encryption: Run the following AWS CLI command to enable Node-to-Node encryption for your OpenSearch Service domain:
    Replace YOUR_DOMAIN_NAME with the name of your OpenSearch Service domain.
  2. Verify Node-to-Node Encryption: You can verify that Node-to-Node encryption is enabled for your OpenSearch Service domain by describing the domain configuration:
    Ensure that the NodeToNodeEncryptionOptions parameter shows Enabled: true.
  3. Monitor the Configuration: It is recommended to monitor the OpenSearch Service domain for any issues after enabling Node-to-Node encryption to ensure that the domain continues to function properly.
By following these steps, you can successfully remediate the misconfiguration of enabling Node-to-Node Encryption for AWS OpenSearch Service domains using the AWS CLI.
To remediate the misconfiguration of enabling Node-to-Node Encryption for AWS OpenSearch Service domains using Python, you can utilize the AWS SDK for Python (Boto3) to update the domain configuration. Here are the step-by-step instructions to remediate this issue:
  1. Install Boto3: Ensure you have Boto3 installed in your Python environment. You can install it using pip:
  1. Update OpenSearch Domain Configuration: Create a Python script with the following code to update the OpenSearch domain configuration to enable Node-to-Node Encryption:
  1. Configure AWS Credentials: Ensure that your AWS credentials are properly configured either through environment variables, AWS CLI configuration, or IAM roles.
  2. Run the Python Script: Execute the Python script you created in step 2. This script will update the specified OpenSearch domain configuration to enable Node-to-Node Encryption.
After running the script, the Node-to-Node Encryption should be successfully enabled for the specified AWS OpenSearch Service domain.
Enabling node_to_node_encryption_options.enabled = true on an existing domain will not force Terraform to replace the domain, but AWS will perform a blue/green deployment; the domain stays operational while the change is applied and you cannot make other config changes until it completes.After updating your Terraform, terraform plan should show an in-place update on aws_opensearch_domain.THIS_DOMAIN with node_to_node_encryption_options.enabled changing from false (or null) to true.