You are viewing docs on Elastic's new documentation system, currently in technical preview. For all other Elastic docs, visit elastic.co/guide.

Amazon VPC

Collect Amazon VPC flow logs with Elastic Agent

What is an Elastic integration?
Version
2.14.2 (View all)
Compatible Kibana version(s)
8.12.0 or higher
Supported Serverless project types

What's this?
Security
Observability
Subscription level
What's this?
Basic

The AWS VPC Flow integration allows you to monitor Amazon Virtual Private Cloud (Amazon VPC) flow logs. Flow logs capture information about the IP traffic going to and from network interfaces in a VPC.

Use the AWS VPC Flow integration to collect logs related to your Amazon VPCs. Then visualize that data in Kibana, create alerts to notify you if something goes wrong, and reference logs when troubleshooting an issue.

For example, you could use this data to:

  • Diagnose overly restrictive security group rules
  • Monitor the traffic that is reaching your instance
  • Determine the direction of the traffic to and from the network interfaces

Then you can alert the relevant project manager about those events by email.

IMPORTANT: Extra AWS charges on AWS API requests will be generated by this integration. Please refer to the AWS integration for more details.

Data streams

The AWS VPC Flow integration collects one type of data: logs.

Logs help you keep a record of events happening in your VPCs. Logs collected by the vpcflow integration include the packet-level (original) source and destination IP addresses for the traffic, accepted traffic, rejected traffic, and more. See more details in the Logs reference.

Requirements

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Before using any AWS integration you will need:

  • AWS Credentials to connect with your AWS account.
  • AWS Permissions to make sure the user you're using to connect has permission to share the relevant data.

For more details about these requirements, please take a look at the AWS integration documentation.

Setup

Use this integration if you only need to collect IP traffic data for your VPCs.

If you want to collect data from two or more AWS services, consider using the AWS integration. When you configure the AWS integration, you can collect data from as many AWS services as you'd like.

For step-by-step instructions on how to set up an integration, see the Getting started guide.

For more information on implementation, see the Amazon documentation on:

This integration supports various plain text VPC flow log formats:

  • The default pattern of 14 version 2 fields
  • A custom pattern including all 29 fields, version 2 though 5:
${version} ${account-id} ${interface-id} ${srcaddr} ${dstaddr} ${srcport} ${dstport} ${protocol} ${packets} ${bytes} ${start} ${end} ${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}

Advanced options

CloudWatch

The CloudWatch logs input has several advanced options to fit specific use cases.

Latency

AWS CloudWatch Logs sometimes takes extra time to make the latest logs available to clients like the Agent.

The CloudWatch integration offers the latency setting to address this scenario. Latency translates the query's time range to consider the CloudWatch Logs latency. For example, a 5m latency means the integration will query CloudWatch for logs available 5 minutes ago.

Number of workers

If you are collecting log events from multiple log groups using log_group_name_prefix, you should review the value of the number_of_workers.

The number_of_workers setting defines the number of workers assigned to reading from log groups. Each log group matching the log_group_name_prefix requires a worker to keep log ingestion as close to real-time as possible. For example, if log_group_name_prefix matches five log groups, then number_of_workers should be set to 5. The default value is 1.

Logs reference

Note: The Parquet format is not supported.

Exported fields

FieldDescriptionType
@timestamp
Event timestamp.
date
aws.s3.bucket.arn
ARN of the S3 bucket that this log retrieved from.
keyword
aws.s3.bucket.name
Name of a S3 bucket.
keyword
aws.s3.metadata
AWS S3 object metadata values.
flattened
aws.s3.object.key
Name of the S3 object that this log retrieved from.
keyword
aws.vpcflow.account_id
The AWS account ID for the flow log.
keyword
aws.vpcflow.action
The action that is associated with the traffic, ACCEPT or REJECT.
keyword
aws.vpcflow.instance_id
The ID of the instance that's associated with network interface for which the traffic is recorded, if the instance is owned by you.
keyword
aws.vpcflow.interface_id
The ID of the network interface for which the traffic is recorded.
keyword
aws.vpcflow.log_status
The logging status of the flow log, OK, NODATA or SKIPDATA.
keyword
aws.vpcflow.pkt_dst_service
The name of the subset of IP address ranges for the pkt-dstaddr field, if the source IP address is for an AWS service.
keyword
aws.vpcflow.pkt_dstaddr
The packet-level (original) destination IP address for the traffic.
ip
aws.vpcflow.pkt_src_service
The name of the subset of IP address ranges for the pkt-srcaddr field, if the source IP address is for an AWS service.
keyword
aws.vpcflow.pkt_srcaddr
The packet-level (original) source IP address of the traffic.
ip
aws.vpcflow.sublocation.id
The ID of the sublocation that contains the network interface for which traffic is recorded. If the traffic is not from a sublocation, the field is removed.
keyword
aws.vpcflow.sublocation.type
The type of sublocation that's returned in the sublocation-id field. The possible values are: wavelength
outpost
aws.vpcflow.subnet_id
The ID of the subnet that contains the network interface for which the traffic is recorded.
keyword
aws.vpcflow.tcp_flags
The bitmask value for the following TCP flags: 2=SYN,18=SYN-ACK,1=FIN,4=RST
keyword
aws.vpcflow.tcp_flags_array
List of TCP flags: 'fin, syn, rst, psh, ack, urg'
keyword
aws.vpcflow.traffic_path
The path that egress traffic takes to the destination. To determine whether the traffic is egress traffic, check the network.direction field. The possible values can be found here. If none of the values apply, the field is set to -.
keyword
aws.vpcflow.type
The type of traffic: IPv4, IPv6, or EFA.
keyword
aws.vpcflow.version
The VPC Flow Logs version. If you use the default format, the version is 2. If you specify a custom format, the version is 3.
keyword
aws.vpcflow.vpc_id
The ID of the VPC that contains the network interface for which the traffic is recorded.
keyword
cloud.account.id
The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.
keyword
cloud.availability_zone
Availability zone in which this host, resource, or service is located.
keyword
cloud.image.id
Image ID for the cloud instance.
keyword
cloud.instance.id
Instance ID of the host machine.
keyword
cloud.instance.name
Instance name of the host machine.
keyword
cloud.machine.type
Machine type of the host machine.
keyword
cloud.project.id
The cloud project identifier. Examples: Google Cloud Project id, Azure Project id.
keyword
cloud.provider
Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.
keyword
cloud.region
Region in which this host, resource, or service is located.
keyword
container.id
Unique container id.
keyword
container.image.name
Name of the image the container was built on.
keyword
container.labels
Image labels.
object
container.name
Container name.
keyword
data_stream.dataset
Data stream dataset.
constant_keyword
data_stream.namespace
Data stream namespace.
constant_keyword
data_stream.type
Data stream type.
constant_keyword
destination.address
Some event destination addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the .address field. Then it should be duplicated to .ip or .domain, depending on which one it is.
keyword
destination.as.number
Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.
long
destination.as.organization.name
Organization name.
keyword
destination.as.organization.name.text
Multi-field of destination.as.organization.name.
match_only_text
destination.geo.city_name
City name.
keyword
destination.geo.continent_name
Name of the continent.
keyword
destination.geo.country_iso_code
Country ISO code.
keyword
destination.geo.country_name
Country name.
keyword
destination.geo.location
Longitude and latitude.
geo_point
destination.geo.region_iso_code
Region ISO code.
keyword
destination.geo.region_name
Region name.
keyword
destination.ip
IP address of the destination (IPv4 or IPv6).
ip
destination.port
Port of the destination.
long
ecs.version
ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events.
keyword
error.message
Error message.
match_only_text
event.category
This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories.
keyword
event.dataset
Name of the dataset. If an event source publishes more than one type of log or events (e.g. access log, error log), the dataset is used to specify which one the event comes from. It's recommended but not required to start the dataset name with the module name, followed by a dot, then the dataset name.
constant_keyword
event.end
event.end contains the date when the event ended or when the activity was last observed.
date
event.kind
This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not.
keyword
event.module
Event module
constant_keyword
event.original
Raw text message of entire event. Used to demonstrate log integrity or where the full log message (before splitting it up in multiple parts) may be required, e.g. for reindex. This field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from _source. If users wish to override this and index this field, please see Field data types in the Elasticsearch Reference.
keyword
event.outcome
This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy. event.outcome simply denotes whether the event represents a success or a failure from the perspective of the entity that produced the event. Note that when a single transaction is described in multiple events, each event may populate different values of event.outcome, according to their perspective. Also note that in the case of a compound event (a single event that contains multiple logical events), this field should be populated with the value that best captures the overall success or failure from the perspective of the event producer. Further note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with event.type:info, or any events for which an outcome does not make logical sense.
keyword
event.start
event.start contains the date when the event started or when the activity was first observed.
date
event.type
This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types.
keyword
host.architecture
Operating system architecture.
keyword
host.containerized
If the host is a container.
boolean
host.domain
Name of the domain of which the host is a member. For example, on Windows this could be the host's Active Directory domain or NetBIOS domain name. For Linux this could be the domain of the host's LDAP provider.
keyword
host.hostname
Hostname of the host. It normally contains what the hostname command returns on the host machine.
keyword
host.id
Unique host id. As hostname is not always unique, use values that are meaningful in your environment. Example: The current usage of beat.name.
keyword
host.ip
Host ip addresses.
ip
host.mac
Host MAC addresses. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.
keyword
host.name
Name of the host. It can contain what hostname returns on Unix systems, the fully qualified domain name (FQDN), or a name specified by the user. The recommended value is the lowercase FQDN of the host.
keyword
host.os.build
OS build information.
keyword
host.os.codename
OS codename, if any.
keyword
host.os.family
OS family (such as redhat, debian, freebsd, windows).
keyword
host.os.kernel
Operating system kernel version as a raw string.
keyword
host.os.name
Operating system name, without the version.
keyword
host.os.name.text
Multi-field of host.os.name.
match_only_text
host.os.platform
Operating system platform (such centos, ubuntu, windows).
keyword
host.os.version
Operating system version as a raw string.
keyword
host.type
Type of host. For Cloud providers this can be the machine type like t2.medium. If vm, this could be the container, for example, or other information meaningful in your environment.
keyword
input.type
Input type
keyword
log.file.path
Full path to the log file this event came from, including the file name. It should include the drive letter, when appropriate. If the event wasn't read from a log file, do not populate this field.
keyword
log.offset
Log offset
long
network.bytes
Total bytes transferred in both directions. If source.bytes and destination.bytes are known, network.bytes is their sum.
long
network.community_id
A hash of source and destination IPs and ports, as well as the protocol used in a communication. This is a tool-agnostic standard to identify flows. Learn more at https://github.com/corelight/community-id-spec.
keyword
network.direction
Direction of the network traffic. When mapping events from a host-based monitoring context, populate this field from the host's point of view, using the values "ingress" or "egress". When mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of the network perimeter, using the values "inbound", "outbound", "internal" or "external". Note that "internal" is not crossing perimeter boundaries, and is meant to describe communication between two hosts within the perimeter. Note also that "external" is meant to describe traffic between two hosts that are external to the perimeter. This could for example be useful for ISPs or VPN service providers.
keyword
network.iana_number
IANA Protocol Number (https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). Standardized list of protocols. This aligns well with NetFlow and sFlow related logs which use the IANA Protocol Number.
keyword
network.packets
Total packets transferred in both directions. If source.packets and destination.packets are known, network.packets is their sum.
long
network.transport
Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.) The field value must be normalized to lowercase for querying.
keyword
network.type
In the OSI Model this would be the Network Layer. ipv4, ipv6, ipsec, pim, etc The field value must be normalized to lowercase for querying.
keyword
related.ip
All of the IPs seen on your event.
ip
source.address
Some event source addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the .address field. Then it should be duplicated to .ip or .domain, depending on which one it is.
keyword
source.as.number
Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.
long
source.as.organization.name
Organization name.
keyword
source.as.organization.name.text
Multi-field of source.as.organization.name.
match_only_text
source.bytes
Bytes sent from the source to the destination.
long
source.geo.city_name
City name.
keyword
source.geo.continent_name
Name of the continent.
keyword
source.geo.country_iso_code
Country ISO code.
keyword
source.geo.country_name
Country name.
keyword
source.geo.location
Longitude and latitude.
geo_point
source.geo.region_iso_code
Region ISO code.
keyword
source.geo.region_name
Region name.
keyword
source.ip
IP address of the source (IPv4 or IPv6).
ip
source.packets
Packets sent from the source to the destination.
long
source.port
Port of the source.
long
tags
List of keywords used to tag each event.
keyword

An example event for vpcflow looks as following:

{
    "@timestamp": "2014-12-14T04:07:50.000Z",
    "agent": {
        "ephemeral_id": "1ffa6099-2893-4e54-8f41-e84bf2244161",
        "id": "acba78ef-1401-4689-977c-d8c2e5d6a8fa",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.10.1"
    },
    "aws": {
        "s3": {
            "bucket": {
                "arn": "arn:aws:s3:::elastic-package-aws-bucket-63461",
                "name": "elastic-package-aws-bucket-63461"
            },
            "object": {
                "key": "extra-samples.log"
            }
        },
        "vpcflow": {
            "account_id": "123456789010",
            "action": "ACCEPT",
            "interface_id": "eni-1235b8ca123456789",
            "log_status": "OK",
            "version": "2"
        }
    },
    "cloud": {
        "account": {
            "id": "123456789010"
        },
        "provider": "aws",
        "region": "us-east-1"
    },
    "data_stream": {
        "dataset": "aws.vpcflow",
        "namespace": "ep",
        "type": "logs"
    },
    "destination": {
        "address": "89.160.20.156",
        "as": {
            "number": 29518,
            "organization": {
                "name": "Bredband2 AB"
            }
        },
        "geo": {
            "city_name": "Linköping",
            "continent_name": "Europe",
            "country_iso_code": "SE",
            "country_name": "Sweden",
            "location": {
                "lat": 58.4167,
                "lon": 15.6167
            },
            "region_iso_code": "SE-E",
            "region_name": "Östergötland County"
        },
        "ip": "89.160.20.156",
        "port": 22
    },
    "ecs": {
        "version": "8.0.0"
    },
    "elastic_agent": {
        "id": "acba78ef-1401-4689-977c-d8c2e5d6a8fa",
        "snapshot": false,
        "version": "8.10.1"
    },
    "event": {
        "agent_id_status": "verified",
        "category": [
            "network"
        ],
        "dataset": "aws.vpcflow",
        "end": "2014-12-14T04:07:50.000Z",
        "ingested": "2023-11-07T14:31:30Z",
        "kind": "event",
        "original": "2 123456789010 eni-1235b8ca123456789 89.160.20.156 89.160.20.156 20641 22 6 20 4249 1418530010 1418530070 ACCEPT OK",
        "outcome": "success",
        "start": "2014-12-14T04:06:50.000Z",
        "type": [
            "connection"
        ]
    },
    "input": {
        "type": "aws-s3"
    },
    "log": {
        "file": {
            "path": "https://elastic-package-aws-bucket-63461.s3.us-east-1.amazonaws.com/extra-samples.log"
        },
        "offset": 338
    },
    "network": {
        "bytes": 4249,
        "community_id": "1:CEGBlG6oEeW2Y5LLdr9GONITz00=",
        "iana_number": "6",
        "packets": 20,
        "transport": "tcp",
        "type": "ipv4"
    },
    "related": {
        "ip": [
            "89.160.20.156",
            "89.160.20.156"
        ]
    },
    "source": {
        "address": "89.160.20.156",
        "as": {
            "number": 29518,
            "organization": {
                "name": "Bredband2 AB"
            }
        },
        "bytes": 4249,
        "geo": {
            "city_name": "Linköping",
            "continent_name": "Europe",
            "country_iso_code": "SE",
            "country_name": "Sweden",
            "location": {
                "lat": 58.4167,
                "lon": 15.6167
            },
            "region_iso_code": "SE-E",
            "region_name": "Östergötland County"
        },
        "ip": "89.160.20.156",
        "packets": 20,
        "port": 20641
    },
    "tags": [
        "preserve_original_event",
        "forwarded",
        "aws-vpcflow"
    ]
}

Changelog

VersionDetailsKibana version(s)

2.14.2

Bug fix View pull request
Update aggregation function for AWS lambda invocation metric.

8.12.0 or higher

2.14.1

Enhancement View pull request
Document billing data stream limitations.

8.12.0 or higher

2.14.0

Enhancement View pull request
Add ability to set processors and leader election on AWS Billing.

8.12.0 or higher

2.13.1

Enhancement View pull request
Update latency parameter description

8.12.0 or higher

2.13.0

Enhancement View pull request
Add Amazon MSK integration

8.12.0 or higher

2.12.2

Bug fix View pull request
Fix an issue were the "_id" field was being used to aggregate data in Severity Over Time dashboard.

8.12.0 or higher

2.12.1

Enhancement View pull request
Add cloudsecurity_cdr sub category label.

8.12.0 or higher

2.12.0

Enhancement View pull request
Enable 'secret' for the sensitive fields.

8.12.0 or higher

2.11.3

Bug fix View pull request
Fix query range calculation for GuardDuty datastream.

8.10.2 or higher

2.11.2

Bug fix View pull request
Remove hardcoded event.dataset field and use ecs instead.

8.10.2 or higher

2.11.1

Enhancement View pull request
Improve wording on milliseconds.

8.10.2 or higher

2.11.0

Enhancement View pull request
Convert Total Estimated Charges panel to new metric visualization.

8.10.2 or higher

2.10.2

Bug fix View pull request
Fix dimensions fingerprint field

8.10.2 or higher

2.10.1

Bug fix View pull request
Fix exclude_files pattern.

8.10.2 or higher

2.10.0

Enhancement View pull request
Convert "AWS Redshift metrics overview" visualizations to new metric.

8.10.2 or higher

2.9.1

Bug fix View pull request
Change SQS metrics statistic method, which includes changing ApproximateAgeOfOldestMessage from average to max, changing NumberOfMessagesDeleted, NumberOfEmptyReceives, NumberOfMessagesReceived and NumberOfMessagesSent from average to sum.

8.9.0 or higher

2.9.0

Enhancement View pull request
Limit request tracer log count to five.

8.9.0 or higher

2.8.6

Bug fix View pull request
Add missing fields from beats input

8.9.0 or higher

2.8.5

Enhancement View pull request
Update donut charts with pie for better representation

8.9.0 or higher

2.8.4

Bug fix View pull request
Remove unused aws..metrics..* and aws.s3.bucket.name

8.9.0 or higher

2.8.3

Bug fix View pull request
Include documentation and mappings for subfields of dns.answers

Bug fix View pull request
Fix mapping for tags and dynamic metric fields

8.9.0 or higher

2.8.2

Bug fix View pull request
Add null checks and ignore_missing checks to the rename processor

8.9.0 or higher

2.8.1

Bug fix View pull request
Fix incorrect billing metrics displayed under AWS Billing overview dashboard.

8.9.0 or higher

2.8.0

Enhancement View pull request
Allow configuration of TLD for guardduty, inspector, and security hub datastreams.

8.9.0 or higher

2.7.0

Enhancement View pull request
Add tags.yml file so that integration's dashboards and saved searches are tagged with "Security Solution" and displayed in the Security Solution UI.

Enhancement View pull request
Upgrade package spec to 3.0.0.

Bug fix View pull request
Fix duplicated and invalid field definitions.

Bug fix View pull request
Add missing dashboard filters.

8.9.0 or higher

2.6.1

Bug fix View pull request
Fix AWS API Gateway logs dashboard lens

8.9.0 or higher

2.6.0

Enhancement View pull request
ECS version updated to 8.10.0.

8.9.0 or higher

2.5.0

Enhancement View pull request
Update Cloudtrail datastream to support tlsDetails field

8.9.0 or higher

2.4.1

Bug fix View pull request
Fix Security Hub Findings to abide by ECS allowed values.

8.9.0 or higher

2.4.0

Bug fix View pull request
Add AWS API Gateway metrics dashboards for each API type and additional filters which ensure data consistency

8.9.0 or higher

2.3.0

Enhancement View pull request
Change include_linked_accounts default to true

8.9.0 or higher

2.2.1

Bug fix View pull request
Fix GuardDuty API call parameter.

8.9.0 or higher

2.2.0

Enhancement View pull request
Add AWS API Gateway metrics dashboard Stage filter, control groups and clean up

8.9.0 or higher

2.1.2

Bug fix View pull request
Fix AWS API Gateway metrics dashboard

8.9.0 or higher

2.1.1

Enhancement View pull request
Improve AWS API Gateway dashboard

8.9.0 or higher

2.1.0

Enhancement View pull request
Enable TSDB by default for EC2 metrics data stream. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.9.0 or higher

2.0.0

Enhancement View pull request
Remove deprecated option for "Cloudwatch via S3"from the AWS CloudWatch integration. If you are using it take note that logs WON'T BE ingested via this route anymore once you update.

8.9.0 or higher

1.53.5

Enhancement View pull request
Set metric type in EC2 data stream fields.

8.9.0 or higher

1.53.4

Enhancement View pull request
Add dimension fields to EC2 data stream.

8.9.0 or higher

1.53.3

Enhancement View pull request
Add missing fields definition for ec2

8.9.0 or higher

1.53.2

Bug fix View pull request
Remove the remove processor since rename processor removes old field already.

8.9.0 or higher

1.53.1

Enhancement View pull request
Disable TSDB on AWS Billing.

8.9.0 or higher

1.53.0

Enhancement View pull request
Add AWS API Gateway custom acccess logging fields.

8.9.0 or higher

1.52.1

Enhancement View pull request
Use default color for AWS dashboards metric charts.

8.9.0 or higher

1.52.0

Enhancement View pull request
Enable TSDB by default for cloudwatch metrics data stream. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.9.0 or higher

1.51.3

Bug fix View pull request
Remove hardcoded event.dataset field and use ecs instead.

8.8.1 or higher

1.51.2

Enhancement View pull request
Disable TSDB on AWS Billing.

8.8.1 or higher

1.51.1

Enhancement View pull request
Use object metric type for the cloudwatch metrics

8.8.1 or higher

1.51.0

Enhancement View pull request
Add standalone S3 option for vpcflow

8.8.1 or higher

1.50.6

Enhancement View pull request
Add metric_type metadata to the cloudwatch data_stream

8.8.1 or higher

1.50.5

Enhancement View pull request
Migrate AWS Security Hub dashboards to lens.

8.8.1 or higher

1.50.4

Enhancement View pull request
Migrate AWS VPC dashboard visualizations to lens.

8.8.1 or higher

1.50.3

Enhancement View pull request
Add EMR logs dashboard.

8.8.1 or higher

1.50.2

Enhancement View pull request
Migrate AWS Billing dashboard visualizations to lens.

8.8.1 or higher

1.50.1

Enhancement View pull request
Add AWS API Gateway logs dashboard.

8.8.1 or higher

1.50.0

Enhancement View pull request
Add EMR logs data stream.

8.8.1 or higher

1.49.0

Enhancement View pull request
Add API Gateway logs datastream

8.8.1 or higher

1.48.0

Enhancement View pull request
Adding missing fields for the CloudTrail datastream - add option for standalone S3 bucket

8.8.1 or higher

1.47.1

Enhancement View pull request
Migrate AWS Redshift dashboard input controls.

8.8.1 or higher

1.47.0

Enhancement View pull request
Migrate AWS S3 Server Access Log Overview dashboard visualizations to lens.

8.8.1 or higher

1.46.9

Enhancement View pull request
Migrate AWS Network Firewall dashboard input controls.

8.8.1 or higher

1.46.8

Enhancement View pull request
Add dimensions metadata to the cloudwatch data_stream

8.8.1 or higher

1.46.7

Enhancement View pull request
Enable time series data streams for the API Gateway and EMR data streams. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.8.1 or higher

1.46.6

Enhancement View pull request
Update metric type and set dimension fields for AWS EMR data stream.

8.8.1 or higher

1.46.5

Enhancement View pull request
Fix metric type for API Gateway metric fields.

8.8.1 or higher

1.46.4

Enhancement View pull request
Set dimensions fields for API Gateway data stream.

—

1.46.3

Enhancement View pull request
Add missing S3 fields for vpcflow

8.8.1 or higher

1.46.2

Enhancement View pull request
Enable time series data streams for the S3 daily storage and S3 request datasets. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.8.1 or higher

1.46.1

Enhancement View pull request
Enable time series data streams for the Usage dataset. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.8.1 or higher

1.46.0

Enhancement View pull request
Enable time series data streams for the metrics datasets Billing, DynamoDB, EBS, ECS, ELB, Firewall, Kinesis, Lambda, NAT gateway, RDS, Redshift, S3 Storage Lens, SNS, SQS, Transit Gateway and VPN. This improves storage usage and query performance. For more details, see https://www.elastic.co/guide/en/elasticsearch/reference/current/tsds.html.

8.8.1 or higher

1.45.9

Enhancement View pull request
Add new fingerprint dimension to AWS Billing.

8.8.1 or higher

1.45.8

Enhancement View pull request
Add metric_type metadata to s3_daily_storage and s3_request data streams.

8.8.1 or higher

1.45.7

Enhancement View pull request
Add dimension fields metadata to s3_request and s3_data_storage data streams to support TSDB

8.8.1 or higher

1.45.6

Enhancement View pull request
Add metric type to S3 Storage Lens.

8.8.1 or higher

1.45.4

Enhancement View pull request
Set dimension fields for S3 Storage Lens.

8.8.1 or higher

1.45.3

Bug fix View pull request
Remove aws.dimensions.* from package-fields.yml

8.8.1 or higher

1.45.2

Enhancement View pull request
Add AWS EMR metrics dashboard.

8.8.1 or higher

1.45.1

Enhancement View pull request
Add AWS API Gateway dashboard.

8.8.1 or higher

1.45.0

Enhancement View pull request
Add AWS EMR metrics data stream.

8.8.1 or higher

1.44.4

Enhancement View pull request
Migrate AWS Metric Overview dashboard visualizations to lens.

8.8.1 or higher

1.44.3

Enhancement View pull request
Migrate AWS ELB Access Log dashboard visualizations to lens.

8.8.1 or higher

1.44.2

Bug fix View pull request
Fix image link in readme

8.8.1 or higher

1.44.1

Enhancement View pull request
Migrate AWS TransitGateway metrics dashboard to lenses.

8.8.1 or higher

1.44.0

Enhancement View pull request
Add permissions to reroute events to logs-- for cloudwatch_logs and ec2_logs datastream.

8.8.1 or higher

1.43.2

Enhancement View pull request
Add documentation for latency parameter

8.8.1 or higher

1.43.1

Enhancement View pull request
Add tags_filter and include_linked_accounts config parameter in missing metric data streams.

8.8.1 or higher

1.43.0

Enhancement View pull request
Add include_linked_accounts config parameter for metrics data streams.

8.8.1 or higher

1.42.0

Enhancement View pull request
Add field agent.id to be set as dimension for TSDB migration.

8.7.1 or higher

1.41.0

Enhancement View pull request
Migrate AWS NATGateway metrics dashboard visualizations to lenses.

8.7.1 or higher

1.40.9

Enhancement View pull request
Migrate AWS ELB metrics dashboard visualizations to lenses.

8.7.1 or higher

1.40.8

Enhancement View pull request
Migrate EC2 metrics dashboard visualizations to lenses.

8.7.1 or higher

1.40.7

Enhancement View pull request
Add AWS Firewall metrics dashboard input control groups.

8.7.1 or higher

1.40.6

Enhancement View pull request
Migrate AWS S3 Storage Lens dashboard visualizations to lens.

8.7.1 or higher

1.40.5

Enhancement View pull request
Migrate Usage Overview dashboard to lenses.

8.7.1 or higher

1.40.4

Enhancement View pull request
Migrate AWS CloudTrail dashboard visualizations to lenses.

8.7.1 or higher

1.40.3

Enhancement View pull request
Add fields metric type to usage, dynamoDB and ELB data streams.

8.7.1 or higher

1.40.2

Enhancement View pull request
Replace aws.rds.db_instance.identifier with aws.dimensions.DBInstanceIdentifier in RDS dashboard.

8.7.1 or higher

1.40.1

Enhancement View pull request
Add link to main AWS requirements in all integrations page.

8.7.1 or higher

1.40.0

Enhancement View pull request
Add metric type to SNS, SQS and Billing data streams.

8.7.1 or higher

1.39.0

Enhancement View pull request
Add AWS API Gateway data stream.

8.7.1 or higher

1.38.4

Enhancement View pull request
Add dimension fields to billing, sns and sqs data streams.

8.7.1 or higher

1.38.3

Enhancement View pull request
Add dimension fields to firewall, transit gateway and vpn data streams.

8.7.1 or higher

1.38.2

Enhancement View pull request
Add metric type to vpn, firewall and transit gateway data streams.

8.7.1 or higher

1.38.1

Enhancement View pull request
Add metric type to RDS data stream.

8.7.1 or higher

1.38.0

Enhancement View pull request
Add dimensions to RDS data stream.

8.7.1 or higher

1.37.3

Bug fix View pull request
Fix incorrect fields on multiple visualizations.

8.7.1 or higher

1.37.2

Enhancement View pull request
Migrate AWS RDS metrics dashboard to lenses.

8.7.1 or higher

1.37.1

Enhancement View pull request
Migrate AWS SNS dashboard visualizations to lenses.

8.7.1 or higher

1.37.0

Enhancement View pull request
Migrate AWS SQS metrics dashboard visualizations to lenses.

8.7.1 or higher

1.36.9

Enhancement View pull request
Migrate AWS VPN metrics dashboard to lenses.

8.7.1 or higher

1.36.8

Enhancement View pull request
Add dimension fields to usage, dynamoDB and ELB data streams.

8.7.1 or higher

1.36.7

Enhancement View pull request
Add dimension fields to Lambda data stream for TSDB support.

8.7.1 or higher

1.36.6

Enhancement View pull request
Add metric type to natgateway data stream fields.

8.7.1 or higher

1.36.5

Enhancement View pull request
Add metric type to EBS fields.

8.7.1 or higher

1.36.4

Enhancement View pull request
Add support for TSDB on kinesis data stream (metric type).

8.7.1 or higher

1.36.3

Enhancement View pull request
Add dimensions to Redshift data stream.

8.7.1 or higher

1.36.2

Enhancement View pull request
Add metric type mapping to Redshift data stream.

8.7.1 or higher

1.36.1

Enhancement View pull request
Add dimension fields to natgateway data stream.

8.7.1 or higher

1.36.0

Enhancement View pull request
Add metric type to Lambda fields.

8.7.1 or higher

1.35.1

Bug fix View pull request
Fix typo in field name causing erroneous timestamp detection on the s3access data stream.

8.7.1 or higher

1.35.0

Enhancement View pull request
Add a new flag to enable request tracing on httpjson based input

8.7.1 or higher

1.34.5

Enhancement View pull request
Migrate AWS Lambda metrics dashboard visualizations to lenses.

8.6.0 or higher

1.34.4

Enhancement View pull request
Migrate AWS DynamoDB metrics dashboard visualizations to lenses.

8.6.0 or higher

1.34.3

Enhancement View pull request
Add field metric type to ECS data stream.

8.6.0 or higher

1.34.2

Enhancement View pull request
Add dimension fields to Kinesis datastream.

8.6.0 or higher

1.34.1

Enhancement View pull request
Add dimension fields to ECS datastream for TSDB support.

8.6.0 or higher

1.34.0

Enhancement View pull request
Add dimensions to EBS data stream.

8.6.0 or higher

1.33.3

Enhancement View pull request
Add number_of_workers and latency to all CloudWatch Logs based integrations.

8.6.0 or higher

1.33.2

Bug fix View pull request
Add missing permissions in the AWS Billing integration documentation.

8.6.0 or higher

1.33.1

Bug fix View pull request
Add missing permissions in the AWS CloudWatch Logs integration documentation.

8.6.0 or higher

1.33.0

Enhancement View pull request
Add latency configuration option on the CloudWatch Logs integration.

8.6.0 or higher

1.32.2

Bug fix View pull request
Fix a minor documentation format issue.

8.6.0 or higher

1.32.1

Enhancement View pull request
Added categories and/or subcategories.

8.6.0 or higher

1.32.0

Enhancement View pull request
Migrate AWS EBS dashboard visualizations to lenses.

8.6.0 or higher

1.31.0

Enhancement View pull request
Add a data stream for Amazon GuardDuty.

8.6.0 or higher

1.30.0

Enhancement View pull request
Add dashboards data streams filters.

8.6.0 or higher

1.29.1

Bug fix View pull request
Drop comments from CloudFront loglines

8.6.0 or higher

1.29.0

Enhancement View pull request
Add data_granularity parameter and rename period title to Collection Period.

8.6.0 or higher

1.28.3

Bug fix View pull request
Remove quotes from VPC flow log message field and move dot_expander processor to top

8.4.0 or higher

1.28.2

Bug fix View pull request
Add dot_expander processor to expand all fields with dot into object fields

Bug fix View pull request
Support VPC flow log with message field

8.4.0 or higher

1.28.1

Enhancement View pull request
Adjust kinesis integration to kinesis data stream

8.4.0 or higher

1.28.0

Enhancement View pull request
Enhance S3 integration dashboard

8.4.0 or higher

1.27.3

Bug fix View pull request
Support multiple forwarded IPs in cloudfront integration

8.4.0 or higher

1.27.2

Enhancement View pull request
Update the pagination termination condition.

8.4.0 or higher

1.27.1

Enhancement View pull request
Added a Summary Dashboard for AWS Security Hub.

8.4.0 or higher

1.27.0

Enhancement View pull request
Add Inspector data stream.

8.4.0 or higher

1.25.3

Bug fix View pull request
Remove duplicate fields from agent.yml and use ecs.yml for ECS fields

8.3.0 or higher

1.25.2

Bug fix View pull request
Update ec2 fields.yml doc

8.3.0 or higher

1.25.1

Bug fix View pull request
Remove duplicate 'content_type' config that causes errors while configurating the integration.

8.3.0 or higher

1.25.0

Enhancement View pull request
Force content type where json content is expected

8.3.0 or higher

1.24.6

Bug fix View pull request
Enhance Kinesis integration dashboard

8.3.0 or higher

1.24.5

Bug fix View pull request
Allow adding multiple processors in cloudfront logs.

8.3.0 or higher

1.24.4

Bug fix View pull request
Do not rely on dynamodb lightweight module metricset.

8.3.0 or higher

1.24.3

Bug fix View pull request
Fix adding processors in cloudfront logs.

8.3.0 or higher

1.24.2

Bug fix View pull request
Fix billing datastream agent template.

8.3.0 or higher

1.24.1

Bug fix View pull request
Fix aws.cloudtrail.request_id parsing

8.3.0 or higher

1.24.0

Bug fix View pull request
Expose Default Region setting to UI

8.3.0 or higher

1.23.4

Bug fix View pull request
Set default endpoint to empty string

8.3.0 or higher

1.23.3

Bug fix View pull request
Fix Billing Dashboard

8.3.0 or higher

1.23.2

Bug fix View pull request
Fix EC2 dashboard

8.3.0 or higher

1.23.1

Enhancement View pull request
Update all AWS documentation.

8.1.0 or higher

1.23.0

Bug fix View pull request
Fix file.path field in cloudtrail data stream to use json.digestS3Object

8.1.0 or higher

1.22.0

Enhancement View pull request
Update cloud.region parsing

8.1.0 or higher

1.21.0

Enhancement View pull request
Add Security Hub Findings and Insights data streams

8.1.0 or higher

1.20.0

Enhancement View pull request
Improve dashboards by removing individual visualizations from library

8.1.0 or higher

1.19.5

Enhancement View pull request
Move ebs metrics config from beats to integrations

7.15.0 or higher
8.0.0 or higher

1.19.4

Bug fix View pull request
Fix proxy URL documentation rendering.

7.15.0 or higher
8.0.0 or higher

1.19.3

Bug fix View pull request
Update sample_event.json in kinesis data stream

7.15.0 or higher
8.0.0 or higher

1.19.2

Enhancement View pull request
Move NATGateway metrics config from beats to integrations

7.15.0 or higher
8.0.0 or higher

1.19.1

Enhancement View pull request
Move Transit Gateway metrics config from beats to integrations

7.15.0 or higher
8.0.0 or higher

1.19.0

Enhancement View pull request
Add Kinesis metrics datastream

7.15.0 or higher
8.0.0 or higher

1.18.2

Enhancement View pull request
Move s3_request metrics config from beats to integrations

Enhancement View pull request
Move s3_daily_storage metrics config from beats to integrations

Enhancement View pull request
Move SQS metrics config from beats to integrations

Enhancement View pull request
Move SNS metrics config from beats to integrations

Enhancement View pull request
Move lambda metrics config from beats to integrations

7.15.0 or higher
8.0.0 or higher

1.18.1

Enhancement View pull request
Release AWS billing integration as GA

7.15.0 or higher
8.0.0 or higher

1.18.0

Enhancement View pull request
Add ECS metricset

Bug fix View pull request
Fix incorrect fields on multiple visualizations

7.15.0 or higher
8.0.0 or higher

1.17.5

Enhancement View pull request
Release Amazon Redshift integration as GA

7.15.0 or higher
8.0.0 or higher

1.17.4

Bug fix View pull request
Fix data_stream.dataset indentation on cloudwatch_logs integration

7.15.0 or higher
8.0.0 or higher

1.17.3

Bug fix View pull request
Add missing endpoint config to metrics datasets.

Enhancement View pull request
Move usage metrics config from beats to integrations

Enhancement View pull request
Move dynamodb metrics config from beats to integrations

7.15.0 or higher
8.0.0 or higher

1.17.2

Bug fix View pull request
Improve support for event.original field from upstream forwarders.

7.15.0 or higher
8.0.0 or higher

1.17.1

Bug fix View pull request
Fix misspelling of Log Stream Prefix variable in manifest for aws-cloudwatch input

7.15.0 or higher
8.0.0 or higher

1.17.0

Enhancement View pull request
Added Redshift integration

7.15.0 or higher
8.0.0 or higher

1.16.6

Enhancement View pull request
Update documentation with additional context for new users.

7.15.0 or higher
8.0.0 or higher

1.16.5

Enhancement View pull request
Move ELB metrics config from beats to integrations

—

1.16.4

Bug fix View pull request
Fix ELB dataset to parse URLs with spaces

Enhancement View pull request
Upgrade ECS to 8.2.0

7.15.0 or higher
8.0.0 or higher

1.16.3

Enhancement View pull request
Move RDS metrics config from beats to integrations

—

1.16.2

Enhancement View pull request
Move EC2 metrics config from beats to integrations

—

1.16.1

Bug fix View pull request
Fix invalid values for ECS fields in vpcflow

—

1.16.0

Enhancement View pull request
Move VPN configuration file into integrations and add tag collection

7.15.0 or higher
8.0.0 or higher

1.15.0

Enhancement View pull request
Deprecate s3 input in cloudwatch integration

Enhancement View pull request
Improve description for cloudwatch integration

—

1.14.8

Bug fix View pull request
Fix http.response.status_code to accept 000

7.15.0 or higher
8.0.0 or higher

1.14.7

Bug fix View pull request
Fix aws.dimensions.* for rds data stream

Bug fix View pull request
Fix aws.dimensions.* for sns data stream

Bug fix View pull request
Add aws.dimensions.* for dynamodb data stream

7.15.0 or higher
8.0.0 or higher

1.14.6

Enhancement View pull request
Improve s3 integration tile title and description

—

1.14.5

Bug fix View pull request
Fix duplicate titles for integrations

7.15.0 or higher
8.0.0 or higher

1.14.4

Bug fix View pull request
Fix cloudfront integration grok pattern

—

1.14.3

Enhancement View pull request
Add new pattern to VPC Flow logs including all 29 v5 fields

—

1.14.2

Bug fix View pull request
Fix billing dashboard.

—

1.14.1

Enhancement View pull request
Add documentation for multi-fields

—

1.14.0

Enhancement View pull request
Add configuration for max_number_of_messages to the aws.firewall_logs S3 input.

7.15.0 or higher
8.0.0 or higher

1.13.1

Bug fix View pull request
Fix metricbeat- reference in dashboard

7.15.0 or higher
8.0.0 or higher

1.13.0

Enhancement View pull request
Compress dashboard screenshots.

7.15.0 or higher
8.0.0 or higher

1.12.1

Bug fix View pull request
Fix field mapping conflicts in the elb_logs data stream relating to ECS fields (trace.id, source.port, and a few others).

7.15.0 or higher
8.0.0 or higher

1.12.0

Enhancement View pull request
Add CloudFront Logs Datastream

—

1.11.4

Bug fix View pull request
Add Ingest Pipeline script to map IANA Protocol Numbers

—

1.11.3

Bug fix View pull request
Changing missing ecs versions to 8.0.0

—

1.11.2

Bug fix View pull request
Add data_stream.dataset option for custom aws-cloudwatch log input

—

1.11.1

Bug fix View pull request
Update permission list

—

1.11.0

Enhancement View pull request
Update to ECS 8.0

7.15.0 or higher
8.0.0 or higher

1.10.2

Enhancement View pull request
Change cloudwatch metrics and logs default to false

7.15.0 or higher
8.0.0 or higher

1.10.1

Enhancement View pull request
Add description of supported vpcflow formats

—

1.10.0

Enhancement View pull request
Add cloudwatch input into AWS package for log collection

—

1.9.0

Enhancement View pull request
Add Route 53 Resolver Logs Datastream

7.15.0 or higher
8.0.0 or higher

1.8.0

Enhancement View pull request
Add Route 53 Public Zone Logs Datastream

—

1.7.1

Bug fix View pull request
Regenerate test files using the new GeoIP database

—

1.7.0

Enhancement View pull request
Add integration for AWS Network Firewall

—

1.6.2

Bug fix View pull request
Change test public IPs to the supported subset

—

1.6.1

Enhancement View pull request
Fix the value of event.created in CloudTrail data stream.

7.15.0 or higher
8.0.0 or higher

1.6.0

Enhancement View pull request
Add max_number_of_messages config option to AWS S3 input config.

—

1.5.1

Enhancement View pull request
Add missing sample events

7.15.0 or higher
8.0.0 or higher

1.5.0

Enhancement View pull request
Support Kibana 8.0

7.15.0 or higher
8.0.0 or higher

1.4.1

Enhancement View pull request
Add Overview dashboard for AWS S3 Storage Lens

7.15.0 or higher

1.4.0

Enhancement View pull request
Add integration for AWS S3 Storage Lens

—

1.3.2

Enhancement View pull request
Uniform with guidelines

—

1.3.1

Enhancement View pull request
Add config parameter descriptions

—

1.3.0

Enhancement View pull request
Add WAF datastream

—

1.2.2

Bug fix View pull request
Prevent pipeline script error

—

1.2.1

Bug fix View pull request
Fix logic that checks for the 'forwarded' tag

—

1.2.0

Enhancement View pull request
Update to ECS 1.12.0

—

1.1.0

Enhancement View pull request
vpcflow sync with filebeat fileset

7.14.0 or higher

1.0.0

Enhancement View pull request
Release AWS as GA

7.14.0 or higher

0.10.7

Enhancement View pull request
Add proxy config

—

0.10.6

Bug fix View pull request
Fix aws.billing.EstimatedCharges field name

—

0.10.5

Bug fix View pull request
Add event.created field

—

0.10.4

Enhancement View pull request
Improve RDS dashboard

—

0.10.3

Enhancement View pull request
Convert to generated ECS fields

—

0.10.2

Enhancement View pull request
update to ECS 1.11.0

—

0.10.1

Enhancement View pull request
Escape special characters in docs

—

0.10.0

Enhancement View pull request
Update integration description

—

0.9.3

Bug fix View pull request
Fix categories for each policy template

—

0.9.2

Enhancement View pull request
Add linked account information into billing metricset

—

0.9.1

Bug fix View pull request
Fix aws.s3access pipeline when remote IP is a -

—

0.9.0

Enhancement View pull request
Change default credential options to access keys

—

0.8.0

Enhancement View pull request
Set "event.module" and "event.dataset"

—

0.7.0

Enhancement View pull request
Introduce granularity using input_groups

—

0.6.4

Enhancement View pull request
Add support for Splunk authorization tokens

—

0.6.3

Bug fix View pull request
Fix bug in Third Party ingest pipeline

—

0.6.2

Bug fix View pull request
Removed incorrect http.request.referrer field from elb logs

—

0.6.1

Enhancement View pull request
Add support for CloudTrail Digest & Insight logs

—

0.6.0

Enhancement View pull request
Update ECS version, add event.original and preparing for package GA

—

0.5.6

Bug fix View pull request
Fix stack compatability

—

0.5.5

Enhancement View pull request
Allow role_arn work with access keys for AWS

—

0.5.4

Enhancement View pull request
Rename s3 input to aws-s3.

—

0.5.3

Enhancement View pull request
Add missing "geo" fields

—

0.5.2

Enhancement View pull request
update to ECS 1.9.0

—

0.5.1

Bug fix View pull request
Ignore missing "json" field in ingest pipeline

—

0.5.0

Enhancement View pull request
Moving edge processors to ingest pipeline

—

0.4.2

Enhancement View pull request
Updating package owner

—

0.4.1

Bug fix View pull request
Correct sample event file.

—

0.4.0

Enhancement View pull request
Add changes to use ECS 1.8 fields.

—

0.0.3

Enhancement View pull request
initial release

—

On this page