Provide s3 credential to archival with helm

Hello support team,

How can I provide s3 credentials ( aws access key and secret key ) with helm installation on aws eks?

I am using below command to install temporal

helm install temporal \
   -f values/values.mysql.yaml \
   -f values/values.archival.s3.yaml \
   --set elasticsearch.enabled=false \
   --set grafana.enabled=false \
   --set prometheus.enabled=false \
   --set server.replicaCount=1 \
   . \
   --timeout 15m \
   --namespace temporal --create-namespace \
   --wait

Hi, sorry for late reply, you would need to use one of ways described here.
So for example you could set in your server-deployment.yaml:

aws_access_key_id = <YOUR_ACCESS_KEY_ID>
aws_secret_access_key = <YOUR_SECRET_ACCESS_KEY>

Thanks @tihomir . I am using temporal helm charts. Can you please help me if how credentials can be provided in this file helm-charts/values.archival.s3.yaml at master · temporalio/helm-charts · GitHub

Thanks @tihomir , should it be in the env section of templates/server-deployment.yaml file?

Got the fix. Below are the steps:

  1. Update templates/server-deployment.yaml, put aws access and secret key in the config.
    ...
     containers:
        - name: {{ $.Chart.Name }}-{{ $service }}
          image: "{{ $.Values.server.image.repository }}:{{ $.Values.server.image.tag }}"
          imagePullPolicy: {{ $.Values.server.image.pullPolicy }}
          env:
            - name: POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            - name: AWS_ACCESS_KEY_ID
              value: *****************
            - name: AWS_SECRET_ACCESS_KEY
              value: ****************************
...
  1. Ensure that you have right permission for the user to which aws access and secret key are associated.
  2. Run below command on the aws admin container
tctl --namespace default namespace update --has enabled
tctl --namespace default namespace update -vas enabled

2 Likes