Agent Configuration

Manage AWS scanning agent deployments and settings.

The Agent Configuration page lets you manage the file scanning agents that DataDefender deploys into your AWS environments. These agents perform the actual content scanning of your storage resources to detect sensitive data patterns.


Deployments Grid

Each row in the grid represents a deployed scanning agent configuration for a specific AWS account and region.

Column
Description

Provider

Cloud Provider

Account ID

Cloud Account ID

Region

The region where agents are deployed

Errors

If the Agent has any current errors. Hover over message to see error messages

Status

Agent status (Active, Inactive)


Configuring a Deployment

Click the Configure button (settings icon) on any row to open the configuration dialog.

Field
Description

Min Agents

The minimum number of agents that should always be running

Max Agents

The ceiling for auto-scaling during high scan volumes

Queue Threshold

How many pending jobs must accumulate before scaling up. Will be automatically set to 1 if Smart Scanning is enabled.

CPU

CPU allocation per agent

Memory

Memory allocation per agent

Disk Size

Disk size per agent

Smart Scanning

When enabled, agents shut down when idle and only start when there is scanning work to do. This reduces AWS costs.

Click Save to apply changes or Cancel to discard them.


Enabling and Disabling a Deployment

Click the button with 3 dots then the toggle button on a deployment row to enable or disable it:

  • Disabling a deployment stops active scanning for all containers in that region. When disabled, Smart Scanning is automatically enabled so agents will still run if there is a backlog, but will not run continuously.

  • Enabling resumes normal active scanning.

You will be asked to confirm before the change is applied.


Deleting a Deployment

Click the Delete button (trash icon) on a row to remove a deployment entirely.

You will be asked to confirm the deletion. Note that deleting a deployment is permanent. Some resources may require manual cleanup in AWS after deletion. If so, a warning will appear listing the resources that need attention.


Last updated