Configure external object storage for the TempoStack to store trace data instead of using the default storage.
Before you begin
Before you configure external object storage, ensure you have:
- Access to an S3-compatible object storage system
- Storage credentials (access key and secret key)
- Storage bucket or container created and accessible
- Network connectivity between the logging system and object storage
- Administrative access to the TempoStack configuration
About this task
External object storage allows you to use your existing storage infrastructure instead of the default object store. This provides flexibility to manage costs, leverage existing storage, and integrate with your organization storage policies. The following process describes how to configure S3 object storage. You can use similar steps for any S3-compatible object storage service.
Procedure
-
Review the supported object storage types and requirements.
The system supports S3-compatible object storage systems, including:
- Amazon S3
- IBM Cloud Object Storage
- MinIO
- Other S3-compatible storage systems
-
Gather the required connection information for your object storage:
-
Note the storage endpoint URL.
-
Obtain the access key ID and secret access key.
-
Identify the bucket or container name for log storage.
-
Determine the region (if applicable).
-
Create a Kubernetes secret to store the storage credentials.
Use the following namespace and secret name for each component. This keeps credentials secure and separate from configuration files.
Table 1. Namespace and secret name for storage credentials
| Component |
Namespace |
Secret name |
| Tempo |
tempo |
tempo-s3 |
-
Update the TempoStack configuration to use external storage.
Modify the configuration files according to the documentation, specifying:
- Storage type (S3)
- Endpoint URL
- Bucket name
- Region
- Secret reference for credentials
-
Configure storage retention and lifecycle policies.
Set up policies in your object storage system to manage log lifecycle, including archival and deletion based on age.
-
Apply the configuration changes to the TempoStack deployment.
-
Verify that traces are being written to the external storage.
Check the object storage bucket to confirm that traces are being stored correctly.
-
Test trace retrieval and querying. Perform the test queries to ensure that the traces can be retrieved from storage and correctly as visualized in dashboards.
Results
External storage is configured for TempoStack, and trace data is stored in your specified storage system instead of the default storage.
What to do next
Monitor storage costs and usage patterns. Set up billing alerts if available to track storage expenses. Regularly review retention policies to balance storage costs with troubleshooting needs.