-
Notifications
You must be signed in to change notification settings - Fork 4k
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
FlowLog: add support for log_format
parameter
#19316
Comments
@charbyzard we currently have an open PR to implement this functionality. |
@charbyzard I won't have time to work on #16279 for a while so don't hesitate if you want to contribute |
Yes, I will continue to work on this. |
refer to #16279 and #16279 (comment). The difference is below - I don't think you need custom for `LogFormatField`. "custom" in the document below does not mean that the user can specify any Key. It means that you can specify any Key of "Available fields" with a space-separated string. https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-logs-fields fixes #19316 ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Description
It would be nice if passing a value for the VPC FlowLog
logFormat
parameter was exposed through the higher-level FlowLog construct. Currently, the only way to use this feature seems to be through the lower level CfnFlowLog construct.It seems like the L2 construct for FlowLogs was introduced before this feature came out and simply never got updated.
Use Case
The current default is to use log only the values defined in the
v2
specification, which excludes a lot of useful information (such as thetcp_flags
parameter, which indicates if a given packet wasSYN/ACK/SYN-ACK/RST/FIN
). The only way to specify a custom log format that includes desirable information is to use the lower level CloudFormation wrapper construct, which is more cumbersome to work with.Proposed Solution
Update the FlowLog module to support the
logFormat
property.Other information
Reference documentation: Logging IP traffic with VPC Flow Logs
Acknowledge
The text was updated successfully, but these errors were encountered: