Archival to s3 in helm charts

[Sandeep_Paul]

Hi @ryland,

(in the context of .29 helm chart)

I tried adding the value as mentioned in the below topic by @samar in the server-config.yaml

How to enable s3 archival in cadence 0.13

Looks like there are no hooks provided in our existing config_template.yaml for docker image to override defaults for archival config. Filed a feature to add support for overriding archival config. If you are running Temporal using docker-compose then by default it brings up the server with archival turned on using file based archival config. I just filed an issue to disable it by default and have a separate docker-compose-archival.yaml for folks who want to try it out with archival turned o…

archival:
  history:
    state: "enabled"
    enableRead: true
    provider:
      s3store:
        region: "eu-central-1"
        endpoint: "https://<bucket_name>.s3.eu-central-1.amazonaws.com"   **>>>>> (1) is the format correct ??**
  visibility:
    state: "enabled"
    enableRead: true
    provider:
      s3store:
        region: "eu-central-1"
        endpoint: "https://<bucket_name>.s3.eu-central-1.amazonaws.com"  

namespaceDefaults:
  archival:
    history:
      state: "enabled"
      URI: "s3://<bucket_name>/history"   **>>>> (2) is the format correct ??**
    visibility:
      state: "enabled"
      URI: "s3://<bucket_name>/visibility"

the archival didnt work as expected, which led me to think of possibilities.

1: is the s3store endpoint format correct ??
2: is the URI format correct ??
3: if these two values are correct, where will the archival process get the authorisation to push data into the s3 ?? (I have attached s3-full-access policy in a role and attached it to the EKS cluster)

I checked the tctl namespace list cmd in the admintool pod which is clearly showing that the archival is still disabled even after passing the enabled value in the configmap.

Any lead on this regard would be helpful.

thanks and regards
Sandeep