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
        • AWS Marketplace AMI
        • AWS ECS
          • Architecture
          • Prerequisites
          • Deployment
          • Database Operations
          • Monitoring
          • Updating
          • Best Practices
          • Interoperability
          • Mutual TLS
          • Troubleshooting AWS ECS Deployment
          • Template Changelog
      • Kubernetes
      • 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 page describes what you need for deploying The Things Stack on AWS ECS.

      Before you can start the deployment, you will need to make sure that you have:

      • An AWS account with billing enabled.
      • An SSH keypair registered in the AWS region of choice.
      • A domain name with a hosted zone in AWS Route 53. For multi-tenant deployments, you need to be able to add a wildcard subdomain under this domain.
      • A username and password for an SMTP server for sending emails, or a Sendgrid API key with “Mail Send” rights.
      • A LoRa Alliance NetID and DevAddr block. For development and testing it is possible to use NetID 000000 and DevAddr block 00000000/7, or NetID 000001 and DevAddr block 02000000/7.
      • A license key for The Things Stack.
      • Configuration and Certificates for Backend Interfaces interop (optional).
      • Configuration and Certificates for Packet Broker peering (optional).

      You will need to come up with the following parameters, which will be used in multiple places:

      • Network Name: the name of the network. Example: The Things Industries uses ttich for their Cloud Hosted service.
      • Environment: prod or staging.
      • Cluster: the name of the cluster. Example: The Things Industries uses continent+number for their Cloud Hosted service. eu1 for Europe 1, nam1 for North America 1, etc.
      • Cluster Secret for internal communication. This can be randomly generated with openssl rand -hex 24. When deploying a network with multiple clusters, this needs to be the same for all clusters.
      • OAuth Client ID and Secret for the Console. Example: The Things Industries uses client ID console- + cluster for their Cloud Hosted service. console-eu1 for the Console of the Europe 1 cluster. The client secret can be randomly generated with openssl rand -hex 24.
      • OAuth Client ID and Secret for Device Claiming. Example: The Things Industries uses client ID device-claiming- + cluster for their Cloud Hosted service. device-claiming-eu1 for the Console of the Europe 1 cluster. The client secret can be randomly generated with openssl rand -hex 24.
      ← Architecture Deployment →

      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