AWS S3 Data Storage

By default, Chronicle Server writes data locally to /var/lib/posit-chronicle/data. Chronicle also optionally supports writing the data to cloud storage in an AWS S3 bucket.

Set up an S3 bucket

In your desired AWS region, create a new S3 bucket to store Chronicle data. Chronicle Server expects this bucket to be empty and not shared with other services.

Configure AWS credentials

To allow Chronicle Server to access the selected S3 bucket, configure the credentials on the server where Chronicle is installed. The recommended authentication method depends on the type of deployment:

Virtual machine-based deployment

When the server is deployed on a virtual machine (VM) or EC2 instance, the recommended authentication method is an instance profile.

Kubernetes-based deployment

When the server is running on Kubernetes, the recommended authentication method is to use IAM roles for service accounts.

Important

When storing files created by Posit Chronicle in S3, use the built-in AWS S3 lifecycle rules to manage file retention. See Setting a lifecycle configuration on a bucket for more information.

Enable S3 storage in Chronicle Server configuration

Enable S3 Storage by specifying the S3 Bucket name and region in the Chronicle configuration file:

/etc/posit-chronicle/posit-chronicle.gcfg
[LocalStorage]
Enabled = false

[S3Storage]
Enabled = true
Bucket = posit-chronicle
Region = us-east-2

After making these edits, restart the Chronicle Server via systemd for the changes to take effect:

Terminal
$ systemctl restart chronicle
Back to top