Zabbix Agent 2 Over A Pre-Shared Key

Zabbix agent 2 from the vendor's repository, its key pinned by fingerprint: passive checks only for the servers you list, over a pre-shared key generated on the host, no active checks until you name a server, remote commands refused. The live test asks with zabbix_get and is refused from an unlisted address, with a wrong key and in plaintext. 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.

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.

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_zabbix_agent2" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-zabbix-agent2/any"
  version = "1.0.0"
}

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