#support

Resolving Linode S3 Error in Config

TLDR chintan encountered a Linode S3 error and was able to resolve it by modifying the endpoint format in the config.

6mo

Join the chat

Jun 19, 2023 (6 months ago)

Photo of md5-5160a496f51f350885fb9a7bc6b8004b

chintan

02:23 AM

Hello, getting following error when specifying Linode S3

2023.06.19 01:58:05.205134 [ 7 ] {} <Error> Application: DB::Exception: Bucket or key name are invalid in S3 URI

in following config

clickhouse:
  coldStorage:
    enabled: true
    # Set free space size on default disk in bytes
    defaultKeepFreeSpaceBytes: "10485760" # 10MiB
    type: s3
    endpoint: https://<bucket_name>.
    accessKey: <access_key>
    secretAccess: <secretaccess>

Any help appreciated... Thanks

12:47

chintan

12:47 PM

I was able resolved issue by passing endpoint into following format

type: s3
endpoint: <bucket_name>/<key_name>/
accessKey: <access_key>
secretAccess: <secretaccess>

SigNoz Community

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

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Services UI Goes Blank Due to Retention Issue with S3 Bucket

oluchi reports issue with services UI going blank after a while. Conversation explores possible reasons, such as S3 connection problems and disk space, but no resolution is reached.

7mo

Troubleshooting Signoz S3 Bucket File Creation Issue

Nishant has an issue with no files being created in their S3 bucket after updating Signoz. Prashant asks to verify credentials and check logs.

8mo

Setting Up Signoz Standalone with S3 Bucket

Kurt needed help setting up Signoz standalone using an S3 bucket. Ankit provided advice on configuration and suggested checking the S3 endpoint region.

9mo