aws-vpc-flow-log-appender icon indicating copy to clipboard operation
aws-vpc-flow-log-appender copied to clipboard

Sample code to append additional information (e.g. Security Group IDs and geolocation data) to VPC Flow Logs for analysis in Elasticsearch.

Results 7 aws-vpc-flow-log-appender issues
Sort by recently updated
recently updated
newest added

The Ingestion Lambda function is still built on nodejs6.10 which Lambda no longer supports.

When working with larger networks the decorator fails due to the response "body size is too long" (response over 6MB). I've observed this when decorating 11K + items

When i am streaming from firehose i call the function it says error. this is what i see in the logs.  23:04:08 START RequestId: 867b3d2a-12a4-11e8-bf8e-1928728ff215 Version: $LATEST START RequestId:...

I did troubleshooting the issues, but here is the error and logs not flowing to ElasticSearch... Finished building ENI to Security Group Mappig and Extracting Records Decorating 633 records No...

I have installed the per-requesites... below is the error when packaging the source code. Traceback (most recent call last): File "D:\Users\ABC\AppData\Roaming\Python\Scripts\sam-script.py", line 11, in load_entry_point('aws-sam-cli==0.6.0', 'console_scripts', 'sam')() File "c:\python27\lib\site-packages\click\core.py", line...

Kudos to the team/project. Its really useful. This currently works for only one region. And to monitor multiple region logs having multiple setup would be difficult. Instead can we have...

First of all i'm using this entire setup to monitor AWS vpc flow logs and its easy to use ES for some data insights. We use AWS ES and everything...