The Cato Terraform Example Usage project provides functional examples of how to use the cato terrafrom provider resources and modules for real-world deployment use cases.
Setup instructions for installing terraform on your host.
Install Terraform on Mac
- Option 1: Using Homebrew (Recommended)
brew tap hashicorp/tap brew install hashicorp/tap/terraform
- Option 2: Manual Install
- Go to the Terraform Downloads page.
- Download the macOS (arm64 or amd64) .zip file depending on your chip (M1/M2 = arm64).
- Unzip and move the binary to /usr/local/bin/:
sudo mv terraform /usr/local/bin/ chmod +x /usr/local/bin/terraform
Install Terraform on Windows
- Option 1: Using Chocolatey (Recommended)
choco install terraform -y
- Option 2: Manual Install
- Go to the Terraform Downloads page.
- Download the Windows (amd64) .zip file.
- Unzip it and place the terraform.exe file somewhere in your system’s PATH (e.g., C:\terraform).
- Open a new Command Prompt and run:
terraform -version
Terraform requires the respective cloud provider CLIs—AWS CLI, Azure CLI, and Google Cloud SDK (gcloud)—to be installed and properly configured on your local machine.
AWS CLI Installation Guide
- macOS: Python 3.8+ (check with
python3 --version). - Windows: Windows 10 or later (64-bit recommended).
- AWS account with Access Key ID and Secret Access Key (generate via AWS IAM).
- Install via Homebrew (recommended):
brew install awscli
- Alternatively, use the bundled installer:
curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg" sudo installer -pkg AWSCLIV2.pkg -target /
- Verify installation:
aws --version
- Download the MSI installer from AWS CLI v2.
- Run the installer:
msiexec.exe /i AWSCLIV2.msi
- For silent installation:
msiexec.exe /i AWSCLIV2.msi /qn
- For silent installation:
- Verify installation:
aws --version
- Run the configuration command:
aws configure
- Enter the following when prompted:
- AWS Access Key ID
- AWS Secret Access Key
- Default region (e.g.,
us-east-1) - Output format (e.g.,
json)
- Verify configuration:
aws sts get-caller-identity
References: AWS CLI Installation Guide
- AWS CLI: If
aws --versionfails, check PATH or reinstall. See AWS CLI Troubleshooting.
- AWS CLI:
brew upgrade awscli # macOS winget upgrade --id Amazon.AWSCLI # Windows
Azure CLI Installation Guide
### Prerequisites - **macOS**: Homebrew installed (`/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"`). - **Windows**: PowerShell 5.1+ or Windows 10/11. - Azure account with active subscription.- Install via Homebrew:
brew install azure-cli
- Verify installation:
az version
- Install via WinGet (recommended):
winget install --exact --id Microsoft.AzureCLI
- Alternatively, download the MSI installer from Azure CLI Releases.
- Run the MSI installer and follow prompts.
- Verify installation:
az version
- Log in to Azure:
az login
- Follow the browser prompt to authenticate.
- Verify subscription access:
az account show
- (Optional) Set default subscription:
az account set --subscription <subscription-id>
References: Azure CLI Installation Guide
- Azure CLI: Restart terminal after installation. For proxy issues, configure
HTTP_PROXY/HTTPS_PROXYvariables.
- Azure CLI:
brew upgrade azure-cli # macOS winget upgrade --id Microsoft.AzureCLI # Windows
GCP CLI (gcloud) Installation Guide
### Prerequisites - **macOS**: Python 3.8–3.13 (check with `python3 -V`). - **Windows**: Windows 8.1+ with PowerShell. - Google Cloud account with a project.- Download the archive for your architecture (e.g., x86_64 or ARM64):
curl -O https://dl.google.com/dl/cloudsdk/channels/rapid/downloads/google-cloud-cli-<version>-darwin-<arch>.tar.gz
- Extract and install:
tar -xvf google-cloud-cli-<version>-darwin-<arch>.tar.gz ./google-cloud-sdk/install.sh
- Initialize the CLI:
./google-cloud-sdk/bin/gcloud init
- Verify installation:
gcloud --version
- Download the installer from Google Cloud CLI.
- Run the installer and follow prompts.
- Alternatively, use PowerShell:
(New-Object Net.WebClient).DownloadFile("https://dl.google.com/dl/cloudsdk/channels/rapid/GoogleCloudSDKInstaller.exe", "$env:Temp\GoogleCloudSDKInstaller.exe") & $env:Temp\GoogleCloudSDKInstaller.exe
- Alternatively, use PowerShell:
- Initialize the CLI:
gcloud init
- Verify installation:
gcloud --version
- During
gcloud init, follow prompts to:- Log in via browser.
- Select a project.
- Set a default region/zone (optional).
- Verify configuration:
gcloud config list
References: Google Cloud CLI Installation Guide
- gcloud CLI:
gcloud components update
Create system environment variables for the cato token and account id. Using the TF_VAR prefix when creating environment variables tells terraform to resolve those values from the host OS as opposed to in your local variables files.
WARNING: DO NOT add your cato token in clear text to any variable files on your local system.
Setting environment variables in Unix
Use the following syntax in a unix command prompt to temporarily set environment variables.set TF_VAR_account_id=xxxxx
set TF_VAR_cato_token=xxxxxTo make these values persistent, run either vi ~/.bash_profile or vi ~/.zshrc, and add the following lines.
set TF_VAR_account_id=xxxxx
set TF_VAR_cato_token=xxxxxSetting environment variables in Windows
Use the following syntax in a windows command prompt to temporarily set environment variables. ```bash set TF_VAR_account_id=xxxxx set TF_VAR_cato_token=xxxxx ``` To make these values persistent, run the following windows command prompt: ```bash setx TF_VAR_account_id=xxxxx setx TF_VAR_cato_token=xxxxx ``` NOTE: On a local system, variables created or modified by this tool will be available in future command windows but not in the current CMD.exe command window.Setting environment variables in Windows Powershell
Use the following syntax in a powershell command prompt to temporarily set environment variables. ```bash $env:TF_VAR_account_id = "xxxxx" $env:TF_VAR_cato_token = "xxxxx" ``` To make these values persistent, run the following in a powershell terminal as Admin (UserLevel): ```bash [System.Environment]::SetEnvironmentVariable('TF_VAR_account_id','xxxxxxx', 'User') [System.Environment]::SetEnvironmentVariable('TF_VAR_cato_token','xxxxxxx', 'User') ```Avaialble Cato modules and default networks
Below is a list of the terraform modules included in this package, and the associated default networks for those modules to be used as an example. Each module exposes variables to override these networks and module settings as needed on a per module basis.
| Cato Module | Network | Module Deployment Time | Test Environment Deployment Time |
|---|---|---|---|
| aws-ipsec | 10.0.0.0/16 | 40 min | |
| aws-socket | 10.1.0.0/16 | 5 min | |
| aws-socket-vpc | 10.2.0.0/16 | 5 min | N/A |
| aws-socket-ha | 10.3.0.0/16 | 16 min | N/A |
| aws-socket-ha-vpc | 10.4.0.0/16 | 16 min | N/A |
| aws-socket-tgw | 10.5.0.0/16 | 5 min | 13 min |
| aws-socket-tgw-ha | 10.6.0.0/16 | 16 min | 25 min |
| aws-ipsec-tgw | 10.7.0.0/16 | 10 min | 20 min |
| azure-ipsec | 10.50.0.0/16 | 40 min | N/A |
| azure-socket | 10.51.0.0/16 | 6 min | N/A |
| azure-socket-vnet | 10.52.0.0/16 | 6 min | N/A |
| azure-socket-ha | 10.53.0.0/16 | 16 min | N/A |
| azure-socket-ha-vnet | 10.54.0.0/16 | 16 min | N/A |
| azure-vwan | 10.55.0.0/16 | 120 min | N/A |
| azure-socket-ha-vnet-2nic | 10.56.0.0/16 | 25 min | N/A |
| azure-vwan-vsocket-ha | 10.57.0.0/16 | 120 min | N/A |
| gcp-ipsec | 10.100.0.0/16 | n/a | N/A |
| gcp-socket | 10.101.0.0/16 | 5 min | N/A |
| gcp-socket-vpc | 10.102.0.0/16 | n/a | N/A |
| socket | 10.150.0.0/16 | 1 min | N/A |
After checking out the project, rename the following files removing .example from from the file names to start to use in your deployment. Renaming these files ensures you can start to use this project, and received updaetes to the repo without future code conflicts. There is a main file created for each cloud environment (AWS, GCP, Azure), as well as a main file for a physical socket. Rename the main for the deployment you are looking to run.
git clone https://github.com/catonetworks/terraform-example-usage.git
cd terraform-example-usage
mv terraform.tfvars.example terraform.tfvars
mv main.azure.tf.example main.azure.tf
mv main.aws.tf.example main.aws.tf
mv main.gcp.tf.example main.gcp.tf
mv main.socket.tf.example main.socket.tfPull in future updates to this repository by using git pull.
The terraform.tvars file contains variable values using a set of boolean flags to selectively enable or disable the deployment of specific Terraform modules across physical socket examples as well as, AWS, Azure, and GCP.
Run terraform apply to create and deploy your modules.
NOTE Cato’s backend is API requires sequential execution with the use of terraform's parallelism=1 to successfully create and update resources (like creating vsockets, firewall rules, and network ranges).
terraform init
terraform plan
terraform apply --auto-approve -parallelism=1
terraform destroy --auto-approve terraform init
terraform plan
terraform apply --auto-approve -parallelism=1 -target=module.ipsec-aws
terraform destroy -target=module.ipsec-awsUse the following bash or zsh aliases to simplify running these commands. Run either vi ~/.bashrc or vi ~/.zshrc, and add the following lines.
alias tf='terraform'
alias tfi='terraform init'
alias tfp='terraform plan'
alias tfap='terraform apply --auto-approve'
alias tfapp='terraform apply --auto-approve -parallelism=1'
alias tfdap='terraform destroy --auto-approve'
alias tfdapp='terraform destroy --auto-approve -parallelism=1'
alias tfclear='rm -rf .terraform* && rm terraform.tfstate*'
alias tffmt="tf fmt -recursive"📦 AWS Transit Gateway Test Environment
This repo comes with a test enviroment for testing connectivity and displaying how Cato vSockets can be deployed within a cloud provider. By setting build_aws_vsocket_tgw_test_env = true in the terraform.tfvars file, the test environment for AWS Transit Gateway (Non-HA) will be built automaticallyThis environment will build 3 VPCs, and associated subnets, route tables, routes, transit gateway, attachments, and transit gateway route tables and routes. This will also build 6 servers, which can be connected to via SSM.
| Resource | IP Address | Access Method | Egress Via | Type |
|---|---|---|---|---|
| test-env-vpc1-server-0 | 10.5.1.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-server-1 | 10.5.1.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-wserver-0 | 10.5.1.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc1-wserver-1 | 10.5.1.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-server-0 | 10.5.2.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-server-1 | 10.5.2.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-wserver-0 | 10.5.2.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-wserver-1 | 10.5.2.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc3-server-0 | 10.5.5.6 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc3-server-1 | 10.5.5.136 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc3-wserver-0 | 10.5.5.7 | Connect Via SSM or RDP | Public IP and Subnets | Windows 2019 Server |
| test-env-vpc3-wserver-1 | 10.5.5.135 | Connect Via SSM or RDP | Public IP and Subnets | Windows 2019 Server |
| AWS-Cato-vSocket-TGW-Site-vSocket-LAN | 10.5.0.134 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-Site-vSocket-WAN | 10.5.0.70 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-Site-vSocket-MGMT | 10.5.0.6 | Connect via CMA | Public IP and Subnets | Cato Socket |
📦 AWS Transit Gateway HA Test Environment
This repo comes with a test enviroment for testing connectivity and displaying how Cato vSockets can be deployed within a cloud provider. By setting build_aws_vsocket_tgw_test_env = true in the terraform.tfvars file, the test environment for AWS Transit Gateway (HA) will be built automaticallyThis environment will build 3 VPCs, and associated subnets, route tables, routes, transit gateway, attachments, and transit gateway route tables and routes. This will also build 6 servers, which can be connected to via SSM.
| Resource | IP Address | Access Method | Egress Via | Type |
|---|---|---|---|---|
| test-env-vpc1-server-0 | 10.6.1.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-server-1 | 10.6.1.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-wserver-0 | 10.6.1.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc1-wserver-1 | 10.6.1.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-server-0 | 10.6.2.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-server-1 | 10.6.2.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-wserver-0 | 10.6.2.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-wserver-1 | 10.6.2.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc3-server-0 | 10.6.4.6 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc3-server-1 | 10.6.4.136 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc1-wserver-0 | 10.6.5.7 | Connect Via SSM | Public IP and Subnets | Windows 2019 Server |
| test-env-vpc1-wserver-1 | 10.6.5.135 | Connect Via SSM | Public IP and Subnets | Windows 2019 Server |
| AWS-Cato-vSocket-TGW-HA-Site-LAN-INT-Primary | 10.6.0.70 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-HA-Site-LAN-INT-Secondary | 10.6.0.86 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-HA-Site-MGMT-INT-Primary | 10.6.0.6 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-HA-Site-MGMT-INT-Secondary | 10.6.0.22 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-HA-Site-WAN-INT-Primary | 10.6.0.38 | Connect via CMA | Public IP and Subnets | Cato Socket |
| AWS-Cato-vSocket-TGW-HA-Site-WAN-INT-Secondary | 10.6.0.54 | Connect via CMA | Public IP and Subnets | Cato Socket |
📦 AWS Transit Gateway IPSEC Test Environment
This repo comes with a test enviroment for testing connectivity and displaying how Cato IPSEC can be deployed within a cloud provider. By setting build_aws_ipsec_tgw_test_env = true in the terraform.tfvars file, the test environment for AWS Transit Gateway IPSEC will be built automaticallyThis environment will build 3 VPCs, and associated subnets, route tables, routes, transit gateway, attachments, and transit gateway route tables and routes. This will also build 6 servers, which can be connected to via SSM.
| Resource | IP Address | Access Method | Egress Via | Type |
|---|---|---|---|---|
| test-env-vpc1-server-0 | 10.7.1.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-server-1 | 10.7.1.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc1-wserver-0 | 10.7.1.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc1-wserver-1 | 10.7.1.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-server-0 | 10.7.2.6 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-server-1 | 10.7.2.134 | Connect Via SSM | Cato Socket | AL2023 Unix Server |
| test-env-vpc2-wserver-0 | 10.7.2.7 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc2-wserver-1 | 10.7.2.135 | Connect Via SSM or RDP | Cato Socket | Windows 2019 Server |
| test-env-vpc3-server-0 | 10.7.4.6 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc3-server-1 | 10.7.4.136 | Connect Via SSM | Public IP and Subnets | AL2023 Unix Server |
| test-env-vpc1-wserver-0 | 10.7.5.7 | Connect Via SSM | Public IP and Subnets | Windows 2019 Server |
| test-env-vpc1-wserver-1 | 10.7.5.135 | Connect Via SSM | Public IP and Subnets | Windows 2019 Server |
📦 Enabling the Kali Server Module
The Kali Server Module allows you to deploy Kali Linux penetration testing instances as part of your AWS Transit Gateway test environments. This module is available for security testing and network analysis purposes.
To enable Kali servers in your deployment, you need to set the following variable(s) in your terraform.tfvars file:
Required Variable:
enable_kali = true- Set this totrueto enable the deployment of Kali Linux instances
Optional Variable:
kali_ami_id = "ami-xxxxxxxxx"- Specify a custom Kali Linux AMI ID (if not provided, the module will automatically find the most recent Kali Linux AMI from Offensive Security)
Example Configuration:
# Enable Kali servers
enable_kali = true
# Optional: Specify a custom AMI ID
# kali_ami_id = "ami-0395cfad13fba5338" # Example for us-west-2Supported Environments/Modules: The Kali server module is supported in the following AWS Transit Gateway test environments:
- AWS Transit Gateway Test Environment (
build_aws_vsocket_tgw_test_env = true) - AWS Transit Gateway HA Test Environment (
build_aws_vsocket_tgw_ha_test_env = true)
Instance Details:
- Instance Type: t3.medium (optimized for Kali Linux performance)
- Deployment Location: VPC3 public subnets with public IP addresses
- Naming Convention:
test-env-vpc-3-kaliServer-{index} - IP Assignment: Static private IPs (typically .8 in each subnet)
- Storage: 150GB GP3 EBS volume
Access Methods:
-
SSH Access: Use your configured EC2 key pair to SSH into the instances
ssh -i your-key.pem kali@<private-ip> (If Connected to the network which houses the Kali Server) ssh -i your-key.pem kali@<public-ip> (If accessing over the internet)
-
AWS Systems Manager (SSM): Connect via AWS SSM Session Manager
aws ssm start-session --target <instance-id>
-
Remote Desktop (XRDP): The instances are configured with XRDP for GUI access
- Connect using any RDP client to
<public-ip>:3389 - Use the
kaliuser credentials
- Connect using any RDP client to
Pre-installed Tools: The Kali instances come with:
- Kali Linux default toolset (
kali-linux-default) - Desktop environment (GNOME)
- Headless tools (
kali-linux-headless) - AWS CLI and SSM Agent
- Development tools (git, vim, python3-pip)
- Network utilities
Password Change Required
- You must ssh in to the server using the above instructions prior to using RDP
- Once Connected with SSH you will need to change the password for the Kali User (
sudo passwd kali) - Once the Password is changed you should be able to leverage an RDP client to connect to this server
Boot Time
- Due to the number of updates, and installs on boot you must wait a minimum of 30 minutes for this server to be ready
- You can check the status by viewing the cloud-init logs located in
/var/log/cloud-init*
AMI ID
- Custom AMI IDs can be passed to the module using
kali_ami_idin the case that you can't use the Marketplace version of Kali in your environment
| Name | Version |
|---|---|
| aws | ~> 5.98.0 |
| azurerm | >= 4.1.0 |
| cato | >= 0.0.30 |
| ~> 4.0 |
No providers.
| Name | Source | Version |
|---|---|---|
| azure-vsocket-vwan-ha | ./modules/cato/azure/vsocket-vwan | n/a |
| build_aws_ipsec_tgw_module | ./modules/cato/aws/ipsec-tgw | n/a |
| build_aws_vsocket_tgw_ha_module | ./modules/cato/aws/vsocket-tgw-ha | n/a |
| ipsec-aws | ./modules/cato/aws/ipsec | n/a |
| ipsec-azure | ./modules/cato/azure/ipsec | n/a |
| vsocket-aws | ./modules/cato/aws/vsocket | n/a |
| vsocket-aws-ha | ./modules/cato/aws/vsocket-ha | n/a |
| vsocket-aws-ha-vpc | ./modules/cato/aws/vsocket-ha-vpc | n/a |
| vsocket-aws-tgw | ./modules/cato/aws/vsocket-tgw | n/a |
| vsocket-aws-vpc | ./modules/cato/aws/vsocket-vpc | n/a |
| vsocket-azure | ./modules/cato/azure/vsocket | n/a |
| vsocket-azure-ha | ./modules/cato/azure/vsocket-ha | n/a |
| vsocket-azure-ha-vnet | ./modules/cato/azure/vsocket-ha-vnet | n/a |
| vsocket-azure-ha-vnet-2nic | ./modules/cato/azure/vsocket-ha-vnet-2nic | n/a |
| vsocket-azure-vnet | ./modules/cato/azure/vsocket-vnet | n/a |
No resources.
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| account_id | Cato Networks Account ID | string |
n/a | yes |
| aws_default_keypair | AWS Key Pair | string |
n/a | yes |
| aws_region | AWS Region | string |
n/a | yes |
| azure_subscription_id | Azure Subscription ID | string |
n/a | yes |
| baseurl | Cato Networks API URL | string |
"https://api.catonetworks.com/api/v1/graphql2" |
no |
| build_aws_ipsec_module | Build AWS IPsec site module | bool |
false |
no |
| build_aws_ipsec_tgw_module | Build AWS IPsec tgw site module | bool |
false |
no |
| build_aws_ipsec_tgw_test_env | Build AWS IPsec tgw test env module | bool |
false |
no |
| build_aws_vsocket_ha_module | Build AWS vSocket VPC site module | bool |
false |
no |
| build_aws_vsocket_ha_vpc_module | Build AWS vSocket VPC site module | bool |
false |
no |
| build_aws_vsocket_module | Build AWS vSocket site module | bool |
false |
no |
| build_aws_vsocket_tgw_ha_module | Build AWS vSocket tgw ha site module | bool |
false |
no |
| build_aws_vsocket_tgw_ha_test_env | Build AWS vSocket tgw ha test env module | bool |
false |
no |
| build_aws_vsocket_tgw_module | Build AWS vSocket tgw site module | bool |
false |
no |
| build_aws_vsocket_tgw_test_env | Build AWS vSocket tgw test env module | bool |
false |
no |
| build_aws_vsocket_vpc_module | Build AWS vSocket VPC site module | bool |
false |
no |
| build_azure_ipsec_module | Build Azure IPsec site module | bool |
false |
no |
| build_azure_vsocket_ha_module | Build Azure vSocket VPC site module | bool |
false |
no |
| build_azure_vsocket_ha_vnet_2nic_module | Build Azure vSocket Net 2NIC site Module | bool |
false |
no |
| build_azure_vsocket_ha_vnet_module | Build Azure vSocket VNET site module | bool |
false |
no |
| build_azure_vsocket_ha_vwan_module | Build Azure vSocket vWAN site module | bool |
false |
no |
| build_azure_vsocket_module | Build Azure vSocket site module | bool |
false |
no |
| build_azure_vsocket_vnet_module | Build Azure vSocket VNET site module | bool |
false |
no |
| build_azure_vwan_module | Build Azure vWAN Site Module | bool |
false |
no |
| build_bulk_socket_csv_module | Build Bulk Socket site from csv module | bool |
false |
no |
| build_gcp_ipsec_module | Build GCP IPsec site module | bool |
false |
no |
| build_gcp_vsocket_module | Build GCP vSocket site module | bool |
false |
no |
| build_gcp_vsocket_vpc_module | Build GCP vSocket VPC site module | bool |
false |
no |
| build_socket_csv_module | Build Socket site from csv module | bool |
false |
no |
| cato_token | Cato Networks API Token | string |
n/a | yes |
| gcp_region | GCP Region for the deployment | string |
n/a | yes |
| project | GCP Project ID for the deployment | string |
n/a | yes |
| zone | GCP Zone for the deployment | string |
n/a | yes |
| Name | Description |
|---|---|
| private_ips_from_ipsec_tgw_test_env | private IPs of servers in the test environment |
| private_ips_from_tgw_ha_test_env | private IPs of servers in the test environment |
| private_ips_from_tgw_test_env | private IPs of servers in the test environment |
| vpc3_public_ips_from_ipsec_tgw_test_env | Public IPs of Public VPC servers in the test environment |
| vpc3_public_ips_from_tgw_ha_test_env | Public IPs of Public VPC servers in the test environment |
| vpc3_public_ips_from_tgw_test_env | Public IPs of Public VPC servers in the test environment |