Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-4408

Set Up AWS STS Access for Tempo to Connect to AWS S3

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhosdt-3.3
    • None
    • None
    • None
    • TBD
    • 1
    • False
    • None
    • False
    • Not Selected
    • To Do

      Jaeger has been deprecated as a service mesh component, and customers are transitioning to Tempo. Tempo utilizes object storage for metric storage.

      currently, Tempo supports AWS S3 access via access key and secret key. To access S3, we typically create a secret in OpenShift containing these keys. However, the customer's SIEM team does not permit storing secrets locally on the cluster. Could you please configure new feature access to AWS S3 using temporary access with AWS STS for Tempo. enabling a more secure method of access without local store the secret on cluster.

              ploffay@redhat.com Pavol Loffay
              njajodia Nirjhar Jajodia (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: