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

# AWS AppSync's logging is disabled misconfiguration detected in code

## Rule Details

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

## Impact

This rule ensures that AWS AppSync GraphQL APIs have logging enabled. Enabling logging for AppSync allows you to capture, store, and analyze the API activity, which is crucial for monitoring, troubleshooting, and ensuring the security of your API. This rule checks whether the `CloudWatchLogsRoleArn` property in the `LogConfig` configuration is set to a valid value.

## How to Fix

To fix this issue, ensure that the `CloudWatchLogsRoleArn` property in the `LogConfig` configuration of the `AWS::AppSync::GraphQLApi` resource is set to a valid IAM role ARN that grants permission to write logs to CloudWatch.

## Example: \[source,go]

## Resources: MyAppSyncGraphQLApi: Type: AWS::AppSync::GraphQLApi Properties: Name: example-api AuthenticationType: API\_KEY LogConfig: CloudWatchLogsRoleArn: arn:aws:iam::123456789012:role/appsync-logging-role FieldLogLevel: ALL ...


---

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