Terraform-provider-aws: Error creating Lambda function: ResourceConflictException: Function already exist

[hashibot]

_This issue was originally opened by @14mar1983 as hashicorp/terraform#15929. It was migrated here as a result of the provider split. The original body of the issue is below._

---

I am facing below error, how to avoid already created lambda functions by terraform.pl suggest.

Error applying plan:

3 error(s) occurred:

* aws_lambda_function._airflow_request: 1 error(s) occurred:

* aws_lambda_function._airflow_request: Error creating Lambda function: ResourceConflictException: Function already exist: _airflow_request
    status code: 409, request id: 76db4773-8a23-11e7-87a8-6ff908dd6661
* aws_lambda_function._get_config_dict: 1 error(s) occurred:

* aws_lambda_function._get_config_dict: Error creating Lambda function: **ResourceConflictException**: Function already exist: _get_config_dict
    status code: 409, request id: 76e4485d-8a23-11e7-b757-b30b03a1361b
* aws_lambda_function._em7_message_check_file_system: 1 error(s) occurred:

* aws_lambda_function._em7_message_check_file_system: Error creating Lambda function: ResourceConflictException: Function already exist: _em7_message_check_file_system
    status code: 409, request id: 76e8401a-8a23-11e7-9a25-f11e0f8c287c

[Ninir]

Hi @14mar1983

Thanks for reporting this. Could you provide your configuration?

Also, are you sure that your functions are not already part of you AWS account? to confirm, can you connect to the AWS console & check in the Lambda Service please?

Thanks!

[Ninir]

Hey @14mar1983

To do so, first import the lambda function, and then, with your already existing terraform code, you should be able to manage it.

Tell us how it goes!

[Ninir]

It was already created that's what the exception is saying, how to deal
with already created lambda role and lambda function.

I think that the import stuff I provided is the answer to this question. Terraform already gives you the way to import & know the background error, if any.

If already created skip and do not fail the running build. can we check using paramter?

As the core would need to be updated to handle this schema option this is not something achievable at the moment sadly.

Is the import answering your initial problem? Please tell me more if there is anything I could help on.

[lucas-rudd]

Did this get resolved? I'm having a similar issue. I'm attempting to add permissions to my lambda (the permissions already exist) and I am getting the same exception as @14mar1983. How am I supposed to handle this situation?

Here is some context:

```
resource "aws_lambda_permission" "lambda_connect_permission_stable" {
statement_id = "AllowExecutionFromAmazonConnect-Stable"
action = "lambda:InvokeFunction"
function_name = "${var.function_name}"
principal = "connect.amazonaws.com"
source_account = "${var.connect_account}"
source_arn = "${var.connect_instance_arn}"
qualifier = "stable"
}

[bnolan]

Having this same problem:

* aws_lambda_permission.allow_cloudwatch2: [WARN] Error adding new Lambda Permission for arn:aws:lambda:ap-southeast-2:693844451913:function:job_injector, retrying: ResourceConflictException: The statement id (AllowExecutionFromCloudWatch2) provided already exists. Please provide a new statement id, or remove the existing statement.

[lucas-rudd]

@bnolan I believe what we did was remove the lambda entirely and then rebuilt allowing terraform to manage the permission. We either that or we went into our terraform state file and edited it manually to include the Permission, I can't quite remember.

[koooge]

I might get the same issue. Terraform could not add two triggers(cloudwatch event) to lambda function. Am I wrong?

resource "aws_lambda_permission" "foo" {
  statement_id  = "AllowExecutionFromCloudWatch"
  action = "lambda:InvokeFunction"
  function_name = "<arn>"
  principal = "events.amazonaws.com"
  source_arn = "foo"
}

resource "aws_lambda_permission" "bar" {
  statement_id  = "AllowExecutionFromCloudWatch"
  action = "lambda:InvokeFunction"
  function_name = "<arn>"
  principal = "events.amazonaws.com"
  source_arn = "bar"
}

* aws_lambda_permission.bar: Error adding new Lambda Permission for <arn>, retrying: ResourceConflictException: The statement id (AllowExecutionFromCloudWatch) provided already exists. Please provide a new statement id, or remove the existing statement.
    status code: 409, request id: <id>

$ tf version
Terraform v0.11.8
+ provider.aws v1.39.0

[eXist-FraGGer]

Just use unique statement_id.

[bflad]

The original post about aws_lambda_function should be resolvable by using terraform import as mentioned previously. The newer posts about aws_lambda_permission should be resolvable by using a unique statement_id in each aws_lambda_permission.

If you have any lingering issues with either, please create a new bug report, filling out all the relevant details from the issue template. 👍

[hashibot[bot]]

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!