Error "image_uri" is not expected here.

[nirsv]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.12.25

• provider.aws v3.5.0

Affected Resource(s)

• aws_lambda_function

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_lambda_function" "my-dockerized-lambda" {
  image_uri                      = var.lambda_image_uri
  description                    = "Lambda using docker image"
  function_name                  = "my-lambda-function"
  role                           = aws_iam_role.lambda-role.arn
  handler                        = "my_lambda.lambda_handler"
  runtime                        = "python3.6"
  timeout                        = "780"
  memory_size                    = "512"
  reserved_concurrent_executions = "-1"
  publish                        = false

  vpc_config {
    subnet_ids         = var.subnets
    security_group_ids = [data.aws_security_group.default_sg.id]
  }

  environment {
    variables = merge(
      var.env_vars
    )
  }
}

Debug Output

Panic Output

Expected Behavior

I expect the lambda to be created (at least the plan to succeed)

Actual Behavior

Error: Unsupported argument
An argument named "image_uri" is not expected here.

Steps to Reproduce

1. terraform plan

Important Factoids

References

• #0000

[ewbankkit]

@nirsv Thanks for raising this issue.
AWS Lambda container image support (and the image_uri attribute) was added in #16512 and released in v3.19.0 of the Terraform AWS Provider.
You will need to upgrade to at least that version of the provider for the functionality you require.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!