Views:

Before performing this task, the "SCAN_CONFIG" key of the Scanner Lambda function should exist. Follow these steps:

  1. Navigate to the AWS console and go to CloudFormation > Stacks > (find the scanner stack) > Resources > ScannerLambda.
  2. Click the link in "Physical ID" field to open the Lambda function page.
  3. In Scanner Lambda function page go to Configuration > Environment variables.
  4. Check if SCAN_CONFIG exists.

    Module state

To configure SCAN_CONFIG, follow these steps:

  1. In Scanner Lambda function page > Configuration > Environment variables > Edit.
  2. Edit the environment variable: SCAN_CONFIG value as:

    {"extractFileCountLimit": <the_file_count_limit> }

    As an example: {"extractFileCountLimit": 40 }

    Module state

  3. In Scanner Lambda function page go to Versions and click Publish new version button to publish a new version.
  4. In Scanner Lambda function page go to Aliases.
  5. Choose TM-FSS-MANAGED then click Edit.
  6. Click the Version dropdown and choose the version published in Step 3.
  7. Click Save.

    Module state

 
The scan time depends on file type, file size and the number of files in a ZIP or compressed file. There is a chance it may cause ScannerLambda to time out if too many files are in a ZIP/compressed file.
 

To increase the timeout configuration, follow these steps:

  1. In the Scanner Lambda Function page go to Configuration.
  2. Under General Configuration, you can edit the Timeout value.

    Module state

 
Do not attempt to edit and redeploy the File Storage Security Cloudformation template to apply the variable changes. Editing and redeploying the template may affect the File Storage Security subscription.