EC2 Launch Template + Auto Scaling Group
EC2 launch template and Auto Scaling group with IMDSv2 enforced, encrypted gp3 root volume, an egress-only security group, and scale-to-zero defaults so it applies cleanly with no compute cost.
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-autoscaling-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-autoscaling/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-autoscaling-1.0.0.sigstore.json \
aws-autoscaling-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "599d940f4b20e5b185380a47966b006b0124abd963caa7474730217a827e8fd1 aws-autoscaling-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "autoscaling" {
source = "www.iac-bazaar.com/iac-bazaar/aws-autoscaling/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-autoscaling?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [EC2 Launch Template + Auto Scaling Group](https://www.iac-bazaar.com/catalog/aws-autoscaling?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "autoscaling" {
source = "www.iac-bazaar.com/iac-bazaar/aws-autoscaling/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-autoscaling
EC2 launch template + Auto Scaling group with secure defaults. Works with
Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0. The launch
template enforces IMDSv2, encrypts the root volume, and the group is wired to
always track the template's latest version. Networking is self-contained: with
no subnets supplied the module uses the account's default VPC and creates an
egress-only security group, so it applies cleanly in a fresh account.
By default the group scales to zero (desired_capacity = 0, min_size = 0):
the ASG and launch template are created and fully exercised, but no instances
launch — no compute cost. Raise desired_capacity to run instances.
Secure defaults:
- IMDSv2 required on the launch template (
http_tokens = required) — blocks the SSRF → credential-theft class of attacks - Root volume encrypted at rest always (AWS-managed
aws/ebskey, or yourkms_key_id), gp3 by default - Egress-only security group (no inbound) created automatically; bring your
own via
security_group_idsto allow specific ingress ebs_optimizedinstances; instance tags propagated to launched instances
Security notes
- IMDSv2 is enforced and cannot be disabled by a variable — only the hop limit is tunable.
- The root volume is always encrypted; you can choose the KMS key.
- The module-managed security group has no inbound rules. Add ingress by
supplying your own
security_group_ids.
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-image-builder
A pipeline with no schedule builds when somebody clicks, so the golden image ages until a person remembers it; image tests are the switch turned off to save an hour and scanning is off unless enabled; and the build instance's metadata service can hand its credentials to whatever a step downloads. Weekly rebuilds when a dependency changed, tests and scanning on, IMDSv2-only builds.
aws-lightsail-instance
A Lightsail instance is created with 22 and 80 open to every address; its public address changes when it stops unless a static IP is attached, and every DNS record pointing at it is then wrong; and automatic snapshots are off. The port list replaced by your rules with SSH from anywhere accepted by name, a static IP attached, and the daily AutoSnapshot add-on on at the hour you choose.
aws-ssm-patch-manager
A patch baseline that approves security patches after a delay, the patch group that binds instances to it by tag, and a maintenance window that runs AWS-RunPatchBaseline on a schedule with the output in CloudWatch. Install rather than Scan (scan-only by name), RebootIfNeeded, and unapproved security updates counted as non-compliant so the approval delay shows on the dashboard.
aws-elastic-beanstalk
AWS Elastic Beanstalk with the defaults turned the right way: managed platform updates are ON (AWS leaves them off, so the platform is never patched), health reporting is enhanced rather than basic, logs stream to CloudWatch and survive termination, IMDSv1 is disabled, deployments go out in batches instead of all at once, and application versions are pruned before they hit the quota.
aws-batch
Batch does not retry by default, so a reclaimed spot instance or a timed-out image pull ends as FAILED - reported as if the job failed on its merits, which is how somebody ends up debugging working code. Retries infrastructure failures and exits on real ones.
aws-ec2-instance
EC2 instance with IMDSv2, encrypted EBS, instance profile, and EIP - secure defaults out of the box.