Skip to content





The composition creates container instances in 6 different regions for a broader attack simulation. If you want to make a different setup, just alter modules in the

Create a new terraform.tfvars file in the folder, if you want to change the default configuration of the farm (db1000n can be configured with either command line parameters or environment variables, former having precedence over the latter):

  • bomblet_count=10 - can be used for custom number of containers per region
  • attack_commands=["/usr/src/app/db1000n","-c=https://link_to_your_config_file"]
  • attack_environment_variables={"ENABLE_PRIMITIVE":"false"}

terraform init - to restore all dependencies.

terraform apply -auto-approve - to provision the attack farm.

Collecting logs from the containers

The container instances are provisioned without public IP addresses to make the setup more cost effective. If you deploy more than one container per region, play with the -01 suffix to get logs from the correct instance.

  • Logs from North Europe region:
az container logs --resource-group main-rg --name main-northeurope-01 --container-name main
  • Logs from West Europe region:
az container logs --resource-group main-rg --name main-westeurope-01 --container-name main
  • Logs from Canada Central region:
az container logs --resource-group main-rg --name main-canadacentral-01 --container-name main
  • Logs from UAE North region:
az container logs --resource-group main-rg --name main-uaenorth-01 --container-name main
  • Logs from Central US region:
az container logs --resource-group main-rg --name main-centralus-01 --container-name main
  • Logs from East Asia region:
az container logs --resource-group main-rg --name main-eastasia-01 --container-name main


terraform destroy