SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

Hi team, I am using community edition signoz updated to latest 0.18.1 and log, metrics, traces (7 day retention) set with s3 bucket credentials from past 2 months in the file `signoz/deploy/docker/clickhouse-setup/clickhouse-storage.xml`

```&lt;s3&gt;
&lt;type&gt;s3&lt;/type&gt;
&lt;endpoint&gt;<https://BUCKET-NAME.s3.amazonaws.com/data/>&lt;/endpoint&gt;
&lt;access_key_id&gt;ACCESS-KEY-ID&lt;/access_key_id&gt;
&lt;secret_access_key&gt;SECRET-ACCESS-KEY&lt;/secret_access_key&gt;
&lt;/s3&gt;```
however I dont see any files created in my s3 bucket. Is there anything I am doing wrong here?
Running signoz with docker on aws t3a.2xlarge instance

Hi <@U04GYUUHLLX> :wave:

can you verify that provided bucket name and S3 credentials are correct?

did you check clickhouse logs? anything related to S3 there?

in past, we have noticed that config changes via volume mount, not propagating with docker-compose.
And it required removing the existing container and spawning them again.

credentials are correct. I haven’t checked the logs will give you a follow up on this.
Also I am running the existing container after updating the config with docker compose restart