aws_lambda_event_source_mapping does not retry when modifying source mapping

[cecheta]

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 v1.1.5

• provider registry.terraform.io/hashicorp/aws v3.74.0

Affected Resource(s)

• aws_lambda_event_source_mapping

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_sqs_queue" "queue" {}

resource "aws_lambda_event_source_mapping" "mapping" {
  event_source_arn = aws_sqs_queue.queue.arn
  function_name    = aws_lambda_function.function.arn
}

resource "aws_lambda_function" "function" {
  function_name = "function"
  role          = aws_iam_role.role.arn
  handler       = "index.handler"
  runtime       = "nodejs14.x"
  filename      = "${path.module}/index.zip"
}

resource "aws_iam_role" "role" {
  name = "role"
  assume_role_policy = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Action = "sts:AssumeRole"
        Effect = "Allow"
        Principal = {
          Service = "lambda.amazonaws.com"
        }
      }
    ]
  })
}

resource "aws_iam_policy" "policy" {
  name = "${aws_lambda_function.function.function_name}-policy"
  policy = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Action = [
          "sqs:*"
        ]
        Effect   = "Allow"
        Resource = aws_sqs_queue.queue.arn
      }
    ]
  })
}

resource "aws_iam_role_policy_attachment" "attach" {
  role       = aws_iam_role.role.name
  policy_arn = aws_iam_policy.policy.arn
}

Steps to Reproduce

1. Apply the above configuration
2. Rename aws_lambda_function and aws_iam_role

resource "aws_lambda_function" "function" {
  function_name = "function-rename"
  ...
}

resource "aws_iam_role" "role" {
  name = "role-rename"
  ...
}

3. Apply the configuration

Expected Behavior

The lambda function + IAM role, policy and attachment are destroyed and recreated, and the existing lambda event source mapping is updated to the new lambda function.

Actual Behavior

Error: error updating Lambda Event Source Mapping (742a8399-979c-49d6-b4ad-b75d4443d5c4): InvalidParameterValueException: The provided execution role does not have permissions to call ReceiveMessage on SQS
{
  RespMetadata: {
    StatusCode: 400,
    RequestID: "cf39b3b5-407e-4e56-9f5b-1e8d08250068"
  },
  Message_: "The provided execution role does not have permissions to call ReceiveMessage on SQS",
  Type: "User"
}

  on main.tf line 7, in resource "aws_lambda_event_source_mapping" "mapping":
   7: resource "aws_lambda_event_source_mapping" "mapping" {

Important Factoids

When creating/updating a lambda event source mapping, AWS responds with an error if the lambda function does not have the necessary permissions. When creating a new lambda event source mapping, the AWS provider retries for up to 2 minutes as IAM policy changes can take some time to propagate. However, this retry does not occur when updating an existing lambda event source mapping. Re-running the configuration after a brief time completes successfully.

[github-actions]

This functionality has been released in v4.64.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.