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-29 · 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-jenkins-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-jenkins/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-jenkins-1.0.0.sigstore.json \
aws-jenkins-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "a2ead02ad06b50717a7b34a806df168323ffac21c94efb555ab8e794d3eea3a7 aws-jenkins-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "jenkins" {
source = "www.iac-bazaar.com/iac-bazaar/aws-jenkins/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-jenkins?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Jenkins Controller on AWS (EC2)](https://www.iac-bazaar.com/catalog/aws-jenkins?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "jenkins" {
source = "www.iac-bazaar.com/iac-bazaar/aws-jenkins/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-jenkins — Jenkins Controller on AWS
A single-node Jenkins controller on EC2 with secure defaults baked in. The
instance runs Amazon Linux 2023 and installs Jenkins (stable) + Amazon
Corretto 17 via cloud-init. IMDSv2 is enforced (http_tokens = required), the
root EBS volume is always encrypted (gp3 by default), and the module ships an
SSM-agent-ready, least-privilege instance profile (just
AmazonSSMManagedInstanceCore) so you get Session Manager shell access with no
SSH keys and no inbound SSH at all. The security group exposes the Jenkins UI and
SSH only to the CIDR blocks you list in allowed_cidrs — there is no
open-to-the-world default.
Self-contained for quick trials: leave subnet_id unset and the module
discovers a subnet in the account's default VPC and derives the matching VPC
for the security group.
Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
What it provisions
aws_instance— the Jenkins controller (IMDSv2-only, encrypted gp3 root, EBS-optimized).aws_security_group+ standalone ingress/egress rules — UI (jenkins_port) and SSH (22) fromallowed_cidrs; all egress for package/plugin installs.aws_iam_role+aws_iam_instance_profile— SSM-ready, least privilege.
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
- Notes
Related modules
aws-codebuild
privileged_mode hands the build the Docker socket, so anything it runs can read every environment variable and assume the service role. Off by default, and a PLAINTEXT variable whose name looks like a secret is refused.
aws-fis
FIS refuses a template with no stop condition, which reads like a guarantee - and source = 'none' is a legal stop condition meaning the experiment never halts by itself. Refused here, along with targets that grow at run time and an empty-target mode that reports success for having tested nothing.
aws-codeartifact
A repository with a public external connection serves whatever the public registry holds for any name it does not. This puts the connection on its own repository, reached through an upstream, and emits the origin-control commands Terraform cannot apply.
aws-appconfig
AppConfig exists to deploy a configuration slowly and roll it back automatically, and both halves are opt-in - the predefined AllAtOnce strategy is 100% of the fleet with zero bake time. Gradual here, and a precondition refuses an environment with no alarms, where automatic rollback has nothing to fire on.
ansible-aws-cli-v2
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.
aws-mwaa
webserver_access_mode defaults to PUBLIC_ONLY, and the Airflow UI is not a dashboard: anyone who reaches it can trigger a DAG, which is arbitrary Python running as the execution role. PRIVATE_ONLY here, all five log streams on, and a precondition refuses an unpinned requirements.txt or plugins.zip - where bucket write access is otherwise the same permission as code execution.