👀 Views: 81 💬 Answers: 1 📅 Created: 2025-06-06

terraform aws lambda HCL

I'm testing a new approach and I'm working with an scenario where Terraform refuses to apply changes to my AWS Lambda function due to what seems to be an invalid key in my configuration... I am using Terraform version 1.3.9 with the AWS provider version 4.0.0. My Lambda function resource is defined as follows: ```hcl resource "aws_lambda_function" "my_lambda" { function_name = "my_lambda_function" role = aws_iam_role.lambda_exec.arn handler = "index.handler" runtime = "nodejs14.x" source_code_hash = filebase64sha256("./lambda.zip") filename = "./lambda.zip" } ``` I recently updated the runtime from `nodejs12.x` to `nodejs14.x`, and now when I run `terraform apply`, I get the following behavior: ``` behavior: InvalidParameterValueException: The function configuration is invalid. The following key is invalid: runtime ``` This behavior appears even though I have verified that the Lambda function exists in the AWS console and I can see that it's currently running on `nodejs14.x`. I've tried several things to resolve this scenario: - Running `terraform plan` to see if there are any differences that need to be applied, and it indicates that the runtime is indeed set to `nodejs14.x`. - Destroying the resource and recreating it, but I still receive the same behavior. - Checking the IAM role permissions to make sure the Lambda function has the necessary permissions to be updated, which seem correct. How can I troubleshoot this scenario further? Is there something specific I need to adjust in my Terraform configuration or AWS Lambda settings to avoid this invalid key behavior?