> 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/logging/appsec-aws-95.md).

# AWS API Gateway V2 has Access Logging is disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_95               |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AWS                           |
| Severity               | LOW                           |
| Framework              | CloudFormation, Serverless    |

## Impact

Enabling access logging for API Gateway V2 (including both HTTP APIs and WebSocket APIs) is critical for monitoring and auditing API usage. Access logging provides detailed records of requests sent to your API, including requester IP, requested paths, response status, and latency. This information is invaluable for troubleshooting, understanding API usage patterns, and identifying potential security threats. This rule ensures that access logging is configured for API Gateway V2 stages, thereby enhancing the observability and security of your API infrastructure.

## How to Fix

Resources:\* AWS::ApiGatewayV2::Stage, AWS::Serverless::HttpApi *Logging Configuration:* Ensure the AccessLogSettings property specifies a DestinationArn for storing access logs.

## This configuration snippet demonstrates how to enable access logging for an API Gateway V2 stage by specifying a destination ARN for the logs, following best practices for API management and security. \[source,go]

Resources: MyHttpApi: Type: AWS::ApiGatewayV2::Stage Properties: ApiId: !Ref MyApi StageName: 'prod' AccessLogSettings:

* DestinationArn: !GetAtt MyLogGroup.Arn Format: '{"requestId":"$context.requestId", "ip":"$context.identity.sourceIp", "requestTime":"$context.requestTime", "httpMethod":"$context.httpMethod", "routeKey":"$context.routeKey", "status":"$context.status", "protocol":"$context.protocol", "responseLength":"$context.responseLength"}' MyLogGroup: Type: AWS::Logs::LogGroup Properties: LogGroupName: /aws/apigateway/myhttpapi/logs RetentionInDays: 365

***


---

# 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/logging/appsec-aws-95.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.