SSM Agent That rpm On EL 10 Cannot Verify, Verified

The AWS Systems Manager Agent on EL 10, where rpm refuses the SSM signing key (a SHA-1 self-signature) and dnf fails its GPG check, so the usual answer is --nogpgcheck. This role verifies the detached signature with gpg against a pinned fingerprint first, pins the version (latest differs by region), and registers a hybrid activation once. 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.

ansibleAWSCompute & VMsv1.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 Golden AMI Pipeline that Rebuilds on a Schedule, Tests and Scans A Lightsail Instance with a Firewall that Names Its Sources, a Static IP and Snapshots A Patch Baseline, Its Patch Group and a Maintenance Window that Installs An Application Platform That Patches Itself Batch Jobs that Survive a Reclaimed Host EC2 Instance EC2 Launch Template + Auto Scaling Group Streamed Applications That Do Not Leak Data by Default

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_amazon_ssm_agent" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-amazon-ssm-agent/aws"
  version = "1.0.0"
}

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