Prisma Public Cloud (formerly RedLock) setting warning

[LeeJuWon]

I am running Prisma Public Cloud with trial version.

I had configured Prisma Public Cloud and AWS.

I found status is orrange following as;

What is mean 3 warring messages and how could I fix it on AWS or Prisma Public Cloud.

Please help me....

[kchen]

Did you use Prisma Public Cloud's CloudFormation template to create the Prisma Public Cloud role?  If so, then it looks like the CloudFormation may be out of date.  Please manually add those permissions to the Prisma Public Cloud role's inline policy.  I'll run some tests too

[kchen]

This appears to be a bug.  Prisma Public Cloud is not correctly checking against Describe* permissions that are given within the role.  So even though the specific permission is covered, Prisma Public Cloud is still inaccurately reporting it as missing.  Engineering is looking into this already.

[lpingali · Accepted solution]

The Prisma Public Cloud role in the AWS console (IAM services) needs these specific permissions added in the inline policy. Prisma Public Cloud checks for these permissions for access and data ingestion.

You can log into AWS console-->IAM-->Role-->RedLock Role-->Permissions-->Check the Inline Policy JSON file.

Add the permissions mentioned in the Config status message, such as 

ssm:DescribeParameters, etc.

Once done, the warning message will disappear.