> 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/iam/appsec2-aws-70.md).

# AWS API Gateway method lacking authorization or API keys misconfiguration detected in code

## AWS API Gateway method lacking authorization or API keys misconfiguration detected in code

### Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_70          |
| Category - Subcategory | Public Exposure - APIs    |
| Provider               | AWS                       |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

### Impact

This rule detects whether an API Gateway method is missing authorization or an API key. It is crucial to implement these security measures to ensure that only authenticated and authorized users can access the API. Without such controls, APIs could be exposed to unauthorized access and potential misuse, leading to data breaches, unauthorized data modifications, and other security vulnerabilities. Proper authorization mechanisms and API keys help safeguard sensitive information and maintain the integrity of the API.

### How to Fix

*Resource:* aws\_api\_gateway\_method, aws\_api\_gateway\_rest\_api

* *Arguments:* authorization, api\_key\_required

### In this example, the Terraform configuration defines an API Gateway method and configures it for secure access using AWS IAM authentication and an API key. \[source,go]

resource "aws\_api\_gateway\_method" "example" { ...

## Ensure that authorization is set

authorization = "AWS\_IAM"

## Optionally, you can also indicate that an API key is required

### api\_key\_required = 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/iam/appsec2-aws-70.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.