Lambda: known Terraform limitations

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 itself. This page collects the recurring ones for this module, says plainly what causes each, gives the native workaround in full, and - where one exists - shows the Operational Rule that removes the need for a fork.

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

The native fix is ignore_changes = [s3_key, s3_object_version, source_code_hash, image_uri] on the function, which is a lifecycle argument. Fork this module and add the lifecycle block to the resource yourself. That works, and it is the honest answer - it is what module maintainers do when they need it. The cost is ongoing rather than one-off: the fork has to be re-synced with every upstream release, and each sync needs a review to confirm the block still lands on the resource it was meant for. A wrapper module does not avoid this, because the lifecycle block still has to sit inside the resource block, which is inside the module you did not write.

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.

Managed fix

Native option only, today. compliance.tf has no rule for this yet, so the workaround above is the whole answer. The rule that would answer this is not built yet.

Using the maintained alternative

compliance.tf serves this module from a registry that applies the rules above during terraform init. The change is the source line; the inputs and outputs are the upstream module's.

module "lambda" {
  source = "https://cis.compliance.tf/terraform-aws-modules/lambda/aws"

  # ... the same inputs you pass today ...
}

None of the limitations above has a rule yet, so this module is served with compliance controls only. The ?add_rules= parameter takes the ids of rules that do exist - see Operational Rule Definitions.

Related

• Operational Rules - what rules are, and how they differ from compliance controls
• Operational Rule Definitions - the HCL of every selectable rule
• 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