Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-794

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

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhosdt-3.3
    • None
    • PM Tracing
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% To Do, 0% In Progress, 100% Done

      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.

              rh-ee-jgomezse Jose Gomez-Selles
              njajodia Nirjhar Jajodia (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: