> 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/iam/appsec2-aws-52.md).

# AWS OpenSearch Fine-grained access control is disabled misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_52                     |
| Category - Subcategory | IAM - Overly Permissive              |
| Provider               | AWS                                  |
| Severity               | LOW                                  |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | 512be9cc-ed41-4e18-a4ba-c5419c07b5e7 |

## Impact

This rule detects AWS ElasticSearch/OpenSearch domains that do not have fine-grained access control enabled. Fine-grained access control allows you to manage access to specific domain actions based on user roles and permissions.

## How to Fix

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

* *Arguments:* advanced\_security\_options.internal\_user\_database\_enabled, advanced\_security\_options.enabled

To fix the issue, set the `fine_grained_access_control_enabled` argument to `true` in the `aws_elasticsearch_domain` resource.

Secure code example:

## Enabling `internal_user_database_enabled` ensures that AWS ElasticSearch/OpenSearch domains have fine-grained access control enabled, providing more granular control over user roles and permissions. \[source,go]

resource "aws\_elasticsearch\_domain" "example" { // other arguments advanced\_security\_options {

* enabled = true
* internal\_user\_database\_enabled = true } }

***


---

# 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/iam/appsec2-aws-52.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.