Closed umpa385 closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @umpa385 👋 Thank you for taking the time to raise this! I've opened PR #28964 to address this.
This functionality has been released in v4.51.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!
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.
Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/flow_log
Description
On this page here https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/flow_log
for the section below the log destination should be a kinesis delivery stream for direct put or a data stream for the arn, and not a cloudwatch log group arn.
[Amazon Kinesis Data Firehose logging](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/flow_log#amazon-kinesis-data-firehose-logging) resource "aws_flow_log" "example" { iam_role_arn = aws_iam_role.example.arn log_destination = aws_cloudwatch_log_group.example.arn
References
No response
Would you like to implement a fix?
None