> 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/compute/appsec-aws-313.md).

# RDS cluster is not configured to copy tags to snapshots misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_313               |
| Category - Subcategory | Compute - Startup Script Leaks |
| Provider               | AWS                            |
| Severity               | LOW                            |
| Framework              | Terraform, Terraform Plan      |

## Impact

This rule is checking to ensure that an AWS RDS (Relational Database Service) cluster is configured to copy tags to snapshots. Tags are important in AWS as they allow users to categorize AWS resources in different ways, such as by purpose, owner, or environment.

If the RDS cluster is not configured to copy tags to snapshots, it could result in operational confusion and challenges in understanding the nature of the snapshot, its purpose and its owner or the entity it belongs to. Moreover, some organizations also use resource tags to track billing or manage costs. Hence, not having these tags on snapshots could impact these processes. Therefore, it's not ideal if the RDS cluster isn't configured to do so.

## How to Fix

*Resource:* aws\_rds\_cluster

* *Arguments:* copy\_tags\_to\_snapshot

## Include the `copy_tags_to_snapshot` parameter in your AWS RDS instance configuration and set it to `true`. This is to ensure that all tags on the RDS instance are copied over to any snapshots created from the instance. \[source,go]

resource "aws\_db\_instance" "default" { allocated\_storage = 10 engine = "mysql" engine\_version = "5.7" instance\_class = "db.t2.micro" name = "mydb" username = "foo" password = "foobarbaz" parameter\_group\_name = "default.mysql5.7" skip\_final\_snapshot = true

* copy\_tags\_to\_snapshot = 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/compute/appsec-aws-313.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.