- | DAM | 14.16.1.10 | 14.11.1.10 and up
+ | DAM | 14.17.1.10 | 14.11.1.10 and up
14.7.x.y (LTS)
@@ -770,7 +779,7 @@ Make sure that the version you are using is supported by all the modules which a
To see which versions are supported by each module, refer to the specific module.
(For example, [DSF Hub module](https://registry.terraform.io/modules/imperva/dsf-hub/aws/latest))
-# Deployment
+# Deployment
After you have [chosen the deployment mode](#choosing-the-deployment-mode), follow the step-by-step instructions below to ensure a successful deployment. If you have any questions or issues during the deployment process, please contact [Imperva Technical Support](https://support.imperva.com/s/).
@@ -779,7 +788,7 @@ After you have [chosen the deployment mode](#choosing-the-deployment-mode), foll
This mode offers a straightforward deployment option that relies on running a Terraform script on the user's computer which must be a Linux/Unix machine, e.g, Mac.
This mode makes use of the Terraform Command Line Interface (CLI) to deploy and manage environments.
-1. Download the zip file of the example you've chosen (See the [Choosing the Example/Recipe that Fits Your Use Case](#choosing-the-examplerecipe-that-fits-your-use-case) section) from the eDSF Kit GitHub Repository, e.g., if you choose the "dsf_deployment" example, you should download dsf_deployment.zip.
+1. Download the zip file of the example you've chosen (See the [Choosing the Example/Recipe that Fits Your Use Case](#choosing-the-examplerecipe-that-fits-your-use-case) section) from the DSF Kit GitHub Repository, e.g., if you choose the "dsf_deployment" example, you should download dsf_deployment.zip.
2. Unzip the zip file in CLI or using your operating system's UI.
For example, in CLI:
@@ -858,7 +867,7 @@ This mode makes use of the Terraform Command Line Interface (CLI) to deploy and
## Installer Machine Deployment Mode
This mode is similar to the CLI mode except that the Terraform is run on an EC2 machine that the user launches, instead of on their computer.
-This mode can be used if a Linux/Unix machine is not available, or eDSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
+This mode can be used if a Linux/Unix machine is not available, or DSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
**NOTE:** The steps provided below are specific to deployment in an AWS environment. For deployment in an Azure environment, it is necessary to [create an Azure virtual machine instance based on Linux/Unix](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/quick-create-portal?tabs=ubuntu).
@@ -896,7 +905,7 @@ This mode can be used if a Linux/Unix machine is not available, or eDSF Kit cann
For example: `chmode 400 a_key_pair.pem`
-9. Download the zip file of the example you've chosen (See the [Choosing the Example/Recipe that Fits Your Use Case](#choosing-the-examplerecipe-that-fits-your-use-case) section) from the eDSF Kit GitHub Repository, e.g., if you choose the "dsf_deployment" example, you should download dsf_deployment.zip.
+9. Download the zip file of the example you've chosen (See the [Choosing the Example/Recipe that Fits Your Use Case](#choosing-the-examplerecipe-that-fits-your-use-case) section) from the DSF Kit GitHub Repository, e.g., if you choose the "dsf_deployment" example, you should download dsf_deployment.zip.
Run:
```bash
wget https://github.com/imperva/dsfkit/raw/1.7.20/examples/aws/installation/dsf_single_account_deployment/dsf_single_account_deployment_1_7_20.zip
@@ -970,10 +979,10 @@ If you want to use Imperva's Terraform Cloud account, contact Imperva's Technica
* To avoid automatic Terraform configuration changes when the GitHub repo updates, set the following values under “Run triggers”:
As displayed in the above screenshot, the Custom Regular Expression field value should be “23b82265”.
- * Click “Create workspace” to finish and save the new eDSF Kit workspace.
+ * Click “Create workspace” to finish and save the new DSF Kit workspace.
3. **Add the AWS variables:** The next few steps will configure the required AWS variables.
- * Once the eDSF Kit workspace is created, click the "Go to workspace overview" button.
+ * Once the DSF Kit workspace is created, click the "Go to workspace overview" button.
* Click on the "Configure Variables" button.
@@ -1031,7 +1040,7 @@ If you want to use Imperva's Terraform Cloud account, contact Imperva's Technica
**NOTE:** The workspace variables mentioned above are tailored for deployment in an AWS environment. For deployment in an Azure environment, it is necessary to include distinct workspace variables, and these will be addressed in a future release.
-4. **Run the Terraform:** The following steps complete setting up the eDSF Kit workspace and running the example's Terraform code.
+4. **Run the Terraform:** The following steps complete setting up the DSF Kit workspace and running the example's Terraform code.
* Click on the **Actions** dropdown button from the top navigation bar, and select the "Start new run" option from the list.
* Enter a unique, alphanumeric name for the run, and click on the "Start run" button.
@@ -1060,11 +1069,11 @@ If you want to use Imperva's Terraform Cloud account, contact Imperva's Technica
# IAM Permissions
-## IAM Permissions for Running eDSF Kit
+## IAM Permissions for Running DSF Kit
-### IAM Permissions for AWS
+### IAM Permissions for AWS
-To be able to create AWS resources inside any AWS Account, you need to provide an AWS User or Role with the required permissions in order to run eDSF Kit Terraform.
+To be able to create AWS resources inside any AWS Account, you need to provide an AWS User or Role with the required permissions in order to run DSF Kit Terraform.
The permissions are separated to different policies. Use the relevant policies according to your needs:
1. For general required permissions such as create an EC2, security group, etc., use the permissions specified here - [general required permissions](/permissions_samples/aws/GeneralRequiredPermissions.txt).
@@ -1076,7 +1085,7 @@ The permissions are separated to different policies. Use the relevant policies a
**NOTE:** The permissions specified in option 2 are irrelevant for customers who prefer to use their own network objects, such as VPC, NAT Gateway, Internet Gateway, etc.
### IAM Permissions for Azure
-To be able to create Azure resources inside any Azure Account, you need to provide an Azure user or application registration service principal with the required permissions in order to run eDSF Kit Terraform.
+To be able to create Azure resources inside any Azure Account, you need to provide an Azure user or application registration service principal with the required permissions in order to run DSF Kit Terraform.
Use the relevant permissions according to your needs:
1. For general required permissions such as create a virtual machine, security group, etc., use the permissions specified here - [general required permissions](/permissions_samples/azure/GeneralRequiredPermissions.txt).
@@ -1164,12 +1173,12 @@ In case of failure, the Terraform may have deployed some resources before failin
## Choosing the Upgrade Mode
-eDSF Kit offers several upgrade modes:
+DSF Kit offers several upgrade modes:
* **CLI Upgrade Mode:** This mode offers a straightforward upgrade option that relies on running a Terraform script on the user's computer which must be a Linux/Unix machine, e.g, Mac.
For more details, refer to [CLI Upgrade Mode](#cli-upgrade-mode).
-* **Installer Machine Deployment Mode:** This mode is similar to the CLI mode except that the Terraform is run on an EC2 machine that the user launches, instead of on their computer. This mode can be used if a Linux/Unix machine is not available, or eDSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
+* **Installer Machine Deployment Mode:** This mode is similar to the CLI mode except that the Terraform is run on an EC2 machine that the user launches, instead of on their computer. This mode can be used if a Linux/Unix machine is not available, or DSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
For more details, refer to [Installer Machine Upgrade Mode](#installer-machine-upgrade-mode).
@@ -1178,7 +1187,7 @@ If you need more information to decide on your preferred mode, refer to the deta
## Upgrade Prerequisites
-Before using eDSF Kit to upgrade DSF Hubs and Agentless Gateways, it is necessary to satisfy a set of prerequisites.
+Before using DSF Kit to upgrade DSF Hubs and Agentless Gateways, it is necessary to satisfy a set of prerequisites.
1. The upgrade requires access to the DSF installation software. [Click here to request access](https://github.com/imperva/dsfkit/blob/1.7.20/REQUEST_ACCESS_AWS.md).
2. Only if you chose the [CLI Upgrade Mode](#cli-upgrade-mode), install [Git](https://git-scm.com).
@@ -1189,7 +1198,7 @@ Before using eDSF Kit to upgrade DSF Hubs and Agentless Gateways, it is necessar
### Additional Prerequisites
-If the DSF deployment has not been deployed using the eDSF Kit, it is also necessary to satisfy the following prerequisites:
+If the DSF deployment has not been deployed using the DSF Kit, it is also necessary to satisfy the following prerequisites:
1. Grant the DSF Hubs and Agentless Gateways IAM roles access to the S3 bucket containing the DSF installation software, use the permissions specified here - [IAM Permissions for Granting Access to DSF Installation](/permissions_samples/aws/DSFIntallationAccessPermissions.txt).
@@ -1198,7 +1207,7 @@ If the DSF deployment has not been deployed using the eDSF Kit, it is also neces
## Upgrade Software Location and Versioning
-When using eDSF Kit, there is no need to manually download the DSF installation software, eDSF Kit will do that automatically based on the Sonar target version specified in the Terraform example.
+When using DSF Kit, there is no need to manually download the DSF installation software, DSF Kit will do that automatically based on the Sonar target version specified in the Terraform example.
In order to be able to download the upgrade software during upgrade, you must request access beforehand. See [Upgrade Prerequisites](#upgrade-prerequisites).
Sonar version constrains can be found in the Sonar Upgrader module.
@@ -1225,14 +1234,14 @@ This mode makes use of the Terraform Command Line Interface (CLI) to deploy and
```bash
unzip sonar_upgrade_.zip
- >>>> Replace the x_y_z with the eDSF Kit version in the zip file name
+ >>>> Replace the x_y_z with the DSF Kit version in the zip file name
```
3. In CLI, navigate to the directory which contains the Terraform files.
```bash
cd sonar_upgrade_
- >>>> Replace the x_y_z with the eDSF Kit version in the zip file name
+ >>>> Replace the x_y_z with the DSF Kit version in the zip file name
```
4. Enter the details of DSF Hubs and Agentless Gateways which you want to upgrade, and the desired configuraiton options, in the main.tf file.
@@ -1266,7 +1275,7 @@ This mode makes use of the Terraform Command Line Interface (CLI) to deploy and
## Installer Machine Upgrade Mode
This mode is similar to the CLI mode except that the Terraform is run on an EC2 machine that the user launches, instead of on their computer.
-This mode can be used if a Linux/Unix machine is not available, or eDSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
+This mode can be used if a Linux/Unix machine is not available, or DSF Kit cannot be run on the available Linux/Unix machine, e.g., since it does not have permission or network access to the deployment environment, or if the user doesn't want to install additional software on their computer.
1. In AWS, choose a region for the installer machine while keeping in mind that the machine should have access to the DSF environment that you want to upgrade, and preferably be in proximity to it.
diff --git a/REQUEST_ACCESS_AWS.md b/REQUEST_ACCESS_AWS.md
index 677425a3..d03363d8 100644
--- a/REQUEST_ACCESS_AWS.md
+++ b/REQUEST_ACCESS_AWS.md
@@ -12,16 +12,16 @@ Following your request, you are automatically granted access after a period of t
When deploying to multiple AWS accounts, use multiple forms.
-**Clarification**: After getting the requested access, you don’t have to “download” the software, just run eDSF Kit.
+**Clarification**: After getting the requested access, you don’t have to “download” the software, just run DSF Kit.
-1. [eDSF Kit - Request access to DSF installation software in S3 bucket](https://forms.gle/6DY6vgEgm91XAA7PA) (Google form)
+1. [DSF Kit - Request access to DSF installation software in S3 bucket](https://forms.office.com/r/MDaPUiqEES) (Microsoft form)
1. **Open only to Imperva employees**
2. Includes:
1. DSF Hub and Agentless Gateway (formerly Sonar)
2. DAM Agent audit source for POC purposes
3. Requesting access is for all versions and all regions
-2. [eDSF Kit - Request access to DAM AMI](https://aws.amazon.com/marketplace/pp/prodview-3wa5bmj5ol4g4) (In AWS Marketplace)
+2. [DSF Kit - Request access to DAM AMI](https://aws.amazon.com/marketplace/pp/prodview-3wa5bmj5ol4g4) (In AWS Marketplace)
1. Make sure you are logged in the AWS account
2. Open DAM marketplace link
3. Click “Continue to subscribe”
@@ -30,7 +30,7 @@ When deploying to multiple AWS accounts, use multiple forms.
**Note**: If you are already subscribed, you won’t see step (iv). You can manage your subscriptions [here](https://us-east-1.console.aws.amazon.com/marketplace/home#/subscriptions).
-3. [eDSF Kit - Request access to DRA AMI](https://forms.gle/4pinYVzGt39bU74d8) (Google form)
+3. [DSF Kit - Request access to DRA AMI](https://forms.office.com/r/s2CUijLRK8) (Microsoft form)
1. **Open only to Imperva employees**
2. Requesting access is for a specific version and specific regions
diff --git a/REQUEST_ACCESS_AZURE.md b/REQUEST_ACCESS_AZURE.md
index 38095bd9..e95cb492 100644
--- a/REQUEST_ACCESS_AZURE.md
+++ b/REQUEST_ACCESS_AZURE.md
@@ -10,16 +10,16 @@ The following links allow you to request access to the installation software of
Following your request, you are automatically granted access after a period of time specified in each link.
-**Clarification**: After the DSF installation files are copied, configure the relevant terraform variables and run eDSF Kit.
+**Clarification**: After the DSF installation files are copied, configure the relevant terraform variables and run DSF Kit.
-1. [eDSF Kit - Copy DSF installation to Azure storage account](https://docs.google.com/forms/d/e/1FAIpQLSfCBUGHN04u2gK8IoxuHl4TLooBWUl7cK7ihS9Q5ZHwafNBHA/viewform) (Google form)
+1. [DSF Kit - Copy DSF installation to Azure storage account](https://forms.office.com/r/xVgzA9d5nz) (Microsoft Form)
1. **Open only to Imperva employees**
2. Includes:
1. DSF Hub and Agentless Gateway (formerly Sonar)
2. DRA Admin and Analytics
3. DAM Agent audit source for POC purposes
-2. _eDSF Kit - Configure programmatic deployment for DAM image and DAM Agent operating system machine_ (In Azure Marketplace)
+2. _DSF Kit - Configure programmatic deployment for DAM image and DAM Agent operating system machine_ (In Azure Marketplace)
1. Make sure you are logged in the Azure account and the Azure subscription
2. Configure programmatic deployment for the desired version of Imperva DAM by enabling it on the relevant DAM image from the Azure Marketplace:
1. For DAM image - click [here](https://portal.azure.com/#view/Microsoft_Azure_Marketplace/LegalTermsSkuProgrammaticAccessBlade/legalTermsSkuProgrammaticAccessData~/%7B%22product%22%3A%7B%22publisherId%22%3A%22imperva%22%2C%22offerId%22%3A%22imperva-dam-v14%22%2C%22planId%22%3A%22securesphere-imperva-dam-14%22%2C%22standardContractAmendmentsRevisionId%22%3Anull%2C%22isCspEnabled%22%3Atrue%7D%7D)
diff --git a/examples/aws/installation/dsf_single_account_deployment/variables.tf b/examples/aws/installation/dsf_single_account_deployment/variables.tf
index 47192731..1bb78978 100644
--- a/examples/aws/installation/dsf_single_account_deployment/variables.tf
+++ b/examples/aws/installation/dsf_single_account_deployment/variables.tf
@@ -455,7 +455,7 @@ variable "sonar_machine_base_directory" {
variable "dam_version" {
type = string
description = "The DAM version to install"
- default = "14.16.1.10"
+ default = "14.17.1.10"
validation {
condition = can(regex("^(\\d{1,2}\\.){3}\\d{1,3}$", var.dam_version))
error_message = "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)"
diff --git a/examples/aws/poc/dsf_deployment/variables.tf b/examples/aws/poc/dsf_deployment/variables.tf
index 43130cbd..d78a59af 100644
--- a/examples/aws/poc/dsf_deployment/variables.tf
+++ b/examples/aws/poc/dsf_deployment/variables.tf
@@ -123,7 +123,7 @@ variable "subnet_ids" {
variable "dam_version" {
type = string
description = "The DAM version to install"
- default = "14.16.1.10"
+ default = "14.17.1.10"
validation {
condition = can(regex("^(\\d{1,2}\\.){3}\\d{1,3}$", var.dam_version))
error_message = "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)"
diff --git a/examples/azure/poc/dsf_deployment/variables.tf b/examples/azure/poc/dsf_deployment/variables.tf
index 91bcd4cd..9c94a573 100644
--- a/examples/azure/poc/dsf_deployment/variables.tf
+++ b/examples/azure/poc/dsf_deployment/variables.tf
@@ -118,7 +118,7 @@ variable "subnet_ids" {
variable "dam_version" {
type = string
description = "The DAM version to install"
- default = "14.16.1.10"
+ default = "14.17.1.10"
validation {
condition = can(regex("^(\\d{1,2}\\.){3}\\d{1,3}$", var.dam_version))
error_message = "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)"
|