ACM Certificate (DNS-validated)
Requests a public, DNS-validated ACM TLS certificate that ACM auto-renews forever, outputting the validation records to publish - CT logging on, wildcards and SANs supported.
Compare Managed TLS Certificates across clouds →
Part of: AWS Production Landing Zone
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o aws-acm-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-acm/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-acm-1.0.0.sigstore.json \
aws-acm-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "8329a4a081761fddaeabde83adc2e1aec6e15028ee691914698ebd10a0e9f9ba aws-acm-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "acm" {
source = "www.iac-bazaar.com/iac-bazaar/aws-acm/aws"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-acm?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [ACM Certificate (DNS-validated)](https://www.iac-bazaar.com/catalog/aws-acm?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "acm" {
source = "www.iac-bazaar.com/iac-bazaar/aws-acm/aws"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
aws-acm
Public ACM TLS certificate, DNS-validated. Works with Terraform and
OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0. The module requests the
certificate and outputs the DNS records you publish to validate it — and from
then on ACM auto-renews it forever with zero further action.
It deliberately does not create an aws_acm_certificate_validation
resource. That resource blocks the apply until the validation records resolve
in public DNS, coupling a fast, free certificate request to slow external DNS
propagation (and failing the apply outright if you do not control the zone yet).
Instead, take the domain_validation_options output, publish one CNAME per
entry (e.g. with aws_route53_record), and let ACM validate asynchronously.
Secure defaults:
- Certificate Transparency logging ENABLED — required for the certificate to be trusted by modern browsers; only disable for private/internal names.
- DNS validation by default — the only method that supports unattended auto-renewal (EMAIL validation needs a human to click a link every renewal).
RSA_2048key for the broadest client compatibility (EC algorithms offered).- Wildcard names (
*.example.com) and SANs supported and validated. create_before_destroyso the replacement certificate exists before the old ARN is removed, never leaving a listener pointing at a deleted certificate.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
aws-cloudhsm
Cluster and HSMs, with the parts nobody mentions: AWS holds no copy of your keys, Terraform cannot initialise the cluster, and an uninitialised cluster bills per HSM per hour while being unable to store anything.
aws-private-ca
A root or subordinate CA with revocation configured, its certificate installed in the same apply, and ACM permitted to issue from it. Documents the two traps: a CA bills through its deletion window, and one without CRL or OCSP can issue certificates it can never revoke.
aws-kms
Customer-managed KMS keys with sane key policies, aliases, rotation, and multi-region replicas.
aws-ssm-parameter-store
Map-driven SSM Parameter Store parameters - String, StringList, and SecureString - created from a single map, with SecureString always KMS-encrypted and the free Standard tier by default.
aws-secrets-manager
Secrets with versioning, resource policies, replication, and optional Lambda rotation scaffolding.
ansible-chamber
chamber on EL 10 from the GitHub release; get_url refuses it unless its SHA-256 is in the vendor's checksums file, and the live test re-checks it, then runs list with no credentials and the metadata service off, expecting 'no EC2 IMDS role found', and exercises the null backend (a list answered, a read refused). Pinned. Original role, live-tested on Rocky Linux 10.