Summary

With the upcoming Functionbeat, we'd like to introduce a new addition to the Add Data UI for “AWS”. This Functionbeat will be based on Beats core, allowing users to define functions that can be uploaded to AWS Lambda to collect data from various first-class AWS services like Cloudwatch logs, Kinesis, S3, etc. when triggered. The initial version will be beta or experimental and will support:

• Only AWS Lambda - GCP and Azure will be available in the future.
• Only Cloudwatch logs for the CLI setup - Kinesis, S3, SQS, and API Gateway will be available shortly after.

Listing

Title: AWS
Description: “Collect data from AWS services with AWS Lambda”
Note: This will only go under the "All" tab, as the type of data it collects can be generic.

Tutorial

Title: AWS (Beta | Experimental)
Description: “Functionbeat collects data from your AWS services with AWS Lambda. Learn more.”

There should be separate instructions for “Self managed” and “Elastic Cloud”. The general workflow is outlined below:

Getting Started
Three tabs: MacOS, Windows, Linux. There will be two options: .zip and .tar.gz.

1. Download and unpack Functionbeat
2. Configure AWS credentials

Set up AWS service
Two tabs to begin with: Cloudwatch Logs and SQS. We should use the APM-like template (see image below) to make sure this is future proof for adding instruction tabs for Kinesis, S3, API Gateway, etc.

3. Edit the configuration

4. Upload Functionbeat as an AWS Lambda function
5. Check AWS Lambda console to make sure function has successfully uploaded