> 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/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/aws-post-deployment-verification.md).

# AWS post-deployment verification

After you have completed the AWS onboarding wizard and you have deployed the authentication template in AWS (using CloudFormation or Terraform), verify that the deployment succeeded.

After you have deployed the authentication template in Amazon Web Services (AWS), verify that it was successfully deployed. In Cortex XSIAM, select **Data Sources & Integrations → Cloud Accounts**. Verify the following:

* The original cloud instance remains in "Pending" state. For more details on pending instances, see Understand pending instances.
* A new cloud instance appears in the cloud accounts list (separate from the pending instance).
* The new cloud instance shows status "Connected".
* The discovery scan starts automatically for every discovered account.
* Assets appear in the **Asset Inventory** as discovery progresses.

## Troubleshooting AWS onboarding

If no new cloud instance appears:

* Check the CloudFormation stack status in the AWS console. The status should be **CREATE\_COMPLETE**.
* Check the Lambda execution logs in AWS CloudWatch for errors. If the Lambda notification to Cortex XSIAM is not executed, Cortex XSIAM does not create a new cloud instance in Connected stated.
* You can [Manually connect an instance](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/manually-connect-a-cloud-instance.md) to create the instance from the pending cloud instance.


---

# 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/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/aws-post-deployment-verification.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.