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

# State machine does not have X-ray tracing enabled misconfiguration detected in code

## Rule Details

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

## Impact

This rule is checking to make sure that X-Ray tracing is enabled for the State Machine in Amazon Web Services (AWS). X-Ray tracing provides insight into the behavior of your applications. By enabling this feature, you can analyze your applications' performance and troubleshoot issues that could potentially affect the user experience. If X-Ray tracing is not enabled, you may lack the necessary visibility into your applications' operations, which could make it difficult to identify and resolve issues quickly and effectively. This could potentially lead to prolonged downtimes and may negatively impact your service's reliability and your users' satisfaction.

## How to Fix

*Resource:* aws\_sfn\_state\_machine

* *Arguments:* tracing\_configuration.enabled

To fix the issue, you need to enable X-Ray tracing for your State Machine. You can do this by setting the `tracing_configuration` block in your AWS Step Function (State Machine) resource to `enabled = true`.

The fixed code would look like this:

## The above code is secure because it enables X-Ray tracing for the State Machine. This allows you to trace the execution of the State Machine, which is important for debugging and latency analysis. It also helps in identifying performance bottlenecks, which can be critical in optimizing your application. \[source,go]

resource "aws\_sfn\_state\_machine" "sfn\_state\_machine" { name = "sfn\_state\_machine" role\_arn = aws\_iam\_role.role.arn

## definition = <\<EOF { /\* Step Function definition \*/ } EOF tracing\_configuration { enabled = 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/logging/appsec-aws-284.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.