Hey guys, we’re hosting medplum on GCP right now, and has been quite smooth, except the storage signing for binary resources. Right now it is done via cloudfront, but s3 has support for signing natively. GCP buckets have s3 api compatibility so we are using it as is directly, but the cloudfront thing is blocking its proper use. I’ve created a very small patch of medplum and we’re currently maintaining our own (private) fork and it works quite well for us, and an issue (https://github.com/medplum/medplum/issues/4815) plus a PR (https://github.com/medplum/medplum/pull/4817) that implements it. But haven’t gotten and 👀 love. Was wondering if the approach we’re taking is the right one.