How to Update Archival URI After Namespace Creation

Community Support
,
1

Hi,

I have a question regarding archival configuration in Temporal:

Once a namespace is created with file:// URIs for history_uri and visibility_uri, is it possible to update them later to switch to a different backend (e.g., from file:// to s3://)?

I understand that archival URIs are immutable after initial set, but:

  • Is there a safe way to migrate archival storage from file to S3 for an existing namespace?
  • If not, what’s the recommended path — creating a new namespace with S3 configured and migrating workflows?
  • Will there ever be support for changing archival backends post-creation?

Appreciate any guidance. Thanks!

2

File system based archival (default) if enabled is really meant for testing. If you start using archival I’d use the s3 or gcloud providers to begin with.
There is to my knowledge no ability for migration of already archived workflows to a different provider. That said you should be able to update static config , see here and do service restart to pick up changes.