Lambda

Some things people ask the terraform-aws-modules/lambda/aws module for cannot be implemented by any module, in any registry: they are limits of Terraform and OpenTofu themselves. This page is for engineers who hit one of them. For each it says what causes it, gives the native workaround in full, and, where one exists, shows the Operational Rule that removes the need for a fork. Read the native option first; several are the right answer on their own.

Terraform keeps reverting my Lambda code to an old version

The pipeline publishes a new artifact and updates the function. Terraform holds the s3_key, source_code_hash, or image_uri from the last apply and pushes the old code back on the next one, so a deploy can be silently undone by an unrelated infrastructure change.

Why Terraform cannot fix this. Terraform's model is that it owns every attribute it can see. When a controller, an autoscaler, a scanner, or a deployment pipeline writes to one of those attributes, Terraform reads the new value as drift and plans to put its own value back. Both systems are behaving correctly; they simply disagree about who owns the field.

The only mechanism Terraform offers for splitting ownership is ignore_changes, and that is a lifecycle argument, which brings the literal-value restriction above with it. A module cannot accept the list of attributes to ignore as an input, so a module consumer has no way to declare the split.

The native workaround. This module has a native option for a local zip: set ignore_source_code_hash = true, and Terraform stops comparing the package hash. It does not cover a pipeline that changes s3_key, s3_object_version or image_uri: the module has no ignore_changes on the function, so those still revert. For those, the native fix is ignore_changes on the function, which means forking the module.

The clean alternative is to stop splitting ownership: build the artifact in the same pipeline that runs Terraform, and let Terraform publish it. That is the better answer when the two pipelines can be merged.

The rule that answers it. lifecycle_ignore_deployed_artifacts adds the block for you, server-side, while the module is being downloaded. What arrives in .terraform/modules/ is ordinary HCL with this change already in it, and nothing else about the module changes: same inputs, same outputs, same version.

 resource "aws_lambda_function" "this" {
   # ... the module's own configuration, unchanged ...
+
+  lifecycle {
+    ignore_changes = [s3_key, s3_object_version, source_code_hash, image_uri]
+  }
 }

Use the rule

This source line applies the rules above during terraform init. The inputs and outputs stay the upstream module's.

module "lambda" {
  source = "https://registry.compliance.tf/terraform-aws-modules/lambda/aws?version=x.y.z&add_rules=lifecycle_ignore_deployed_artifacts"

  # ... the same inputs you pass today; the version is in the URL above ...
}

• Pin the version in the URL. ?version= takes an exact release; without it the registry serves the latest. Delete the version argument, which Terraform accepts only on registry-protocol sources. Several rules go in ?add_rules=, separated by commas.
• Keep the token out of the source line. Register a free compliance.tf account and configure an access token; it never goes in the source line or in git.
• Preview in the Playground, within its limits. The Rules Playground shows the diff with no account, at the version it pins for Lambda, which need not be yours. It reads the module root only: a rule whose resource lives in a submodule shows no diff there even though the download applies it, and a module that publishes nothing but submodules cannot be previewed. It takes the list as ?rules= because it previews rules on their own rather than against your Baseline.

On registry.compliance.tf, or on a framework host, ?add_rules= adds to whatever Baseline your organization has Enforced; on an organization host that organization's configuration decides. A module compliance.tf builds for you carries a compliancetf-manifest.json naming every rule the build received, each with an outcome recording what it did.

Related

• Rules overview - what rules are, and how they differ from compliance controls
• Rule definitions - the HCL of every selectable rule
• lifecycle_ignore_deployed_artifacts - the rule page, with limits and failure modes
• Stop paying the Terraform fork tax - why forking a module to add a lifecycle block costs more than it looks
• Lambda module reference - inputs, outputs, and the controls applied to it