Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

Outpost troubleshooting

Check here for solutions to issues that might occur while configuring, deploying, and operating outposts.

This document provides solutions for issues that might occur while deploying, configuring, and operating Cortex XDR outposts. These troubleshooters can help identify symptoms, locate errors, and suggest how you can remediate.

General troubleshooting

These general troubleshooters apply to all cloud service providers and outpost deployment modes.

The template deployment completes successfully but no outpost appears in Cortex XDR

After the template deployment completes successfully, your cloud environment sends a notification to Cortex XDR to register the new outpost. If the outpost doesn't appear in the Cortex XDR console, verify that outbound internet connectivity is available from the environment where the template was deployed. The notification requires an active connection to reach Cortex XDR. If connectivity is confirmed and the outpost still doesn't appear, contact customer support for a manual workaround.

Terraform template execution fails on a non-approved tenant, such as after changing the target tenant mid-deployment

If Terraform execution fails on a non-approved tenant, such as if you change an Azure target tenant after starting outpost creation. Terraform execution fails because the outpost is bound to the originally-approved tenant. Delete the partially-created outpost from the Cortex console, revert to the approved tenant, and re-run the Terraform template.

An Update available indicator appears next to the outpost status

The outpost template is older than the current template. Hover over the indicator to see the version details. For details, see View and manage outposts.

Standard outpost troubleshooting

Standard outposts handle most of the infrastructure and identity provisioning automatically. Issues in this deployment mode might stem, for example, from broad permission gaps, restrictive policy definitions, or quota limits that prevent Cortex from deploying necessary resources.

AWS CloudFormation deployment troubleshooting

These troubleshooters apply when you deploy an AWS outpost with CloudFormation, either with Execute in AWS or by uploading the downloaded CloudFormation template.

The stack fails because a service-linked role already exists

The template creates the AWSServiceRoleForEC2Spot and AWSServiceRoleForRedshift service-linked roles by default. If either role already exists in the account, stack creation fails. Delete the failed stack, deploy the template again, and set the Create service-linked roles (set to false if they already exist) parameter to false.

The stack cannot be created because IAM resources were not acknowledged

The template creates IAM resources with custom names, so AWS requires an explicit acknowledgement. On the create-stack page, select I acknowledge that AWS CloudFormation might create IAM resources with custom names, and then create the stack.

The stack status does not reach CREATE_COMPLETE after you click Execute in AWS

The stack might have been created in the wrong AWS account, or it might have failed in the AWS CloudFormation console. Verify that your browser session is logged in to the AWS account that is dedicated to the outpost. In the AWS CloudFormation console, review the stack events for the failure reason, resolve it, and deploy the template again.

The template cannot be loaded in the AWS CloudFormation console after Execute in AWS was clicked

The link that Execute in AWS opens is valid for a limited time. If the Quick create stack page was left open too long, or the link was used later, the template link might have expired. Return to the outpost creation wizard in Cortex XDR and click Execute in AWS again to open a new link.

A stack deployed from a downloaded CloudFormation template completes, but the outpost does not register with Cortex XDR

The downloaded CloudFormation template contains a registration link that expires 7 days after download. If the template was deployed after the link expired, the outpost cannot notify Cortex XDR. Delete the stack, download a new CloudFormation template from the outpost creation wizard, and deploy the new template.

Custom outpost troubleshooting

For issues with custom outposts, including custom networking (BYON), your own Azure app registration (BYOA), and Egress routing off, see Custom outpost troubleshooting.

Last updated

Was this helpful?