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

# AWS S3 bucket Object not encrypted using Customer Managed Key misconfiguration detected in code

## AWS S3 bucket Object not encrypted using Customer Managed Key misconfiguration detected in code

### Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_186          |
| Category - Subcategory | Storage - Encryption      |
| Provider               | AWS                       |
| Severity               | LOW                       |
| Framework              | Terraform, Terraform Plan |

### Impact

This is a simple check to ensure that the S3 bucket Object is using AWS key management - KMS to encrypt its contents. To resolve add the ARN of your KMS or link on creation of the object.

### How to Fix

*Resource:* aws\_s3\_bucket\_object

* *Attribute:* kms\_key\_id - (Optional) Specifies the AWS KMS Key ARN to use for object encryption. This value is a fully qualified ARN of the KMS Key. \[source,go]

***

resource "aws\_s3\_bucket\_object" "object" { bucket = "your\_bucket\_name" key = "new\_object\_key" source = "path/to/file"

* kms\_key\_id = "ckv\_kms"

## The filemd5() function is available in Terraform 0.11.12 and later

## For Terraform 0.11.11 and earlier, use the md5() function and the file() function:

## etag = "${md5(file("path/to/file"))}"

### etag = filemd5("path/to/file") }


---

# 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-186.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.