> 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/logging/appsec-aws-84.md).

# AWS Elasticsearch domain logging is not enabled misconfiguration detected in code

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_84                                       |
| Category - Subcategory | Logging - Disabled or missing                         |
| Provider               | AWS                                                   |
| Severity               | MEDIUM                                                |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |

## Impact

Amazon Elasticsearch Service (Amazon ES) exposes logs through CloudWatch. ES logs enable troubleshooting performance and stability issues, as well as audit logs to track user activity for compliance purposes. Supported ES logs include error logs, search slow logs, index slow logs, and audit logs. All logs are disabled by default.

We recommend you enable Elasticsearch domain logging.

NOTE: If enabled, standard CloudWatch pricing applies.

## How to Fix

*Resource:* AWS::Elasticsearch::Domain

* *Arguments:* Properties.LogPublishingOptions.AUDIT\_LOGS.Enabled \[source,go]

***

{ "Resources: Resource0: Type: 'AWS::Elasticsearch::Domain' Properties: ... LogPublishingOptions: AUDIT\_LOGS:

* 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/logging/appsec-aws-84.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.