Enabling Tempo¶

Configure AWS S3 for Tempo¶

Prerequisites¶

Ensure the following are in place:

1. An S3 bucket to store Tempo data.
2. An IAM role with the necessary permissions and trust relationship(of kubernetes service account).

Step 1: Ensure that an Identity Provider (IdP) is already created for your EKS cluster’s OIDC. If not, create a new Identity Provider before proceeding.¶

1. Navigate to AWS EKS → Select your cluster.
2. From the Overview tab, copy the OIDC (OpenID Connect) provider URL.
3. Go to IAM → Identity Providers → Add provider.
   • Select OpenID Connect.
   • Paste the OIDC URL under Provider URL and click Get thumbprint.
   • Set Audience as sts.amazonaws.com.
   • Add optional tags and click Add provider. ( we will need this ID to be added in the IAM role.)

Step 2: Create an IAM Policy¶

Go to IAM → Policies, and create a new policy with the following JSON definition:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

{
"Version": "2012-10-17",
"Statement": [
    {
    "Effect": "Allow",
    "Action": [
        "s3:PutObject",
        "s3:GetObject",
        "s3:ListBucket",
        "s3:DeleteObject",
        "s3:GetObjectTagging",
        "s3:PutObjectTagging"
    ],
    "Resource": [
        "arn:aws:s3:::<AWS_S3_BUCKET_NAME>",
        "arn:aws:s3:::<AWS_S3_BUCKET_NAME>/*"
    ]
    }
]
}

Step 3: Create an IAM Role and Trust Relationship¶

1. Navigate to IAM → Roles → Create role.
2. Select Web identity as the trusted entity type.
3. Choose the OIDC provider created earlier, set Audience to sts.amazonaws.com, and proceed.
4. Attach the custom policy from the previous step.
5. Name and create the role.

Once created, modify the trust relationship to limit role assumption to specific Kubernetes service accounts:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

{
"Version": "2012-10-17",
"Statement": [
    {
    "Effect": "Allow",
    "Principal": {
        "Federated": "arn:aws:iam::<AWS_ACCOUNT_ID>:oidc-provider/oidc.eks.<AWS_REGION>.amazonaws.com/id/<OIDC_ID>"
    },
    "Action": "sts:AssumeRoleWithWebIdentity",
    "Condition": {
        "StringLike": {
        "oidc.eks.<AWS_REGION>.amazonaws.com/id/<OIDC_ID>:sub": [
            "system:serviceaccount:privacera-monitoring:tempo-distributed"
        ]
        }
    }
    }
]
}

Step 4: Configure Tempo for S3¶

1. SSH into the instance where Privacera Manager is installed.
2. Navigate to the configuration directory:

1

cd ~/privacera/privacera-manager/config/custom-vars/

1. Create the Tempo custom values file:

1

vi tempo_distributed_custom_values.yml

1. Add the following configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

storage:
  trace:
    block:
      version: null
      dedicated_columns: []
    backend: s3
    s3:
      bucket: <AWS_S3_BUCKET_NAME>
      prefix: tempo-data
      endpoint: s3-accesspoint.<AWS_REGION>.amazonaws.com
      region: <AWS_REGION>
    pool:
      max_workers: 400
      queue_depth: 20000
  admin:
    backend: filesystem

serviceAccount:
  annotations:
    eks.amazonaws.com/role-arn:  <AWS_IAM_ROLE_ARN>

Step 5: Redeploy Monitoring Components¶

a. Go to privacera-manager directory.

1

cd ~/privacera/privacera-manager.

1

./privacera-manager.sh setup

1

./pm_with_helm.sh install-monitoring

1

./privacera-manager.sh post-install

Configure Azure Blob Storage for Tempo¶

Step 1: Enable Workload Identity on AKS¶

1. Go to Azure Portal → Kubernetes Services → Your AKS Cluster.
2. In the left sidebar, go to Settings → Authentication.
3. Ensure the following are enabled:
   • OIDC Issuer: Enabled
   • Workload Identity: Enabled
4. Click Save if any changes were made.

Step 2: Create a Storage Account¶

1. Go to Azure Portal → Storage Accounts → Create.
2. Configure:
   • Name: e.g., privaceramonitoringsa (must be globally unique)
   • Region: Same as your AKS cluster
   • Resource Group: Same as AKS
   • Performance: Standard
   • Replication: LRS
3. Click Review + create, then Create.

Step 3: Create a Blob Container¶

1. In your created storage account, go to Data storage → Containers.
2. Click + Container and configure:
   • Name: e.g., privacera-monitoring-container
   • Public access level: Private (no anonymous access)
3. Click Create.

Step 4: Create a User-Assigned Managed Identity¶

1. Go to Azure Portal → Managed Identities → Create.
2. Configure:
   • Name: e.g., privacera-monitoring-identity
   • Region: Same as your AKS cluster
   • Resource Group: Same as AKS/storage
3. Click Review + create, then Create.
4. After creation, note down:
   • Client ID

Step 5: Assign Permissions to the Managed Identity¶

1. Go to Storage Accounts → Your Storage Account → Access Control (IAM).
2. Click + Add → Add role assignment.
3. Configure:
   • Role: Storage Blob Data Contributor
   • Assign access to: Managed identity
   • Select member: Choose the privacera-monitoring-identity managed identity
4. Click Save.

Step 6: Add Federated Credential to the Managed Identity¶

1. Go to Azure Portal → Kubernetes Services → Your AKS Cluster → Settings → Authentication.
2. Copy the OIDC Issuer URL (e.g., https://oidc.prod-aks.azure.com/...).

Then:

1. Go to Azure Portal → Managed Identities → privacera-monitoring-identity → Federated credentials.
2. Click + Add credential.
3. Fill in the following:
   • Name: e.g., tempo-federated
   • Issuer: Paste the OIDC Issuer URL
   • Subject: e.g., system:serviceaccount:privacera-monitoring:tempo-distributed
   • Audience: api://AzureADTokenExchange
4. Click Add.

Step 7: Configure Tempo for Azure¶

1. SSH into the Privacera Manager instance.
2. Navigate to the config directory:

1

cd ~/privacera/privacera-manager/config/custom-vars/

1. Create the custom values file:

1

vi tempo_distributed_custom_values.yml

1. Add the following content:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

storage:
  trace:
    backend: azure
    azure:
      container_name: <CONTAINER_NAME>
      storage_account_name: <STORAGE_ACCOUNT_NAME>
      use_federated_token: true
  admin:
    backend: filesystem
serviceAccount:
  annotations:
    azure.workload.identity/client-id: <AZURE_MANAGED_IDENTITY_CLIENT_ID>
tempo: 
  podLabels: 
    azure.workload.identity/use: "true"

Step 8: Redeploy Monitoring Components¶

a. Go to privacera-manager directory.

1

cd ~/privacera/privacera-manager.

1

./privacera-manager.sh setup

1

./pm_with_helm.sh install-monitoring

1

./privacera-manager.sh post-install

Configure GCP Storage for tempo¶

Step 1: Create a GCS Bucket¶

1. Go to GCP Console → Cloud Storage.
2. Click Create Bucket.
3. Configure:
   • Name: Globally unique
   • Region: As required
   • Storage class: Standard
   • Access control: Uniform
4. Click Create.

Step 2: Create a Service Account¶

1. Go to IAM & Admin → Service Accounts.
2. Click Create Service Account.
3. Provide a name and (optionally) a description.
4. Skip assigning roles for now.
5. Click Done.

Step 3: Grant Bucket Access to the Service Account¶

1. Go back to your bucket → Permissions tab.
2. Click Grant Access.
3. Add your service account’s email.
4. Assign the following roles:
   • Storage Admin
   • Storage Object Admin
5. Click Save.

Step 4: Configure Workload Identity¶

1. Open the service account details.
2. Under Permissions, click + Grant Access.
3. In New principals, add:

1

serviceAccount:<PROJECT_ID>.svc.id.goog[privacera-monitoring/tempo-distributed]

1. Assign role:
   Service Account Workload Identity User
2. Save the configuration.

Step 5: Configure tempo for GCP¶

1. SSH into the Privacera Manager instance.
2. Navigate to the config directory:

1

cd ~/privacera/privacera-manager/config/custom-vars/

1. Create the custom values file:

1

vi tempo_distributed_custom_values.yml

1. Add the configuration below:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

storage:
  trace:
    backend: gcs
    gcs:
      bucket_name: <GCP_BUCKET_NAME>
      prefix: "tempo-data"
    pool:
      max_workers: 400
      queue_depth: 20000
  admin:
    backend: filesystem

serviceAccount:
  annotations:
    iam.gke.io/gcp-service-account: "<GCP_SERVICE_ACCOUNT>@<PROJECT_ID>.iam.gserviceaccount.com"

Step 6: Redeploy Monitoring Components¶

a. Go to privacera-manager directory.

1

cd ~/privacera/privacera-manager.

1

./privacera-manager.sh setup

1

./pm_with_helm.sh install-monitoring

1

./privacera-manager.sh post-install