Skip to content
The Things Stack documentation home
Getting Started Concepts Cloud Enterprise Integrations API Hardware
Getting Started Concepts
Cloud Enterprise
Integrations API Hardware
Get The Things Stack

    Recent searches

      Popular pages

      • Getting Started
      • Adding Gateways
      • Adding Devices
      • Payload Formatters
      • Webhooks
      • Authentication

      No results for “”.

      • Check the spelling, or try fewer or more general words.
      • Ask the community on The Things Network Forum
      • Contact support
      ↑↓ to navigate ↵ to open Esc to close

      The Things Stack Enterprise

      • Overview
      • AWS
      • Kubernetes
        • Generic
        • Azure
          • Architecture
          • Prerequisites
          • Configuration
          • Deployment
          • Upgrading
          • Troubleshooting
      • Docker
      • The Things Join Server
      • Manage The Things Stack

      Prerequisites

      Updated 20 January 2025 Edit on GitHub
      Copy page
      • View as MarkdownThis page as plain text
      • Open in ChatGPTAsk questions about this page
      • Open in ClaudeAsk questions about this page

      This section contains prerequisites for deploying The Things Stack on Azure Kubernetes Service.

      Tools

      1. Terraform
      2. kubectl
      3. Helm version 3. Check the version of Helm installed using helm version. Helm v3.8 or above is required.

      License

      The Things Stack requires a license key to run. Please contact our sales team for your license key.

      (Optional) Packet Broker Access

      The Things Stack contains the Packet Broker Agent component that can communicate with Packet Broker.

      Packet Broker is disabled by default in the Helm charts. When enabled, it can operate either only a Forwarder or as both a Forwarder and a Home Network. Check the Packet Broker section for more details.

      • If the cluster acts simply as a Forwarder that forwards traffic to Packet Broker, then all that is needed are access credentials.
      • If the cluster also needs to work as a Packer Broker Home Network, in addition to the access credentials, the cluster either needs a NetID from the LoRa Alliance or The Things Industries can lease a DevAddr Block.

      Please contact our sales team for access credentials and a Device Address Block (if necessary).

      Azure

      We recommend creating an Azure Resource Group (RG) for this deployment during the preparation stage. If you intend to manage the RG with Terraform you can import it into the tfstate later during the deployment.

      After creating the RG we recommend to set up Azure Storage for Terraform backend. You can read more about this in Azure Documentation.

      You need to have rights to create the following resources in the RG:

      • Azure Kubernetes Service
      • Azure Database for PostgreSQL Flexible Server
      • NAT Gateway
      • Private DNS Zone
      • Public IP Address
      • Public IP Prefix
      • Storage Account
      • User Assigned Managed Identity
      • Virtual Network
      • Log Analytics Workspace (optional)
      ← Architecture Configuration →

      On this page

      • Tools
      • License
      • (Optional) Packet Broker Access
      • Azure

      Sections

      Getting Started

      Concepts

      Cloud

      Enterprise

      Integrations

      API

      Hardware

      Sitemap

      View our Sitemap

      Contributing

      GitHub

      About Us

      The Things Industries

      Privacy Policy

      Cookie settings

      Cookie Settings

      We use cookies to enhance your experience, analyze site traffic and deliver personalized content. Read our Privacy Policy.

      Cookie categories