AWS CLI v2, Signature Checked Before Unpacking

The AWS CLI v2 from the upstream zip, verified with gpg against the AWS CLI Team key (pinned by fingerprint, in a GnuPG home of its own) before it is unpacked. EL 10 has no package; most installs run curl | unzip and never read the signature. Pinned version, tab completion, and a live test that runs an API call to 'Unable to locate credentials'. 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.

ansibleAWSCI/CD & Automationv1.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 Build Project that Is Not Root on Its Host A Chaos Experiment that Can Be Stopped A Package Domain that Resists Dependency Confusion A Rollout that Can Still Be Taken Back An Airflow UI that Is Not on the Public Internet CodeDeploy CI/CD (EC2 / ECS / Lambda)CodePipeline + CodeBuild CI/CD Jenkins Controller on AWS (EC2)

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_aws_cli_v2" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-aws-cli-v2/aws"
  version = "1.0.0"
}

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