Table of Contents | ||||
---|---|---|---|---|
|
...
Valid tags and data tables
The full tag must have 3 levels. The first two are fixed as vpc.aws. The third level identifies the type of events sent.
Technology | Brand | Type |
---|---|---|
vpc | awswas | flow |
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
---|---|
vpc.aws.flow | vpc.aws.flow |
Log samples
The following are sample logs sent to each of the vpc.aws.flow data tables. Also, find how the information will be parsed in your data table under each sample log.
Note | ||
---|---|---|
| ||
Fields marked as Extra in the table below are not shown by default in data tables and need to be explicitly requested in the query. You can find them marked as Extra when you perform a query so they can be easily identified. Learn more about this in Selecting unrevealed columns. |
vpc.aws.flow
Code Block |
---|
2022-02-16 18:39:45.924 localhost=127.0.0.1 vpc.aws.flow: 5 027962030681 eni-03f1873c6id 10.2.3.9 11.2.3.9 31302 4443 6 1 44 1615436649 1615436669 REJECT OK vpc-0f5e2id subnet-0e1f0bid - 2 IPv4 10.2.3.9 11.2.3.9 us-east-1 use1-az2 - - - - ingress - |
...
Field | Value | Type | Source field name | Extra fields |
---|---|---|---|---|
eventdate |
|
| ||
version |
|
| ||
accountId |
|
| ||
interface_id |
|
| ||
srcaddr |
|
| ||
dstaddr |
|
| ||
srcport |
|
| ||
dstport |
|
| ||
protocol |
|
| ||
packets |
|
| ||
bytes |
|
| ||
start_date |
|
| ||
end_date |
|
| ||
action |
|
| ||
log_status |
|
| ||
vpc_id |
|
| ||
subnet_id |
|
| ||
instance_id |
|
| ||
tcp_flags |
|
| ||
type |
|
| ||
pkt_srcaddr |
|
| ||
pkt_dstaddr |
|
| ||
region |
|
| ||
az_id |
|
| ||
sublocation_type |
|
| ||
sublocation_id |
|
| ||
pkt_src_aws_service |
|
| ||
pkt_dst_aws_service |
|
| ||
flow_direction |
|
| ||
traffic_path |
|
| ||
rawMessage |
|
| rawSource | ✓ |
hostchain |
|
| ✓ | |
tag |
|
| ✓ |