DNXLabs/kinesis-stream-es/aws: Required to set Lambda Processor? #5
Description
Contact Details (optional)
Description. What happened?
We are setting up a Kinesis FireHose stream to an existing OpenSearch domain using Terraform.
We found your module and have been trying to implement it as shown below.
We do NOT need to process the data with a Lambda. The data is pre-formatted and we just want to feed the data in to OpenSearch as efficiently as possible. However, it seems that the module requires there to be a Lambda connected to the stream, which will likely be expensive for us. Is there a way NOT to implement the Lambda?
module "kinesis-stream_PUT-Status" {
source = "DNXLabs/kinesis-stream-es/aws"
version = "0.4.3"
vpc_id = data.aws_vpc.cm_vpc.id
private_subnet_ids = [data.aws_subnet.subnet_a.id, data.aws_subnet.subnet_b.id]
elasticsearch_name = data.aws_opensearch_domain.log_server.domain_name
kinesis_firehose_name = "PUT-Status"
kinesis_firehose_enabled = true
kinesis_firehose_index_name = "status"
kinesis_firehose_index_rotation_period = "OneWeek"
firehose_lambda_processor_name = "" # We tried using empty string or using null
kinesis_stream_bucket_name = data.aws_s3_bucket.open_search_bucket.id
}
Steps to reproduce
Terraform code is listed above
Expected behavior
The lambda processor should not be created or attached to the stream
Actual behavior
A processing lambda is created regardless or an error is thrown
Occurrence
Frequently
Relevant log output
Every time when we run `terraform plan`Code of Conduct
- I agree to follow this project's Code of Conduct