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

# S3 bucket policy allows lockout all but root user misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_93           |
| Category - Subcategory | Storage - Permissions     |
| Provider               | AWS                       |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is designed to prevent configuration policies that could potentially lock out non-root users from accessing S3 buckets. This check is vital for maintaining access control in AWS environments and ensuring that bucket policies do not inadvertently create security risks by overly restrictive configurations.

## How to Fix

*Resource:* aws\_s3\_bucket, aws\_s3\_bucket\_policy

* *Argument:* policy

## Do not deny overly broad actions with a broad set of resources for all principals in an S3 policy. \[source,go]

resource "aws\_s3\_bucket" "example" { bucket = "example" }

resource "aws\_s3\_bucket\_policy" "example" { bucket = aws\_s3\_bucket.example.id

policy = <\<POLICY { "Version": "2012-10-17", "Statement": \[ { "Effect": "Deny",

* "Principal": "\*",
* "Principal": { "AWS":"some\_arn" }, "Action": "s3:\*",
* "Resource": \["arn:aws:s3:::example/\*", "arn:aws:s3:::example"] } ] } POLICY }

***


---

# 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/storage/appsec-aws-93.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.