Air-Gapped Operations
An air-gapped environment is one that's isolated from the public internet, requiring all necessary components to be available locally. This section outlines what you'll need to deploy and operate Mattermost in a self-hosted air-gapped environment — preparation, deployment guidance, and the configuration changes required for a successful deployment.
Deploying Mattermost in an air-gapped environment requires preparing all necessary software, container images, and configuration resources in advance, since the target system has no direct internet access; transferring these artifacts to the isolated network using secure media; and then installing, configuring, and validating the deployment within the air-gapped environment.
In this section
- Air-gapped deployment runbook — the high-level steps to prepare for and complete an air-gapped install.
- Bill of Materials and Registry Mirroring — what to gather before you cross the air gap, and how to set up a private package mirror or container registry.
- Configure for Air-Gapped Operation — server settings that depend on internet access and should be disabled or adjusted.
For the architectural context — when an organization needs an air gap, and which Mattermost capabilities it rules out — see the Deploy in Air-Gapped Environments deployment scenario.