You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
locked and limited conversation to collaborators
Apr 2, 2020
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: