DSF MX

This Terraform module provisions a DSF Management server (AKA mx) on AWS as an EC2 instance.

Imperva’s Management Server is the manager for DAM components. This includes Agent Gateways and Agents.

Requirements

• Terraform, refer to versions.tf for supported versions.
• An AWS account.
• Network access to port 8083 (API and WebConsole)
• Access to DAM AMIs. To request access, subscribe to Imperva DAM AWS marketplace product.

NOTE: In case you are not yet an Imperva customer, please contact our team.

Resources Provisioned

This Terraform module provisions several resources on AWS to create the DSF MX. These resources include:

• An EC2 instance for running the software.
• An EBS volume for storage.
• AWS security groups to allow the required network access to and from the DSF instance.
• An IAM role with relevant policies.
• An AWS KMS.
• An AWS Elastic Network Interface (ENI).

The EC2 instance and EBS volume provide the computing and storage resources needed to run the DSF software. The security group controls the inbound and outbound traffic to the instance, while the IAM role grants the necessary permissions to access AWS resources. The KMS is used for encrypting sensitive data.

Inputs

The following input variables are required:

• subnet_id: The ID of the subnet in which to launch the DSF instance
• key_pair: AWS key pair name to attach to the instance
• mx_password: MX password
• secure_password: The password used for communication between the Management Server and the Agent Gateway
• dam_version: Version must be in the format dd.dd.dd.dd where each dd is a number between 1-99 (e.g 14.10.1.10)
• license: DAM license file path or activation key. Make sure this license is valid before deploying DAM otherwise this will result in an invalid deployment and loss of time

Refer to variables.tf for additional variables with default values and additional info.

Outputs

Refer to outputs or https://registry.terraform.io/modules/imperva/dsf-mx/aws/latest?tab=outputs

Usage

To use this module, add the following to your Terraform configuration:

provider "aws" {
}

module "mx" {
  source                       = "imperva/dsf-mx/aws"
  subnet_id                    = var.subnet
  key_pair                     = var.key_name
  mx_password                  = var.mx_password
  secure_password              = var.secure_password
  dam_version                  = var.dam_version
  license                      = var.license
  allowed_all_cidrs            = [data.aws_vpc.selected.cidr_block]
}

To see a complete example of how to use this module in a DSF deployment with other modules, check out the examples directory.

We recommend using a specific version of the module (and not the latest). See available released versions in the main repo README here.

Specify the module's version by adding the version parameter. For example:

module "dsf_mx" {
  source  = "imperva/dsf-mx/aws"
  version = "x.y.z"
}

API Access

API access is required to provision this module. Please make sure to pass the relevant CIDR block, representing your workstation, to allow such access through the allowed_web_console_and_api_cidrs variable.

Additional Information

For more information about the DSF MX and its features, refer to the official documentation here.

For additional information about DSF deployment using terraform, refer to the main repo README here.