step-ca Private CA, Initialised Once, Proven By Issuing

Smallstep step-ca and the step CLI from the upstream releases (sha256-verified) as a hardened system service on loopback, initialised once by its own user: root and intermediate keys, ca.json and a JWK provisioner. The live test reads the CA's health, has it issue a certificate, verifies it against the root and sees a wrong password refused. 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-agnosticSecrets & KMSv1.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.

A KV v2 Engine that Keeps Versions and Refuses Blind Overwrites A Private CA that Issues from the Intermediate with Roles Bound to Domains AppRole Roles that Bind to Somewhere Specific and Issue Secret IDs that Expire Dynamic PostgreSQL Credentials with the Root Password Rotated Away OIDC Auth Whose Roles Admit the Claims You Name OpenBao Server With Integrated Storage, Initialised In The Lane Transit Keys that Rotate and Cannot Be Deleted or Exported Vault Policies & Auth

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_step_ca" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-step-ca/any"
  version = "1.0.0"
}

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