Lambda Function (Packaged & Wired)
Lambda with execution role, log group, triggers, aliases, and zip/container packaging handled.
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-19 · 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-lambda-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-lambda/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-lambda-1.0.0.sigstore.json \
aws-lambda-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "8ab847e28c811be6142ffe6257c2ce8023506d0cd95e1378fbf4c1f2e5e5c662 aws-lambda-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "lambda" {
source = "www.iac-bazaar.com/iac-bazaar/aws-lambda/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-lambda?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Lambda Function (Packaged & Wired)](https://www.iac-bazaar.com/catalog/aws-lambda?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "lambda" {
source = "www.iac-bazaar.com/iac-bazaar/aws-lambda/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-lambda
Lambda with execution role, log group, triggers, aliases, and zip/container
packaging handled. Works with Terraform and OpenTofu (>= 1.6), AWS
provider >= 6.0, < 7.0 (+ hashicorp/archive >= 2.4, < 3.0 for
zip-from-source packaging). Point it at a source directory, a prebuilt zip, an
S3 object, or an ECR image — the module wires everything else: IAM, logging,
invoke permissions, and event-source mappings with the exact read permissions
each source type needs.
Secure / sane defaults:
- Execution role is least-privilege: logs scoped to this function's log
group only (no
AWSLambdaBasicExecutionRoleaccount-wide wildcard); VPC, X-Ray, DLQ, and event-source permissions are added only when the matching feature is configured, scoped to the configured ARNs arm64(Graviton) architecture by default — cheaper per ms- Log group managed explicitly with 30-day retention (KMS optional) and wired
via
logging_config, so retention applies before the first invoke - Optional alias gives triggers and event sources a stable qualifier
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0hashicorp/archive>= 2.4, < 3.0(only exercised whensource_diris used)
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 (key)
- Outputs
Related modules
aws-app-runner
auto_deployments takes every push to the image tag straight to production with no review, which quietly makes the deployment gate "who can push". Off by default, egress routed through your VPC, and the pull role kept separate from the run role.
aws-amplify-app
Every branch build is served at a public amplifyapp.com URL, and basic auth, the switch that puts a password on it, is off; auto branch creation builds every branch anyone pushes; the repository token lands in state; and environment variables are plaintext. Basic auth on every non-production branch (public by name), auto creation off, exactly one production branch, the custom domain attached.
aws-ecs-fargate-service
Full Fargate stack: cluster, task definition, service with ALB integration, autoscaling, and Cloud Map discovery.
aws-step-functions
A Step Functions state machine (STANDARD or EXPRESS) with a least-privilege execution role, a managed CloudWatch log group, X-Ray tracing, and encryption at rest - working out of the box from a single name.
ibm-code-engine-function
A Code Engine function in a project created here, callable only from inside the project unless a public URL is accepted by name, with the compute resource token mounted so it obtains IAM tokens through a trusted profile and needs no API key, and CPU, memory, concurrency and execution time capped so a runaway caller cannot drive the bill.
alicloud-fc-function
A Function Compute 3.0 function running as the RAM role you name, with internet access off (on by name), in your VPC when a vpc_config is given, logging every invocation to a Log Service project and logstore (none by name), with code fetched from an OSS object you uploaded. Memory, CPU, disk, timeout and instance concurrency are inputs.