Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/equinix/terraform-equinix-cloudguard
Terraform module for quick deployment of Check Point CloudGuard firewall device
https://github.com/equinix/terraform-equinix-cloudguard
checkpoint cloudguard equinix nfv sdn terraform terraform-module
Last synced: about 2 months ago
JSON representation
Terraform module for quick deployment of Check Point CloudGuard firewall device
- Host: GitHub
- URL: https://github.com/equinix/terraform-equinix-cloudguard
- Owner: equinix
- License: mit
- Created: 2021-03-26T09:50:53.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2023-12-15T08:54:43.000Z (about 1 year ago)
- Last Synced: 2024-05-09T14:25:09.548Z (8 months ago)
- Topics: checkpoint, cloudguard, equinix, nfv, sdn, terraform, terraform-module
- Language: HCL
- Homepage:
- Size: 12.7 KB
- Stars: 1
- Watchers: 9
- Forks: 4
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Equinix Network Edge: Check Point CloudGuard firewall device
A Terraform module to create Check Point CloudGuard firewall device
on the Equinix platform.![Terraform status](https://github.com/equinix/terraform-equinix-cloudguard/workflows/Terraform/badge.svg)
![License](https://img.shields.io/github/license/equinix/terraform-equinix-cloudguard)Supported device modes:
| Management Mode | License mode | Notes |
|-----------------|--------------|-------|
| Self managed | Bring your own license | - |## Requirements
| Name | Version |
|------|---------|
| terraform | >= 0.13.0 |
| equinix/equinix | >= 1.1.0 |## Providers
| Name | Version |
|---------|----------|
| equinix/equinix | >= 1.1.0 |## Assumptions
* if `account_number` is not provided, then `Active` account within given metro
will be used
* most recent, stable version of a device software for a given `software_package`
will be used
* secondary device name will be same as primary with `-secondary` suffix added
* secondary device notification list will be same as for primary## Example usage
```hcl
provider equinix {
client_id = var.equinix_client_id
client_secret = var.equinix_client_secret
}module "cloudguard" {
source = "equinix/cloudguard/equinix"
version = "1.0.0-beta"
metro_code = "SV"
platform = "small"
software_package = "STD"
name = "tf-tst-cloudguard"
hostname = "cg-pri"
term_length = 1
notifications = ["[email protected]"]
acl_template_id = "2e365e34-8f38-46e1-9f57-94b075d5dc09"
ssh_key = {
username = "john"
key_name = equinix_network_ssh_key.john.name
}
secondary = {
enabled = true
metro_code = "DC"
hostname = "cg-sec"
acl_template_id = "81a90c41-8a22-4724-997c-bdc07f401387"
}
}
```## Inputs
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|metro_code|Two-letter device location's metro code|`string`|`""`|yes|
|account_number|Billing account number for a device. If not provided, active account for a device metro code will be used|`string`|`0`|no|
|platform|Device hardware platform flavor: `small`, `medium`, `large`|`string`|`""`|yes|
|software_package|Device software package: `STD`|`string`|`""`|yes|
|name|Device name|`string`|`""`|yes|
|hostname|Device hostname prefix|`string`|`""`|yes
|term_length|Term length in months: `1`, `12`, `24`, `36`|`number`|`0`|yes|
|notifications|List of email addresses that will receive notifications about device|`list(string)`|n/a|yes|
|acl_template_id|Identifier of a network ACL template that will be applied on a device|`string`|`""`|no|
|additional_bandwidth|Amount of additional internet bandwidth for a device, in Mbps|`number`|`0`|no|
|ssh_key|Map of SSH public key attributes|`map`|N/A|yes|
|secondary|Map of secondary device attributes in redundant setup|`map`|N/A|no|SSH key map attributes:
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|username|Username associated with a given public key|`string`|`""`|yes|
|key_name|The name of the SSH public key|`string`|`""`|yes|Secondary device map attributes:
| Name | Description | Type | Default | Required |
|------|-------------|------|---------|----------|
|enabled|Value that determines if secondary device shall be created|`bool`|`false`|no|
|hostname|Device hostname|`string`|`""`|yes
|metro_code|Two-letter secondary device location's metro code|`string`|`""`|yes|
|account_number|Billing account number for a device. If not provided, active account for a device metro code will be used|`string`|`0`|no|
|acl_template_id|Identifier of a network ACL template that will be applied on a secondary device|`string`|`""`|no|
|additional_bandwidth|Amount of additional internet bandwidth for a secondary device, in Mbps|`number`|`0`|no|## Outputs
| Name | Description |
|------|-------------|
|id|Device identifier|
|status|Device provisioning status|
|license_status|Device license status|
|account_number|Device billing account number|
|cpu_count|Number of device CPU cores|
|memory|Amount of device memory|
|software_version|Device software version|
|region|Device region|
|ibx|Device IBX center code|
|ssh_ip_address|Device SSH interface IP address|
|ssh_ip_fqdn|Device SSH interface FQDN|
|interfaces|List of network interfaces present on a device|
|secondary|Secondary device outputs (same as for primary). Present when secondary device was enabled|