Hello!
I’m running Orthanc in Docker on an EC2 in AWS. I started with this cloudformation template https://github.com/aws-samples/annotate-medical-images-in-dicom-server-and-build-ml-models-on-amazon-sagemaker but I’ve made plenty of changes since
I’m using S3 storage plugin and plan to process and store every DICOM file in S3. Is it possible to completely remove the local storage and the database? I’ve read through the book but haven’t found anything explicitly stating how to do this.
A related question, the S3 plugin uploads two files for each DICOM upload, only one file contains the pixel data. Is there a way to configure the plugin to only upload the file with the pixel data?
Thanks in advance!
Hi Dylan,
We run Orthanc in AWS and use S3 for file storage and a Postgres RDS Instance along with the Orthanc Postgres database plugin. This way no data is stored on the Orthanc server. I’m not sure if its possible to run Orthanc without a database.
James
Hello James,
We run Orthanc in AWS and use S3 for file storage and a Postgres RDS Instance along with the Orthanc Postgres database plugin. This way no data is stored on the Orthanc server. I’m not sure if its possible to run Orthanc without a database.
=> No, Orthanc cannot run without a database.
Hello Dylan,
Hello!
I’m running Orthanc in Docker on an EC2 in AWS. I started with this cloudformation template https://github.com/aws-samples/annotate-medical-images-in-dicom-server-and-build-ml-models-on-amazon-sagemaker but I’ve made plenty of changes since
I’m using S3 storage plugin and plan to process and store every DICOM file in S3. Is it possible to completely remove the local storage and the database? I’ve read through the book but haven’t found anything explicitly stating how to do this.
=> Check out the following pages:
A related question, the S3 plugin uploads two files for each DICOM upload, only one file contains the pixel data. Is there a way to configure the plugin to only upload the file with the pixel data?
Yes, if you use versions of Orthanc (since release 1.9.1) and of the S3 plugin (since release 1.2.0) that support “range reads”, this will be done automatically.
Check out the following page for more technical details (cf. attachments 1, 2 and 3):
https://book.orthanc-server.com/faq/features.html?highlight=range#central-registry-of-metadata-and-attachments
Sébastien-