What Is SaltStack? Architecture, Master and Minion, Salt Versions and When to Use It

SaltStack 18 min min read Updated: Nov 17, 2026 Beginner
What Is SaltStack? Architecture, Master and Minion, Salt Versions and When to Use It
Beginner Topic 1 of 3

What Is Salt?

Salt (also called SaltStack) is an open-source tool for two jobs: remote execution (run a command on thousands of servers in seconds) and configuration management (describe how a server should look, and Salt makes it so). It is written in Python and released under the Apache 2.0 licence.

Name check: The company called SaltStack was bought by VMware, and VMware was later bought by Broadcom. Today the open-source tool is maintained as the Salt Project, with Broadcom as its main sponsor. People still say 'SaltStack' and 'Salt' for the same thing.

The Two Big Ideas

IdeaMeaningExample
Remote executionRun a function on many machines at once, right nowsalt '*' pkg.upgrade
Configuration management (states)Describe the wanted state in YAML files. Salt checks and fixes each machine'nginx installed, running, config file correct'

Architecture: Master and Minions

text β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ Salt Master β”‚ holds states, pillar data, keys β”‚ publish :4505 ret :4506β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜ publish (ZeroMQ)β”‚ β”‚ results back β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”΄β”€β”€β”€β”¬β”€β”€β”€β”΄β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β–Όβ”€β”€β”€β” β”Œβ”€β”€β”€β”€β–Όβ”€β”€β”€β”β”Œβ”€β”€β”€β–Όβ”€β”€β”€β”€β”β”Œβ”€β”€β–Όβ”€β”€β”€β”€β”€β” β”Œβ”€β”€β–Όβ”€β”€β”€β”€β”€β” β”‚Minion 1β”‚ β”‚Minion 2β”‚β”‚Minion 3β”‚β”‚Minion 4β”‚...β”‚Minion Nβ”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”˜
PartJob
Salt masterThe control server. You type commands here. It keeps the state files and sends jobs to minions
Salt minionA small agent on each managed machine. It keeps a connection open to the master, runs the job, and returns the result
PortsMaster listens on 4505 (publish: master to minions) and 4506 (return: minions to master). Only the master needs inbound ports. Minions connect out
TransportA fast message bus (ZeroMQ by default, with TCP and WebSocket options). Messages are encrypted with keys that the master accepts
salt-sshAgentless mode: runs Salt over SSH, with nothing installed on the target
salt-callRun Salt on the local machine, with or without a master

Because the master pushes a job to all listening minions at the same moment, results can come back from 1,000 machines in a few seconds. This is the main speed advantage of Salt.

Main Building Blocks

TermMeaning
Execution moduleA function you call on demand: pkg.install, service.restart, cmd.run
StateA declaration of a wanted condition, such as pkg.installed. Saved in .sls files
SLS fileA Salt state file, written in YAML with optional Jinja templating
HighstateApplying all states assigned to a minion by the top.sls file
GrainsFacts about a minion (OS, CPU, IP). Collected by the minion
PillarSecure data defined on the master and given only to chosen minions (passwords, settings)
Top filetop.sls: says which states or pillar data go to which minions
FormulaA reusable, shareable set of states (like a module or role)
ReactorRun actions when an event happens (a new minion starts, a file changes)
BeaconWatches a minion and sends events (disk full, file changed, service stopped)
OrchestrationRun steps across many machines in order, such as 'database first, then web'
ReturnerSends job results to another place (database, Redis, Slack)
RunnerA function that runs on the master (salt-run)

A First Look

bash # Remote execution: run on all minions salt '*' test.ping salt '*' cmd.run 'uptime' salt 'web*' pkg.install nginx # Configuration management: apply the wanted state salt 'web*' state.apply nginx
yaml # /srv/salt/nginx/init.sls nginx: pkg.installed: [] service.running: - enable: True - require: - pkg: nginx

Salt Versions: LTS and STS

Since version 3006 the Salt Project uses a long-term support (LTS) and short-term support (STS) model. Salt versions are numbers like 3006, 3007, 3008. If you are unsure which one to use, the project advises using an LTS release.

ReleaseTypeNotes
3006LTS (April 2023)Very common in production today. In its critical-fixes phase now
3007STS (March 2024)A short-term release. Support has ended, so move off it
3008LTS (May 2026)The current LTS to learn and deploy. Updated bundled Python (3.11), x509 v2 modules by default, and more
Always check the lifecycle page: Dates and versions change. Before you choose a version for production, open the Salt Install Guide page called 'Salt version support lifecycle' and pick a version that is still supported.

What Is Onedir?

Modern Salt packages use onedir: one folder (/opt/saltstack/salt on Linux) that contains Salt and its own Python and libraries. So Salt does not depend on the system Python. Extra Python libraries for Salt are installed with the salt-pip helper, not the system pip.

Salt, Ansible and Puppet

SaltAnsiblePuppet
ModelMaster and minion (also agentless salt-ssh)Agentless over SSHAgent pulls from a server
Speed for big fleetsVery fast (persistent connections, parallel)Slower on huge fleets (SSH per host)Depends on run interval
LanguageYAML + Jinja (Python for custom modules)YAML + JinjaPuppet language
Real-time commandsExcellent (salt '*' ...)Ad hoc commands availableUse Bolt
Event-driven automationBuilt in (events, reactor, beacons)Needs extra toolsLimited
Learning curveMedium (many concepts)LowMedium

Typical Uses

  • Run a command, restart a service or install a patch on hundreds of servers right now
  • Keep servers configured the same way, and fix drift
  • Build servers in the cloud and configure them (Salt Cloud, cloud-init)
  • React to events: a disk filling up triggers a clean-up job
  • Manage Windows, Linux, macOS, network devices (through proxy minions)
  • Run orchestrated, step-by-step changes across tiers

What You Will Build in This Course

  1. Install a master and minions in a lab
  2. Run remote commands and target machines by name, grain and group
  3. Write states, use Jinja and grains, and keep secrets in pillar
  4. Organise code with formulas and Git
  5. Use events, the reactor, beacons and orchestration
  6. Secure, test, and troubleshoot Salt, and finish with three real projects and interview questions

Practice Tasks

  1. Draw the master and minion diagram and label ports 4505 and 4506
  2. In your own words, explain the difference between remote execution and states
  3. Open the Salt version support lifecycle page and write down which version is the current LTS
  4. List three jobs in your work that you could do with salt '*' ...

Conclusion

Salt is a fast remote execution and configuration tool built on a master and minion model with an event bus. Learn the 3008 LTS line, and remember the four core ideas: execution modules, states, grains and pillar.

Quick Summary: master 4505/4506; minion; remote execution vs states; grains vs pillar; top.sls; LTS 3006/3008; onedir.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators