You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-9Lines changed: 15 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -145,20 +145,26 @@ Alternativelly, use Terraform example module to trigger **Create IAM Policy that
145
145
146
146
### Forcing Events - Image Scanning
147
147
148
-
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
148
+
:warning: Image scanning is not activated by default.
149
+
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.
150
+
151
+
When scanning is activated, should see following lines on the cloud-connector compute componente logs
- For ECR image scanning, upload any image to an ECR repository of AWS. Can find CLI instructions within the UI of AWS
151
158
- 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).
152
159
153
-
It may take some time, but you should see logs detecting the new image in the ECS cloud-connector task
0 commit comments