Internals

Overview

What’s in this Section?

If you’re interested in learning about Fugue‘s internals, including how Fugue is installed, how the Basic and Team Conductors differ, and how Fugue processes work, you’re in the right place. If you’d prefer to read about setting up and configuring Fugue, see Configure. If you’ve already installed Fugue and are ready to use it, see Use. And if you want to try an example or learn about writing Ludwig, see Learn.

Here in Internals, you can find details about:

  • Basic Conductor Features - a list of the standard features our Basic Conductor offers, such as declaration, automation, and enforcement
  • Team Conductor Features - a list of the premium features our Team Conductor offers, such as full multi-account and full RBAC support
  • System Architecture - an in-depth explanation of how Fugue is installed in an AWS account, including a list of the major components of Fugue in AWS
  • Processes - a description of the Fugue process management model and how Fugue performs process work

What is the Conductor?

The Fugue Conductor acts as a “kernel” for automating your cloud infrastructure operations and enforcement. It runs inside your designated AWS account, hosted on an EC2 instance, and carries out cloud workloads in the form of processes. You use the Fugue CLI to communicate with the Conductor. There are two versions of the Conductor: Basic and Team.

To see a general list of the AWS components that support the Conductor, check out Major Component Architecture.

To see a precise list of the CloudFormation stack resources created when you install the Conductor, visit The CloudFormation Stack.

To learn more about how the Conductor handles cloud workloads, see Processes.