Update: This is done in aws package version 1.10.0 and promoted to production. Kibana version limitation is: >=.15.0 or >= 8.0.0.
In aws package, we have several data streams that collect logs from AWS services. These data streams are currently only supporting aws-s3 input. This issue is to add support for aws-cloudwatch input so users can decide if they want service logs to send to S3 bucket w/o SQS notification setup or simply send them to a CloudWatch log group.
I want to summarize all the log data streams we have in AWS package here with the supported inputs:
| Data Stream Names |
aws-s3 input |
aws-cloudwatch input |
httpjson input |
| cloudtrail |
Y |
Y(enabled: false) |
Y(enabled: false) |
| cloudwatch_logs |
Y(enabled: false) |
Y |
N |
| ec2_logs |
Y(enabled: false) |
Y |
N |
| elb_logs |
Y |
Y(enabled: false) |
N |
| s3access |
Y |
N |
N |
| vpcflow |
Y(enabled: false) |
Y |
N |
| WAF |
Y |
Y(enabled: false) |
N |
| Network Firewall |
Y |
Y(enabled: false) |
N |
Note: (enabled: false) means in Kibana when adding the integration, this option/toggle is not enabled by default.
Update: This is done in aws package version 1.10.0 and promoted to production. Kibana version limitation is: >=.15.0 or >= 8.0.0.
In
awspackage, we have several data streams that collect logs from AWS services. These data streams are currently only supportingaws-s3input. This issue is to add support foraws-cloudwatchinput so users can decide if they want service logs to send to S3 bucket w/o SQS notification setup or simply send them to a CloudWatch log group.I want to summarize all the log data streams we have in AWS package here with the supported inputs:
Note: (enabled: false) means in Kibana when adding the integration, this option/toggle is not enabled by default.