> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/open-telemetry/configuration.md).

# Configuration

How the Hermes configuration runbook is organized, from Salesforce setup and cloud deployment through backends, operations, and upgrades.

Configuring Hermes touches two surfaces: your Salesforce org (auth, permissions, per-org settings) and your own cloud (where the Hermes container actually runs). This section is the runbook for both, split into focused pages you can work through in order.

***

## What You Configure, and in What Order

1. [**Salesforce setup**](https://docs.pharos.ai/open-telemetry/configuration/salesforce-setup.md) — create the External Client App (or Connected App) Hermes authenticates with, generate the RSA keypair for JWT Bearer auth, and set per-org export behavior on `OTel_Configuration__mdt`.
2. **Deploy to your cloud** — [AWS](https://docs.pharos.ai/open-telemetry/configuration/aws.md) or [Azure](https://docs.pharos.ai/open-telemetry/configuration/azure.md). Both are provisioned via four staged Terraform modules; each page is a step-by-step runbook from prerequisites to first trace.
3. **Configure orgs and backends** — [`ORG_CONFIGS`](https://docs.pharos.ai/open-telemetry/configuration/org-configs.md) for the export destination and per-org Salesforce and Hermes settings, [mapping & redaction](https://docs.pharos.ai/open-telemetry/configuration/mapping-and-redaction.md) and the [pipeline config YAML](https://docs.pharos.ai/open-telemetry/configuration/pipeline-config.md) if you need overrides, and [backend configuration](https://docs.pharos.ai/open-telemetry/configuration/backends.md) with a runbook per backend.
4. **Validate and operate** — confirm the container is healthy, auth is working, and a first trace lands in your backend ([Operations & Validation](https://docs.pharos.ai/open-telemetry/configuration/operations.md)); wire the [self-instrumentation metrics](https://docs.pharos.ai/open-telemetry/configuration/self-metrics.md) and [dashboards & alerts](https://docs.pharos.ai/open-telemetry/configuration/dashboards-and-alerts.md); pin versions and upgrade per [Versioning & Upgrades](https://docs.pharos.ai/open-telemetry/configuration/versioning-and-upgrades.md).

Each step assumes the one before it is complete — for example, the cloud Terraform modules expect the Salesforce-side auth to already be in place.

***

## Prerequisites

Before you start, make sure you have:

* [**Pharos Triton**](https://triton.pharos.ai/installing-pharos-triton) **2.0 or later installed**, if you plan to use **Iris** (Triton/Pharos application-telemetry bridge). Argus, the Event Monitoring channel, needs no Triton instrumentation and **zero code changes** to your org — it works standalone.
* **A cloud account** — AWS or Azure — with permissions to run Terraform and provision the resources it creates (compute, a state store, a secrets vault).
* **An OTLP-compatible backend.** Honeycomb and Splunk Observability Cloud have direct export blocks; Datadog, Grafana Cloud, and any other OTLP backend are reached through an OpenTelemetry Collector or the generic `otlp` block. See [Backends & Routing](https://docs.pharos.ai/open-telemetry/hermes/backends.md).

***

## Deployment Model

Hermes ships as a single, pre-built Docker image — `pharosai/hermes:<version>` — containing multiple runtime binaries (Iris, Argus RTEM, Argus ELF, and a combined supervisor). You never build this image yourself: Pharos publishes it to Docker Hub, and your cloud's Terraform module imports it into your own registry (ECR on AWS, ACR on Azure).

Both AWS and Azure are provisioned the same way — a staged sequence of Terraform modules:

1. **Registry** — imports the Hermes image into your cloud's container registry.
2. **Foundation** — state store, secrets vault, and supporting infrastructure.
3. **Runtime** — the container/service itself (ECS Fargate on AWS, Container Apps on Azure).
4. **Alerts** — monitoring and alerting on top of the running service.

Hermes runs entirely inside your own cloud account and never phones home — Pharos never receives your telemetry. Once the Terraform stages are applied and Salesforce auth is in place, the first trace lands as soon as the org emits its first Triton log or Event Monitoring event.

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>☁️ Salesforce Setup</strong></td><td>External Client App, JWT auth, and OTel_Configuration__mdt</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/salesforce-setup.md">Salesforce Setup</a></td></tr><tr><td><strong>🟠 AWS Deployment</strong></td><td>ECS Fargate runbook — staged Terraform, secrets, validation, upgrades, monitoring</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/aws.md">AWS Deployment</a></td></tr><tr><td><strong>🔵 Azure Deployment</strong></td><td>Container Apps runbook — staged Terraform, Key Vault, validation, upgrades, monitoring</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/azure.md">Azure Deployment</a></td></tr><tr><td><strong>🧩 ORG_CONFIGS Reference</strong></td><td>The export block, per-org settings, state stores, and env vars</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/org-configs.md">ORG_CONFIGS Reference</a></td></tr><tr><td><strong>🗺️ Mapping &#x26; Redaction</strong></td><td>Mapping layering and PII redaction controls</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/mapping-and-redaction.md">Mapping &amp; Redaction</a></td></tr><tr><td><strong>📜 Pipeline Config (YAML)</strong></td><td>The mapping YAML reference — sections, merge rules, recipes</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/pipeline-config.md">Pipeline Config (YAML)</a></td></tr><tr><td><strong>🎯 Backend Configuration</strong></td><td>Backend blocks and Collector wiring, with runbooks per backend</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/backends.md">Backend Configuration</a></td></tr><tr><td><strong>🩺 Operations &#x26; Validation</strong></td><td>Health checks, validation checklist, troubleshooting</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/operations.md">Operations &amp; Validation</a></td></tr><tr><td><strong>📡 Self-Instrumentation Metrics</strong></td><td>What Hermes reports about itself and what to alert on</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/self-metrics.md">Self-Instrumentation Metrics</a></td></tr><tr><td><strong>🔔 Dashboards &#x26; Alerts</strong></td><td>The dashboard suite and alert set shipped for every backend</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/dashboards-and-alerts.md">Dashboards &amp; Alerts</a></td></tr><tr><td><strong>🏷️ Versioning &#x26; Upgrades</strong></td><td>What a version promises, how to pin, upgrade, and roll back</td><td><a href="https://docs.pharos.ai/open-telemetry/configuration/versioning-and-upgrades.md">Versioning &amp; Upgrades</a></td></tr></tbody></table>
