| Table of Contents | ||||
|---|---|---|---|---|
|
...
Valid tags and data tables
The full tag can have 4 to 6 levels. The first two are fixed as cloud.aws. The third level identifies the type of events sent, and the fourth, fifth and sixth levels indicate the event subtype.
Technology | Brand | Type | Subtype 1 | Subtype 2 | Subtype 3 |
|---|---|---|---|---|---|
cloud | aws | waf | logs | <accountId> | <region> |
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
|---|---|
cloud.aws.waf.logs.<accountId>.<region> | cloud.aws.waf.logs |
How is the data sent to Devo?
Logs generated by AWS WAF service can be sent to AWS CloudWatch Logs, S3, and Kinesis Data Firehose services.
The preferred methods are using the first two services as destinations. In these cases, Devo AWS collector can be used for gathering, properly tagging, and securely forwarding these logs to Devo.
Logs sent to Kinesis Data Firehose can be properly tagged using an AWS Lambda function and forwarded to a Devo HTTP(s) endpoint (as an alternative, a Devo Relay deployed in an EC2 instance can be used for tagging and securely forwarding events using Syslog protocol).