Skip to content
MAF Learning Hub
Advanced Duration: 25 min

Automating infrastructure (IaC)

Running one agent by hand is fine; running a fleet across environments is not. Infrastructure as Code (IaC) makes the platform behind your agents repeatable, reviewable, and recoverable - the foundation of platform engineering for the agent fabric.

What you will learn

  • What IaC is and why it matters for an agent platform.
  • How environments and promotion work when infrastructure is code.
  • How IaC pairs with the deployment descriptors from Track 4.

Infrastructure as Code

IaC describes your infrastructure - runtimes, gateways, networking - as version-controlled files instead of manual console clicks. The benefits map directly onto agent operations:

  • Repeatable - stand up an identical environment on demand.
  • Reviewable - changes go through pull requests, like any other code.
  • Recoverable - rebuild from source if something drifts or fails.

Environments and promotion

Because the definition is code, you promote the same configuration from sandbox to production by changing variables, not by rebuilding by hand - which keeps your governed agent platform consistent across stages.

# platform.yaml (excerpt, illustrative)
environments:
  - name: sandbox
    replicas: 1
  - name: production
    replicas: 3
gateway:
  omni: true
monitoring:
  enabled: true

Forward-looking

The IaC descriptor above is illustrative and tool-agnostic; use your organization's chosen IaC tooling and confirm any MuleSoft-specific provisioning against official documentation.

Pairing with Track 4 deployments

IaC provisions the platform; the deployment descriptors from Track 4 place agents onto it. Together they make the whole stack - from network to running agent - reproducible.

Next steps

Continue to Managing network topographies and egress control to lock down how your platform and agents talk to the outside world.

References