Closed ghost closed 6 years ago
Being addressed in https://github.com/terraform-providers/terraform-provider-aws/pull/5509.
@bflad I think this can be closed as it's a duplicate of https://github.com/terraform-providers/terraform-provider-aws/issues/5482.
Thanks so much, @ewbankkit! This functionality was released in version 1.42.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
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!
This issue was originally opened by @whume as hashicorp/terraform#18701. It was migrated here as a result of the provider split. The original body of the issue is below.
Current Terraform Version
Use-cases
Attempted Solutions
This functionality would allow users to dump data directly to S3 instead of a cloudwatch log group. https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs-s3.html \ Currently for centralized logging we create cloud watch destination then use a subscription filter on the cloudwatch log group created by vpc flow logs to send the data to a kinesis stream in another aws account. This would allow us to dump logs directly to s3 then use a bucket policy to provision access.
Proposal
Add feature to support AWS new feature https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs-s3.html
References