This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

« Step 3: Load the index template in Elasticsearch Step 5: View your data in Kibana »

› ›

Step 4: Deploy Functionbeat code to your serverless environment

edit

Step 4: Deploy Functionbeat code to your serverless environment

edit

Before deploying functions to your serverless environment, make sure your user has the credentials required by your cloud service provider. For example, if you are deploying an AWS Lambda function, you can set environment variables that contain your credentials:

linux and mac:

export AWS_ACCESS_KEY_ID=ABCDEFGHIJKLMNOPUSER
export AWS_SECRET_ACCESS_KEY=EXAMPLE567890devgHIJKMLOPNQRSTUVZ1234KEY
export AWS_DEFAULT_REGION=us-east-1

win:

set AWS_ACCESS_KEY_ID=ABCDEFGHIJKLMNOPUSER
set AWS_SECRET_ACCESS_KEY=EXAMPLE567890devgHIJKMLOPNQRSTUVZ1234KEY
set AWS_DEFAULT_REGION=us-east-1

Set AWS_DEFAULT_REGION to the region where your services are running.

After setting credentials, run the deploy command to deploy the function. The following command deploys a function called cloudwatch:

linux and mac:

./functionbeat -v -e -d "*" deploy cloudwatch

win:

.\functionbeat.exe -v -e -d "*" deploy cloudwatch

Functionbeat is now deployed in your serverless environment and ready to send log events to the configured output.

If you change the configuration after deploying the function, use the update command to update your deployment.

« Step 3: Load the index template in Elasticsearch Step 5: View your data in Kibana »