Skip to main content
Ent+
This feature is available as an add-on for the Honeycomb Enterprise plan. Please contact your Honeycomb account team for details.

Supported Types

​The AWS S3 destination saves telemetry into timestamped JSON files in an S3 bucket.

Configuration

* required field

Marshaler Configuration

The destinations supports configuring the marshaler for each telemetry type. The marshaler determines how the data is formatted before being sent to AWS S3. By default, the otlp_json marshaler is used for all telemetry types.
Note that sumo_ic and body marshaler types are only applicable for logs.

Credentials

With AWS S3, users are required to provide some form of authentication. There are two ways to configure this: either entering profile credentials manually or using the CLI, or environment variables that specify access keys for user accounts.
​ In the AWS CLI getting started guide it will instruct you to install for your current user or all users.
The observIQ OTel Collector runs as root by default, meaning the AWS CLI and credentials should be installed under the collector system’s root account.

CLI

The easiest way to configure this is using the aws CLI program provided by AWS. The AWS CLI Getting Started guide describes how to install the CLI and configure it with credentials. The AWS S3 destination uploads telemetry to the specified bucket, so the credentials configured should be associated with an account that has s3:PutObject permissions for that bucket.

Environment Variables

Alternatively, AWS Environment variables can be specified to override a credentials file. You can modify the collector’s environment variables by configuring a systemd override.
Run sudo systemctl edit observiq-otel-collector and add your access key, secret key, and region:
After making that change, reload Systemd and restart the collector service.