Why scanning is failing after setting up Agentless Scanning in Prisma Cloud?
3834
Created On 11/07/22 09:02 AM - Last Modified 09/26/24 18:24 PM
Question
Why scanning is failing after setting up Agentless Scanning in Prisma Cloud?
Environment
- Prisma Cloud - Enterprise Version with Console module enabled Version 22.06
- Prisma Cloud Compute - Self-Hosted Version 22.06
Answer
There could be a couple of reasons why Agentless might fail. Here are the following scenarios where we commonly see issues with agentless:
aws ec2 describe-images \ --region <Region> \ --image-ids ami-1234567890EXAMPLE2. AMI does not support ENA. -> This is not SUPPORTED for agentless scan.
3. Instance uses instance store, which is ephemeral storage -> Not SUPPORTED.
4. Instance type is not available in the region - Run the below command to verify
aws ec2 describe-instance-type-offerings --location-type availability-zone \ --filters Name=instance-type,Values=m5.2xlarge \ --region us-west-1 --output table aws ec2 describe-instance-type-offerings --location-type availability-zone \ --filters Name=instance-type,Values=m4.2xlarge \ --region us-west-1 --output table aws ec2 describe-instance-type-offerings --location-type availability-zone \ --filters Name=instance-type,Values=m3.2xlarge \ --region us-west-1 --output tableAdd and modify filters as needed.
Additional Information
Reference Documentation: