# Temporal Archive not working **URL:** \ **Category:** Server Deployment\ **Created:** [November 2, 2025, 2:14pm UTC](https://community.temporal.io/t/temporal-archive-not-working/18620 "2025-11-02T14:14:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Meridian\_Asllani](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/meridian_asllani/32/7894_2.png) [@Meridian\_Asllani](https://community.temporal.io/u/Meridian_Asllani)\ **Post date:** [November 2, 2025, 2:14pm UTC](https://community.temporal.io/t/temporal-archive-not-working/18620/1 "2025-11-02T14:14:46Z")
We’re running a **self-hosted Temporal cluster on AWS ECS** , not via Helm. Each Temporal service (frontend, history, matching, worker) runs as its own ECS service using temporal-server official docker image. From the CLI (`temporal operator namespace describe default`), both **History** and **Visibility archival** show as **Enabled** , and the `/tmp/temporal_archival` aswell. However — when workflows pass their retention period, they are deleted from persistence but **don’t appear in the archive list** , and nothing new shows up under `/tmp/temporal_archival` or `/tmp/temporal_vis_archival`. Can I please get more information regarding how archive works so I can set it up? Thank you! ---
**Author:** ![Meridian\_Asllani](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/meridian_asllani/32/7894_2.png) [@Meridian\_Asllani](https://community.temporal.io/u/Meridian_Asllani)\ **Post date:** [November 2, 2025, 2:46pm UTC](https://community.temporal.io/t/temporal-archive-not-working/18620/2 "2025-11-02T14:46:56Z")
After reading more and using the slack channel, I see that using file system to store the archives in containers is not very good. I also have tried configuring an s3 bucket to store them but it still does not work as I could not modify the default values when building the image, can someone please help me with this?