Skip to main content
kmak
Staff
Staff
March 30, 2026

Troubleshooting Tip: Reason of difference in the FortiCNAPP AWS Agentless Workload Scanning task frequency and the related ECS task scheduled frequency

  • March 30, 2026
  • 0 replies
  • 53 views
Description This article describes the AWS Agentless Workload Scanning task in FortiCNAPP and the related ECS task scheduled frequency.
Scope Lacework FortiCNAPP.
Solution

As a reference, in the Lacework FortiCNAPP Agentless workload scanning integration on AWS environment: Integrating your AWS environment, the scan frequency is default configured as 24 hours.

 

AWS Cloud account Agentless integration in FortiCNAPP.

 

kmak_0-1774408891708.jpeg

 

The integration would deploy the ECS task in the AWS cloud account. The ECS task can be viewed in the AWS portal. The ECS scheduled tasks will be observed to have a scheduled rate of 1 hour.

 

kmak_1-1774408891714.jpeg


The ECS scheduled task does not reflect the FortiCNAPP Agentless configured scheduled scan task frequency. The ECS task runs on an hourly basis to check and initiate the Agentless Workload Scanning task. It is also performing cleanup operations to ensure there are no lingering resources left from a previous scan.

 

Check out the ECS task logs would be able to see if the workload scanning task was skipped or being executed. It would also show the scanning frequency in the log.

 

kmak_2-1774408891720.jpeg

 

Related document:

Agentless workload scanning FAQs