Alertmanager On Loopback, Gossip Off

Prometheus Alertmanager from the upstream release (sha256-verified) as a hardened system service on loopback, its cluster gossip listener switched off and its configuration checked by amtool before it lands. The live test posts an alert through the API and reads it back active, held by the default receiver, and expects no 9094 listener at all. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticObservabilityv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

Alloy On Loopback, Reporting Off, Validated Blackbox Exporter, Probed With A Control Grafana With Its Own Secret Key Loki Single Binary, Retention On, Reporting Off Prometheus On Loopback, Retention Written Down Prometheus node_exporter (verified)Pushgateway, Pushes Persisted To Disk VictoriaMetrics On Loopback, Retention Written Down

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_alertmanager" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-alertmanager/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.