Setting Up Signoz Standalone with S3 Bucket
TLDR Kurt needed help setting up Signoz standalone using an S3 bucket. Ankit provided advice on configuration and suggested checking the S3 endpoint region.
Ankit
Tue, 21 Mar 2023 03:30:09 UTCmaybe you need to set `move to s3` period from the UI
Kurt
Tue, 21 Mar 2023 14:18:28 UTCHow do you enable S3 for the Move to S3 option to show up?
Ankit
Tue, 21 Mar 2023 14:22:21 UTCit automatically comes up if the s3 config is correctly configured
Ankit
Tue, 21 Mar 2023 14:23:47 UTCthe s3 endpoint would look something like
```
Ankit
Tue, 21 Mar 2023 14:24:12 UTCdid you miss region in the endpoint?
Kurt
Tue, 21 Mar 2023 14:44:40 UTCLet me check on that. Thanks for fast responses.
SigNoz Community
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in AppSimilar Threads
Troubleshooting Signoz S3 Bucket File Creation Issue
Services UI Goes Blank Due to Retention Issue with S3 Bucket
Configuring ClickHouse for S3 Retention and EC2 Deployment
Resolving Log Retention and Login Issues in Clickhouse
Issues with Log Retention Configuration on Self-Hosted SigNoz Installation
Kurt
Mon, 20 Mar 2023 14:20:49 UTCTeam, I am trying to get Signoz standalone running using S3 bucket. Do you have detailed steps on how to do this? 1. I have edit the clickhouse-storage.xml and changed the endpoint, access_key_id, and secret_access_key. 2. I have edit the clickhouse-config.xml and change the database to s3 <!-- Default database. --> <default_database>s3</default_database> 3. Stopped and restart the containers but it’s not writing to s3. I know I am missing something.