# Deployment strategies

- [Overview](https://docs.defguard.net/1.6/deployment-strategies/setting-up-your-instance.md): This documentation will guide you through the process of deploying your Defguard instance.
- [Deploying to Production](https://docs.defguard.net/1.6/deployment-strategies/deploying-to-production.md)
- [Hardware, OS, network and firewall recommendations](https://docs.defguard.net/1.6/deployment-strategies/hardware-os-network-and-firewall-recommendations.md): Before Defguard can be deployed please get familiar with the following recommendations
- [Standalone package based installation](https://docs.defguard.net/1.6/deployment-strategies/standalone-package-based-installation.md)
- [Defguard APT repository](https://docs.defguard.net/1.6/deployment-strategies/standalone-package-based-installation/defguard-apt-repository.md)
- [Docker Compose](https://docs.defguard.net/1.6/deployment-strategies/docker-compose.md)
- [Kubernetes](https://docs.defguard.net/1.6/deployment-strategies/kubernetes.md)
- [Terraform](https://docs.defguard.net/1.6/deployment-strategies/terraform.md)
- [Amazon Machine Image (AMI)](https://docs.defguard.net/1.6/deployment-strategies/amis-and-aws-cloudformation.md)
- [Configuring HTTPS using AWS Certificate Manager](https://docs.defguard.net/1.6/deployment-strategies/amis-and-aws-cloudformation/configuring-https-using-aws-certificate-manager.md)
- [Adding a location and getting a Gateway token](https://docs.defguard.net/1.6/deployment-strategies/gateway.md): This documentation will guide you through adding a new location and proceeding with the Gateway deployment, enabling your devices to connect to it via VPN.
- [Configuration](https://docs.defguard.net/1.6/deployment-strategies/configuration.md)
- [Running Gateway on OPNsense firewall](https://docs.defguard.net/1.6/deployment-strategies/running-gateway-on-opnsense-firewall.md)
- [Running Gateway on MikroTik routers](https://docs.defguard.net/1.6/deployment-strategies/running-gateway-on-mikrotik-routers.md)
- [Reverse Proxy configuration using NGINX](https://docs.defguard.net/1.6/deployment-strategies/reverse-proxy-configuration-using-nginx.md)
- [High Availability and Failover](https://docs.defguard.net/1.6/deployment-strategies/high-availability-and-failover.md)
- [Updating and version compatibility](https://docs.defguard.net/1.6/deployment-strategies/updating-and-version-compatibility.md)
- [Migration guides](https://docs.defguard.net/1.6/deployment-strategies/upgrading.md): Notes on upgrading Defguard and its components
- [Using a userspace wireguard-go implementation](https://docs.defguard.net/1.6/deployment-strategies/using-a-userspace-wireguard-go-implementation.md)
- [Pre-production and development releases](https://docs.defguard.net/1.6/deployment-strategies/pre-production-and-development-releases.md)
- [Securing gRPC communication](https://docs.defguard.net/1.6/deployment-strategies/grpc-ssl-communication.md)
- [Using RSA instead of HMAC for OpenID key](https://docs.defguard.net/1.6/deployment-strategies/openid-rsa-key.md)
- [Health check](https://docs.defguard.net/1.6/deployment-strategies/health-check.md)
- [Production deployment verification guide](https://docs.defguard.net/1.6/deployment-strategies/production-deployment-verification-guide.md)
- [Linux Kernel WireGuard tuning](https://docs.defguard.net/1.6/deployment-strategies/linux-kernel-wireguard-tuning.md): This technical guide addresses requirements regarding WireGuard VPN latency, throughput, resilience, and scalability by tuning Linux Kernel parameters (as WireGuard is part of Linux Kernel).
- [Deployment automation](https://docs.defguard.net/1.6/deployment-strategies/deployment-automation.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.defguard.net/1.6/deployment-strategies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.