TempoOperator (tempo-operator.v0.16.0-1) does not honor region parameter in S3 secret configuration except for the Amazon S3 with Security Token Service (STS) configuration even though Tempo does support the region parameter which is necessary for a valid signature if not using us-east-1.

This issue is files as bug as Tempo does support the parameter in the storage configuration as expected.

    storage:
        ...
        s3:
          bucket: tempo
          endpoint: s3-us-west-1.amazon.com
          access_key: ...
          secret_key: ...
          insecure: false
          region: us-west-1

This configuration parameter is mandatory in particular in larger deployments where different cluster create traces and need to use different S3 regions to save costs (eu-* vs us-* and so on) as well as having replication between regions working for consolidating traces.

Withou that possibility, duplication and quota issues are poping on the horizon as Tempo can consolidate Traces but span's are duplicated.