> 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/amazon-web-services-manual-onboarding/readme/prerequisites.md).

# Prerequisites

* Ensure you have the necessary permissions:
  * In Cortex, you must have a Cortex role with **Data Sources - View & Edit** permissions (to add/configure cloud accounts in Cortex). This role is included in the following built-in roles: Instance Administrator, Security Admin, and IT Admin.
  * In AWS, ensure the AWS CLI is configured with permissions to create IAM roles/policies, SQS queues, and SNS subscriptions.
* You must have the following set up in your AWS account:
  * **CloudTrail**: The AWS service that records everything that happens in your account. The CloudTrail must already be turned on and running.
  * **S3 Bucket**: A cloud storage folder where CloudTrail saves its log files. The S3 bucket must already exist and CloudTrail must already be configured to write logs into it.
  * **SNS**: A notification service that forwards messages from CloudTrail to SQS. The SNS topic must already exist and CloudTrail must already be configured to send notifications to it.

{% hint style="info" %}
**Note:** For audit log collection to function as expected, the CloudTrail, S3 bucket and SNS topic must be in the same management account.
{% endhint %}


---

# 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/amazon-web-services-manual-onboarding/readme/prerequisites.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.
