A "No such object" error is preventing file viewing in Medplum. Issue created in Github: https://github.com/medplum/medplum/issues/6926 Files upload successfully to the root of a GCS bucket using the FUSE CSI driver on a GKE cluster. However, Medplum's retrieval logic incorrectly searches for these files within a bot/ subdirectory, causing the path mismatch. This occurs despite correct IAM permissions and Workload Identity configuration. The central issue is an incorrect storage path configuration within Medplum itself.

@Ankit Yadav Thank you so much for posting such a detailed issue w/ repro

Thanks @Ankit Yadav @rahul1 This seems to be affecting the production environment for a customer. Hopefully we will have solution soon

Thanks for your patience @Ankit Yadav , and for providing such a detailed reproduction of the issue you're encountering with your Google Cloud Platform (GCP) setup and the GCS FUSE driver. We appreciate you taking the time to outline your configuration thoroughly. Currently, our official documentation for self-hosting on GCP, as found here (https://www.medplum.com/docs/self-hosting/install-on-gcp), assumes the use of our provided Terraform configurations and the Google Cloud Storage backend. Your approach, utilizing GCS FUSE, appears to be a highly customized setup that falls outside of our officially supported configurations. While we strive to assist our users, supporting every possible custom environment can be challenging. Therefore, for this particular configuration, we recommend relying on the broader community for advice and further assistance and potential solutions. We would recommending asking in the #1113936455954346005 channel We will, however, keep this issue open for tracking purposes and welcome any contributions or insights from the community that might help resolve it. If this functionality is critical to your use case and you would like to explore the possibility of sponsored development for official support of this configuration, please feel free to reach out to our sales team through our contact page on the website. We hope this clarifies our position, and we wish you the best in finding a resolution.