> 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/public-exposure/appsec2-aws-66.md).

# MWAA environment is publicly accessible misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_66                     |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | AWS                                  |
| Severity               | HIGH                                 |
| Framework              | Terraform, Terraform Plan            |

## Impact

Managed Workflows for Apache Airflow (MWAA) is a managed orchestration service that makes it easier to execute Apache Airflow workflows in the cloud. Ensuring the environment is not publicly accessible helps in preventing unauthorized access. Public accessibility may expose sensitive information or make the environment susceptible to threats.

We recommend setting the MWAA environment's `webserver_access_mode` attribute to `PRIVATE_ONLY` to ensure that the environment remains inaccessible to the public. If the `webserver_access_mode` attribute does not exist or is set to any other value, it indicates that the environment may be publicly accessible.

## How to Fix

*Resource:* aws\_mwaa\_environment

* *Arguments:* webserver\_access\_mode \[source,go]

***

resource "aws\_mwaa\_environment" "example" { //... \[Other resource configurations]

* webserver\_access\_mode = "PRIVATE\_ONLY" }

***


---

# 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/public-exposure/appsec2-aws-66.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.