Add DLQ for Lambda

[phas13]

Describe the Feature

Add Dead Letter Queue configuration for lambda

Expected Behavior

If i add DLQ for Lambda function, we have it configured. We can create SQL for DLQ of provide SQS ARN via dead_letter_config section. Any solution will suite.

Use Case

To be able to pass SOC2/CIS compliance, we need to have DLQ for all lambdas. Even if we do not use it, better to have the ability to set it up or not, using some flag, like enable_dlq.

Currently, we have to find a workaround for that that does not look natural.

Describe Ideal Solution

• add option enable_dlq = true/false
• add dead_letter_config section to setup configuration if enable_dlq = true

Alternatives Considered

No response

Additional Context

No response

[nitrocode]

For the 3 lambdas like this one

terraform-aws-datadog-lambda-forwarder/lambda-log.tf

Line 80 in baab038

resource "aws_lambda_function" "forwarder_log" {

A dead_letter_config block could be added easily. This way the queue could be created outside of the module and passed in.

All we'd need an input to would be https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lambda_function#target_arn

A future option is to use the upstream lambda module instead of the raw resource and expose the same input as above.

https://github.com/cloudposse/terraform-aws-lambda-function/blob/69f2069149da07c7e40837fb53729759d5988dc6/main.tf#L43