> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec2-aws-59.md).

# AWS Elasticsearch domain has Dedicated master set to disabled misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_59                     |
| Category - Subcategory | Compute - Overprovisioned            |
| Provider               | AWS                                  |
| Severity               | LOW                                  |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | ea657be6-6810-4964-9a15-81a8f0177784 |

## Impact

This rule checks if Elasticsearch/OpenSearch clusters are configured with a dedicated master node. Having a dedicated master node for Elasticsearch/OpenSearch clusters helps ensure that the cluster’s state and health status is managed properly and prevents the cluster from becoming unstable in case of failures.

## How to Fix

*Resource:* aws\_opensearch\_domain, aws\_elasticsearch\_domain

* *Arguments:* cluster\_config.dedicated\_master\_enabled

To fix the issue, ensure the 'dedicated\_master\_enabled' configuration is set to 'true' inside the 'cluster\_config' block of the Elasticsearch or OpenSearch domain resource.

Secure code example:

The above code is secure as it enables a dedicated master node in the Elasticsearch/OpenSearch domain, which provides better control and stability over the cluster's state and health status. \[source,go] ----resource "aws\_elasticsearch\_domain" "example" { domain\_name = "example"

cluster\_config { instance\_count = 5

* dedicated\_master\_enabled = true dedicated\_master\_type = "m3.medium.elasticsearch" } }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec2-aws-59.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.