Third Party App not able to call SQS

Question

Hello,
I'm using Prisma Cloud App service intergratino feature to send messages to an SQS I created in AWS. However, the app is not able to call the SQS que. I would like to confirm everything is right on AWS Side.

I have created a rule with the necessary permissions and actions to perform on the SQS que for the account to assume using the root principal. I'm wondering if there's some sort of access I must explicitly also allow on the SQS que?

Note this is cross account access. The third party app is in another account.The permissions on the SQS is default. The permissions for the assume role is listed below.

`{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "sqs:GetQueueAttributes",
                "sqs:ListQueues",
                "sqs:SendMessage",
                "tag:GetResources",
                "iam:GetRole",
                "kms:GenerateDataKey"
            ],
            "Resource": "arn:aws:sqs:us-east-1::prisma-que",
            "Effect": "Allow"
        }
    ]
}`

And the trust policy

`{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam:::root"
            },
            "Action": "sts:AssumeRole",
            "Condition": {
                "StringEquals": {
                    "sts:ExternalId": ""
                }
            }
        }
    ]
}`

Is there anything I'm missing?

Sachin · Answer

This is well documented in below link. it have Step by Step details how to configure in palo as well in AWS.

you can follow it

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-amazon-sqs

kentrad · Answer

You could change the trust policy to allow you to assume the role. Then use the `--dry-run` option of the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-help.html) to test if your permissions are correct.

Third Party App not able to call SQS

Relevant content