> 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/phase-3-complete-the-onboarding-wizard-in-cortex.md).

# Phase 3: Complete the onboarding wizard in Cortex

After creating all AWS resources, provide the following details in the Cortex AWS onboarding wizard. These details correspond to the data that the automated CloudFormation flow sends via its Lambda callback:

Account details:

| Field        | Value                           | How to Retrieve                                             |
| ------------ | ------------------------------- | ----------------------------------------------------------- |
| Account ID   | Your 12-digit AWS account ID    | `aws sts get-caller-identity --query Account --output text` |
| Account Name | A display name for this account | User-defined                                                |

Credentials:

| Field       | Value                                      | How to Retrieve                                                                                                                                                                                                     |
| ----------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Role ARN    | ARN of the Cortex Platform Role (Step 2.2) | `aws iam get-role --role-name "${CORTEX_ROLE_NAME}" --query Role.Arn --output text`                                                                                                                                 |
| External ID | The ExternalID cthat you chose             | The `EXTERNAL_ID` value that you set in [Set up your variables](https://cortex-docs.paloaltonetworks.com/amazon-web-services-manual-onboarding/readme/phase-2-provision-the-aws-resources.md#set-up-your-variables) |

Audit log collection (BYOB) resources:

| Field               | Value                                           | How to Retrieve                                                                         |
| ------------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------- |
| SQS Queue URL       | URL of the CloudTrail logs SQS queue (Step 2.3) | `aws sqs get-queue-url --queue-name "${SQS_QUEUE_NAME}" --query QueueUrl --output text` |
| CloudTrail Role ARN | ARN of the CloudTrail read role (Step 2.6)      | `aws iam get-role --role-name "${LOGS_ROLE_NAME}" --query Role.Arn --output text`       |

Scanner (optional):

| Field               | Value                                 | How to Retrieve                                                                                                                                                                                                             |
| ------------------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scanner Role ARN    | ARN of the Scanner Role (Step 2.7)    | `aws iam get-role --role-name "${SCANNER_ROLE_NAME}" --query Role.Arn --output text`                                                                                                                                        |
| Scanner External ID | The scanner ExternalID that you chose | The `SCANNER_EXTERNAL_ID` value that you set in [Set up your variables](https://cortex-docs.paloaltonetworks.com/amazon-web-services-manual-onboarding/readme/phase-2-provision-the-aws-resources.md#set-up-your-variables) |

### Quick retrieval script

You can use the following script to retrieve all of the required details at once:

```shell
echo "=== Details to provide to Cortex ==="
echo ""
echo "Account ID:             ${AWS_ACCOUNT_ID}"
echo "Role ARN:               $(aws iam get-role --role-name "${CORTEX_ROLE_NAME}" --query Role.Arn --output text)"
echo "External ID:            ${EXTERNAL_ID}"
echo "SQS Queue URL:          $(aws sqs get-queue-url --queue-name "${SQS_QUEUE_NAME}" --query QueueUrl --output text)"
echo "CloudTrail Role ARN:    $(aws iam get-role --role-name "${LOGS_ROLE_NAME}" --query Role.Arn --output text)"

# If using outpost scanning:
# echo "Scanner Role ARN:       $(aws iam get-role --role-name "${SCANNER_ROLE_NAME}" --query Role.Arn --output text)"
# echo "Scanner External ID:    ${SCANNER_EXTERNAL_ID}"
```

Note: In the automated CloudFormation flow, a Lambda function sends these details to Cortex automatically using a callback URL. In the manual flow, you enter them manually in the Cortex AWS onboarding wizard.

### Format requirements

Ensure the values you provide match the expected formats:

| Field           | Format                                                            |
| --------------- | ----------------------------------------------------------------- |
| Account ID      | Exactly 12 digits (e.g., 123456789012)                            |
| Organization ID | Starts with r- followed by alphanumeric characters (e.g., r-ab12) |
| SQS URL         | <https://sqs..amazonaws.com//>                                    |
| Role ARNs       | Valid AWS ARN format: arn:aws:iam:::role/                         |


---

# 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/phase-3-complete-the-onboarding-wizard-in-cortex.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.
