Skip to content

Commit 8f92ef1

Browse files
author
iru
authored
doc: add scanning troubleshooting
1 parent 609fb1a commit 8f92ef1

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,8 @@ If that's not working as expected, some other questions can be checked
216216

217217
**Image Scanning**
218218

219+
Image scanning is not activated by default. Ensure you have the [required scanning enablers](https://docs.sysdig.com/en/docs/installation/sysdig-secure-for-cloud/deploy-sysdig-secure-for-cloud-on-aws/#enabling-image-scanner) in place
220+
219221
- For ECR image scanning, upload any image to an ECR repository of AWS. Can find CLI instructions within the UI of AWS
220222
- For ECS running image scanning, deploy any task in your own cluster, or the one that we create to deploy our workload (ex.`amazon/amazon-ecs-sample` image).
221223

@@ -238,6 +240,13 @@ with the correct values. Check [Sysdig SaaS per-region URLs if required](https:/
238240
### Q-General: I'm not able to see Cloud Infrastructure Entitlements Management (CIEM) results
239241
A: Make sure you installed both [cloud-bench](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-bench) and [cloud-connector](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/modules/services/cloud-connector) modules
240242

243+
### Q-Scanning: I'm not seeing any image scanning results
244+
A: Need to check several steps
245+
<br/>S: First, image scanning is not activated by default. Ensure you have the [required scanning enablers](https://docs.sysdig.com/en/docs/installation/sysdig-secure-for-cloud/deploy-sysdig-secure-for-cloud-on-aws/#enabling-image-scanner) in place.
246+
<br/>Currently, images are scanned on registry/repository push events, and on the supported compute services on deployment. Make sure these events are triggered.
247+
<br/>Dig into secure for cloud compute log (cloud-connector) and check for errors.
248+
<br/>If previous logs are ok, check [spawned scanning service](http://localhost:1313/en/docs/sysdig-secure/sysdig-secure-for-cloud/#summary) logs
249+
241250

242251
### Q-AWS: Getting error "Error: failed creating ECS Task Definition: ClientException: No Fargate configuration exists for given values.
243252
A: Your ECS task_size values aren't valid for Fargate. Specifically, your mem_limit value is too big for the cpu_limit you specified

0 commit comments

Comments
 (0)