> 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/storage/appsec-aws-293.md).

# AWS database instances do not have deletion protection enabled misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_293                     |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | AWS                                  |
| Severity               | MEDIUM                               |
| Framework              | Terraform, Terraform Plan            |

## Impact

This rule is checking for whether AWS database instances have deletion protection enabled or not. If deletion protection is disallowed, there could be potential accidental loss of valuable or critical data. This can happen due to an inadvertent user action. Therefore, it's important for AWS database instances to have deletion protection enabled to prevent the unexpected removal of database that might cause data loss or downtime issues.

## How to Fix

*Terraform*

* *Resource:* aws\_db\_instance
* *Arguments:* deletion\_protection

To fix the issue:

You need to enable `deletion_protection` parameter in the AWS instance block. This ensures that the termination of this DB instance is prevented when this parameter is set to 'true'.

## The above code is secure because the `deletion_protection` is set to `true`. This parameter ensures that the AWS database instance cannot be deleted. This adds an extra layer of security against accidental deletions of the AWS database instances. \[source,go]

resource "aws\_db\_instance" "default" { ...

* 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 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/storage/appsec-aws-293.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.