Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
The Amazon S3 destination plugin (name: s3) lets you configure your telemetry pipeline to store and archive your data by sending it directly to your Amazon S3 bucket.

Supported telemetry types

The for Chronosphere Telemetry Pipeline supports these telemetry types:

Configuration parameters

Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

Required

AWS Authentication

Advanced

Advanced Networking

Shared credential file

Your shared credential file provides authentication credentials to the Amazon S3 destination plugin. This file must be an AWS credentials file that includes an aws_access_key_id parameter and an aws_secret_access_key parameter. For example:
To reference this file in your plugin configuration, use the following syntax:
Replace NAME with the name of your credentials file.

Bucket policies

To use the Amazon S3 destination plugin, you must grant the plugin write access to your S3 buckets. These bucket policies are managed within Amazon S3, not within the plugin’s own configuration. For example, the following bucket policy lets the Amazon S3 destination plugin send data to a bucket named my-bucket: