> 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/networking/appsec-aws-150.md).

# AWS Elastic Load Balancer v2 with deletion protection feature disabled misconfiguration detected in

## Rule Details

|                        |                                  |
| ---------------------- | -------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_150                 |
| Category - Subcategory | Public Exposure - Load Balancing |
| Provider               | AWS                              |
| Severity               | LOW                              |
| Framework              | Terraform, Terraform Plan        |

## Impact

This rule is checking to ensure that the Load Balancer on an AWS cloud network has enabled deletion protection. The absence of this protection can be harmful because it puts the system at the risk of accidental or unintended deletion, leading to disruption of network services and possibly loss of data.

## How to Fix

To fix the issue highlighted by the mentioned rule, you should enable the deletion protection for your load balancer in AWS.

## With the given secure code, the `enable_deletion_protection = true` ensures that the deletion protection is enabled for the load balancer. Thus, AWS prevents the load balancer from being deleted accidentally, which makes the infrastructure secure. \[source,go]

resource "aws\_elb" "example" { name = "example" availability\_zones = \["us-west-2a", "us-west-2b", "us-west-2c"]

listener { instance\_port = 80 instance\_protocol = "http" lb\_port = 80 lb\_protocol = "http" }

## enable\_deletion\_protection = 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/networking/appsec-aws-150.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.