Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add send VPC flow logs to S3 AWS Provider #18701

Closed
whume opened this issue Aug 17, 2018 · 2 comments
Closed

Add send VPC flow logs to S3 AWS Provider #18701

whume opened this issue Aug 17, 2018 · 2 comments

Comments

@whume
Copy link

whume commented Aug 17, 2018

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

@ghost
Copy link

ghost commented Aug 18, 2018

This issue has been automatically migrated to hashicorp/terraform-provider-aws#5600 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#5600.

@ghost
Copy link

ghost commented Apr 2, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants