Getting started¶
This page helps you decide which AMS pieces to install before you touch Helm.
Step 1 — Choose application modules¶
AMS exposes four customer-facing application modules. You may install only one, or any combination up to all four.
| Module | Typical use |
|---|---|
| Command Center | Primary AMS UI and control plane experience |
| ARE | Agent Runtime Environment (backend + UI) |
| EOBS | Engineering Observability UI |
| FortifyOps | Red-teaming / FortifyOps UI |
If you install all four¶
Treat Command Center as the primary module. Shared infrastructure ingress should set:
That means the browser path / on your AMS hostname opens Command Center. The other modules remain available on their own path prefixes (for example /eobs, /fortify-ops, ARE UI paths).
If you install a single module¶
That module becomes primary. Set root.module to match:
| Installed module | root.module value |
|---|---|
| Command Center | command-center |
| EOBS | eobs |
| FortifyOps | fortifyops |
| ARE | are |
You can change the landing module later by updating ingress values and re-applying the chart.
Step 2 — Plan shared dependencies¶
Regardless of module choice, plan for these in order:
- Infrastructure — cluster, ingress controller / Application Gateway, DNS, TLS, image pull, secrets/database as required
- Observability — so modules and adapters can emit metrics, logs, and traces
- Keycloak — so users can sign in
- Infrastructure ingress — one shared host and landing route
Do not skip Keycloak or observability if you expect a production-like AMS experience. Ingress must be installed (or updated) after you know which module owns /.
Step 3 — Decide on adapters¶
Adapters are background workers, not customer landing pages. Add them only when you need telemetry or integration with an external product:
| Adapter | Typical pairing |
|---|---|
| Dify adapter | Self-hosted or external Dify + often Langfuse |
| EMA adapter | EMA integration path |
| LibreChat adapter | LibreChat chat surface |
| Lyzer adapter | Lyzer integration path |
| MS Copilot adapter | Microsoft Copilot integration path |
See Adapters overview and Dify, Langfuse, and LibreChat.
Step 4 — Decide how operators reach the cluster¶
Before any helm install, decide:
- Private AKS only (VPN, ExpressRoute, or jump host), or
- Public AKS API, or
- Jump VM inside the VNet
Open Network access patterns, then the matching Helm guide.
What we intentionally do not provide here¶
- Ready-made Terraform / Bicep / shell IAC for AKS or Application Gateway
- A single “install everything” script
Your cloud and network teams keep ownership of those blueprints. These guides stay stable even when your IAC evolves.