Troubleshoot AWS Onboarding Errors
Use this troubleshooting guide to find tips to identify, detect, and remediate any issues that may arise during or after the onboarding process.
Troubleshoot EventBridge Errors
In cases where you configured EventBridge successfully and created all the rules required for ingestion, however, the rules were accidentally deleted, or you enabled a region in your account that Prisma Cloud already supported,
Review Status
will display errors across the regions.To resolve this error you need to update the EventBridge CFT as follows:
- Click theView(
) icon next to the AWS account or organization you want to update.
- ClickMisconfigurations.
- ClickEditunderNear Real-Time Visibility.
- ClickDownload EventBridge CFTand follow the steps in your AWS console to renable the rules.
- Return to the Prisma Cloud console.
- Review Statusto ensure aSuccessfulmessage displays for each region.
- ClickSave.
- ClickStatuslocated next toMisconfigurationsand scroll down to theSecurity Capabilities and Permissionssection to verify the status ofAudit Logs.
Troubleshoot ExternalId Errors for a Standalone AWS Account
If you created the AWS IAM role using static S3 templates, onboarded the account on Prisma Cloud with a custom ExternalId, the following error may display under
Review Status
:
Make sure to
Save
the account before you follow the steps listed below to resolve the errors.Use any one of the following methods to resolve this error:
- Method 1If you are an AWS Cloud Administrator who does not have access to Prisma Cloud APIs, download and run the CFT template again:
- Click theEditicon for the onboarded AWS cloud account.
- ClickConfigure Account.
- Download IAM Role CFT.
- Follow theStepsto create new stack or update existing stack.
- Navigate toReview Statuspage to verify the status.
- ClickSave.
- Method 2If you are a Prisma Cloud Administrator who does not have AWS Administrator access, update the externalId used inCreate IAM Roleusing Update Cloud Account API.Example:{ curl --location --request PUT 'https://api3.prismacloud.io/cloud/aws/123456789012 \ --header 'Connection: keep-alive' \ --header 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \ --header 'x-redlock-auth: <token>' \ --header 'sec-ch-ua-mobile: ?0' \ --header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json, text/plain, */*' \ --data-raw '{ "accountId": "123456789012", "accountType": "account", "enabled": true, "externalId": "4fc24939-8fab-4978-a4e1-403095713870", "groupIds": [], "name": "AWS Account", "protectionMode": "MONITOR", "roleArn": "arn:aws:iam::123456789012:role/PrismaCloudReadOnlyRole" }' }Method 3If you are an AWS Cloud Administrator who does not have access to Prisma Cloud APIs, manually update the Prisma Cloud generated ExternalId in the existing IAM role trust relationship in your AWS console:
- Click theEditicon for the onboarded AWS cloud account.
- ClickConfigure Account.
- Download IAM Role CFT.
- Open the downloaded CFT in a text editor, search for sts:ExternalId andCopythe value.
- Copy the updatedExternalIdinTrust relationshipsof existing IAM role in AWS.
- Wait for 10-15 seconds for the changes to take effect.
- Review Statusto verify the cloud account status is green or amber.
- ClickSave.
Troubleshoot ExternalId Errors for an AWS Organization
- If you created the AWS IAM role using static s3 templates for Organization management account and member accounts via stackset using separate templates, onboarded the organization on Prisma Cloud with a custom ExternalId, the following error may display underReview Status:

- If the member accounts display an incorrect ExternalId or missing Trust relationship for Prisma Cloud in the provided Role:
- The ExternalId for member role names may be incorrect, or
- You used an old template while onboarding in Prisma Cloud, and the memberRoleName is not in the correct <masterRoleName>-member format.
Make sure to
Save
the account before you follow the steps listed below to resolve the errors.Use any one of the following methods to resolve this error:
- Method 1If you are an AWS Cloud Administrator who does not have access to Prisma Cloud APIs, download and run the CFT template again:
- Click theEditicon for the onboarded AWS organization.
- ClickConfigure Account.
- Download IAM Role CFT.
- Follow theStepsto create new stack or update existing stack.
- Navigate toReview Statuspage to verify the status.
- ClickSave.
- Method 2If you are a Prisma Cloud Administrator who does not have AWS Administrator access, update the externalId, memberExternalId, memberRoleName, and roleArn used inCreate IAM Roleusing Update Cloud Account API:
- externalId and roleArn - Management account IAM role
- memberExternalId and memberRoleName - Member accounts IAM role (created using stackset)Example:{ curl --location --request PUT 'https://api3.prismacloud.io/cloud/aws/123456789012' \ --header 'Connection: keep-alive' \ --header 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="97", "Chromium";v="97"' \ --header 'x-redlock-auth: <token>' \ --header 'sec-ch-ua-mobile: ?0' \ --header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json, text/plain, */*' \ --header 'Sec-Fetch-Site: same-site' \ --header 'Sec-Fetch-Mode: cors' \ --header 'Sec-Fetch-Dest: empty' \ --header 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \ --data-raw '{ "accountId": "123456789012'", "accountType": "organization", "enabled": true, "externalId": "a1ea8fe3-85d8-4ed9-93da-02d68670bc61", "memberExternalId": "a1ea8fe3-85d8-4ed9-93da-02d68670bc61", "memberRoleName": "PrismaCloudOrgMemberReadWriteRole", "memberRoleStatus": true, "name": "AWS ORG", "protectionMode": "MONITOR_AND_PROTECT", "roleArn": "arn:aws:iam::123456789012':role/PrismaCloudReadWriteRole" }' }
Method 3If you are an AWS Cloud Administrator who does not have access to Prisma Cloud APIs, manually update the Prisma Cloud generated ExternalId in the existing IAM role trust relationship in your AWS console:- Click theEditicon for the onboarded AWS organization.
- ClickConfigure Account.
- Download IAM Role CFT.
- Open the downloaded CFT in a text editor, search for sts:ExternalId. There will be one externalId for the Management role and another for member accounts roles. Locate the externalId inside the PrismaCloudRole mapping.
- Copy the updatedExternalIdinTrust relationshipsof existing Management account IAM role in AWS.
- Locate the memberExternalID in the downloaded template.
- Copy the updatedmemberExternalIdinTrust relationshipsof all existing member accounts IAM role in AWS.
- Wait for 10-15 seconds for the changes to take effect.
- Review Statusto verify the cloud account status is green or amber.
- ClickSave.
Most Popular
Recommended For You
Recommended Videos
Recommended videos not found.