This guide has only lightly touched on the many different uses for SaltStack Config. What distinguishes SaltStack Config from similar configuration management systems is its underlying event bus, which is used for inter-process communication between the Salt master and minions. In the event system, events are seen by both the master and minions and events can be monitored and evaluated by both. This high-speed, flexible communication system makes it possible to extend SaltStack Config core capabilities to do nearly any task you need it to do.

For example, with SaltStack Config’s beacon and reactor system, you can monitor:

  • File changes
  • System load
  • Service status
  • Configuration drift
  • Unauthorized login

Using reactors, you can develop automated responses to these network events to provide:

  • File level control
  • Self-healing actions
  • Autonomous configuration
  • Security remediation

Beyond these features that come provided out of the box with SaltStack Config, you also get the ability to customize Salt for your needs. Salt, which powers SaltStack Config, is very pluggable and extendable. If you need your configuration management system to perform custom tasks or functions, you can build your own custom Salt execution or state modules.

Salt is written in Python, which is a programming language that tends to be easier for beginners to learn. It also has a rich open-source community of users that are available to help you solve common problems with Salt and help you learn more.

For more information

See: