> 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-91.md).

# AWS Elastic Load Balancer v2 (ELBv2) with access log disabled misconfiguration detected in code

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_91                                       |
| Category - Subcategory | Logging - Disabled or missing                         |
| Provider               | AWS                                                   |
| Severity               | LOW                                                   |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | b9cdd43b-3483-48a1-9a98-313c40d3989f                  |

## Impact

ELBv2 provide access logs that capture information about the TLS requests sent to NLBs. These access logs can be used to analyze traffic patterns and troubleshoot security and operational issues. Access logging is an optional feature of ELB that is disabled by default. There is no additional charge for access logs. You are charged storage costs for Amazon S3, but not charged for the bandwidth. After you enable access logging for your load balancer, ELBv2 captures the logs as compressed files and stores them in the Amazon S3 bucket that you specify.

## How to Fix

## \*Resource: AWS::ElasticLoadBalancingV2::LoadBalancer \*Argument: Properties.LoadBalancerAttributes \[source,go]

Resources: Resource0: Type: 'AWS::ElasticLoadBalancingV2::LoadBalancer' Properties: ... LoadBalancerAttributes:

* * Key: access\_logs.s3.enabled
* Value: "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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/logging/appsec-aws-91.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.