temporal icon indicating copy to clipboard operation
temporal copied to clipboard

Adding documentation for self-hosting temporal on cloud environments.

Open Pramodh-G opened this issue 4 months ago • 3 comments

Hi Temporal team!

In my day to day job, we recently tried deploying self-hosted temporal in both AWS EKS and Azure AKS. I found that there's a bunch of gotchas while deploying them. Some of them include:

  • Lack of archival support for Azure with storage containers.
  • AKS + Azure flexible postgres server fails with lots of tiny errors:
    • Azure forces you to have TLS by default, so you have to disable TLS when you deploy it.
    • To use visibility store as postgres in Azure, you need to enable BTREE_GIN extension which doesn't come by default.

I thought these might be helpful to add in documentation. Let me know if you think this is worthwhile and please feel free to leave comments.

Pramodh-G avatar Oct 09 '25 18:10 Pramodh-G

Azure forces you to have TLS by default, so you have to disable TLS when you deploy it.

How did you get over this ?

wadhah101 avatar Oct 15 '25 12:10 wadhah101

Two options here:

  1. You can enable TLS, azure already loads up the certificates in the root correctly.
  2. Disable TLS on azure infra side: This can be done with:
    • Navigating to your Postgres flexible server instance
    • Choose Server PArameters on the sidebar.
    • Search for require_secure_transport -> Set value from on to off.
    • save and redeploy.

In AWS - TLS is not strictly necessary but azure enforces it. We ended up with going to 2, as we deploy temporal in AWS without TLs and wanted to standardize.

Pramodh-G avatar Oct 17 '25 21:10 Pramodh-G

Can I take this?, I just deployed Self hoted Temporal on EKS

AlonGluz avatar Nov 19 '25 06:11 AlonGluz