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
          • Deployment Guide
          • Post Deployment Configuration
          • Updating AWS AMI Deployment
          • Best Practices
          • Application Server Telemetry
          • Troubleshooting AWS AMI Deployment
        • AWS ECS
      • Kubernetes
      • Docker
      • The Things Join Server
      • Manage The Things Stack

      Best Practices

      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 best practices of a The Things Stack deployment on AWS AMI.

      Staging

      Performing maintenance operations requires in-depth knowledge of AWS and The Things Stack. It is likely that certain action might have unexpected results. For this reason, we strongly advise to maintain a staging environment, and test all updates on staging before deploying to production.

      Back-ups

      The Things Stack uses three types of storage:

      1. AWS RDS database

      2. AWS ElastiCache database

      3. S3 buckets

      AWS RDS and AWS ElastiCache databases keep important data. By default they have automatic backups. It is advised to periodically check that the backups are still performed correctly, and they restore successfully.

      You might want to consider turning on versioning on the S3 buckets. Currently this can’t be done from our CloudFormation template, but you can do it in bucket settings. Data in these buckets is not vital for functioning of The Things Stack, but loss might result in incovenience.

      SSH access

      EC2 machine included in CloudFormation template can be accessed via SSH. It is suggested to access the machine only from an SSH gateway or the internal network, and to manage the SSH key securely. The CloudFormation template offers a firewall setting for limiting SSH access to a given subnet.

      Alerting

      It is advised to set up an alerting system for basic values like CPU/Memory usage or number of uplinks. Currently the single-AMI template does not offer an alerting solution out of the box, but you can refer to the AWS ECS deployment for an example setup.

      ← Updating AWS AMI Deployment Application Server Telemetry →

      On this page

      • Staging
      • Back-ups
      • SSH access
      • Alerting

      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