Deployment, API & administration — found from sitemap — Defguard

Cited by

Facts read from this source

• Terraform deployment Report an error

  “To deploy Defguard using Terraform on AWS, you can use the Terraform configuration provided in the Defguard deployment repository.”

• Terraform modules Report an error

  “There are three Defguard modules available for deployment: core, proxy and gateway.”

• Module source Report an error

  “source = "github.com/DefGuard/deployment//terraform/modules/<MODULE>?ref=<REF>"”

• Default instance type Report an error

  “instance_type: The instance type to use. The default is t3.micro.”

• Recommended ami Report an error

  “We recommend using the Ubuntu Server 24.04 LTS (64-bit) AMI, which is the default in the example configurations.”

• Supported architectures Report an error

  “arch: The architecture of the Defguard Core package to be installed. This can be set to x86_64 or aarch64. The default is x86_64.”

• Package source Report an error

  “package_version: The version of the Defguard component package to be installed. This must be an existing Defguard debian package released on the Defguard releases page”

• Core database Report an error

  “name: The name of the PostgreSQL database to be created for Defguard.”

• Default vpn port Report an error

  “port: The port on which the VPN gateway will listen for incoming VPN connections. Default is 50051, which is the standard port for WireGuard VPN.”

• Gateway secret Report an error

  “gateway_secret: The secret used to authenticate the gateways with the core. This should be a random string of 64 characters.”

• Network rule edge public Report an error

  “Defguard Edge web UI should be publicly accessible, as it is used to securely pass messages to core from clients that are not connected to the VPN.”

• Network rule core internal Report an error

  “Defguard Core web UI should be accessible only from the internal network or through a secure VPN connection.”

• Network rule grpc internal Report an error

  “All gRPC traffic must stay internal.”

• Vpn networks gateway Report an error

  “vpn_networks: A list of VPN networks that should be created. For every network, a new gateway will be created.”

• Nat option Report an error

  “nat: Whether to enable NAT for the VPN network. This will add a masquerading rule to the gateway's host and enable IP forwarding.”

• Opentofu support Report an error

  “or if using OpenTofu:”

• Ami requirements Report an error

  “Must allow for running systemd services. Must use the APT package manager.”

• Example components Report an error

  “Defguard Core instance Defguard Edge instance Defguard Gateway instance A database instance (RDS) for Defguard Core. A single VPC for all components.”

• Systemd services Report an error

  “All components are deployed as systemd services on the host EC2. Their configuration files can be found at /etc/defguard.”

• Tfstate secrets Report an error

  “running the examples will put some sensitive details into your .tfstate file, most notably: the database password, gateway secret and the initial admin password.”

• Setup log path Report an error

  “The logs of this script are stored in /var/log/defguard.log on a corresponding EC2 instance.”

• Terraform status Report an error

  “We've recently introduced this deployment method and are still actively improving it.”

Scores citing this record

• The DevOps Engineer Access model & connectivity
• The DevOps Engineer Deployment, API & administration
• The IT Lead Access model & connectivity
• The IT Lead Deployment, API & administration
• The MSP Technician Deployment, API & administration
• The Operations Manager Deployment, API & administration
• The Information Security Officer Deployment, API & administration
• The Skeptic Deployment, API & administration