AWS Orthan Server

Greetings to this noble community,

I am using a Orthans Server on my MacBook as a local server and I would like to run the same tasks on an AWS Server. Is it possible? If yes, how?

Do you recommend any other solution for this? I just need to run 3 DICOM images as a WADOURI.

Thank your,

FMC

Greetings to this noble community,

I am using a Orthans Server on my MacBook as a local server and I would
like to run the same tasks on an AWS Server. Is it possible? If yes, how?

Yes, Orthanc runs on any kind of server. On AWS, you should be able to
deploy it on a Linux VM or with Docker. The fact that it runs on AWS does
not change much.

If you want to use S3 for the image storage, you'll have to develop a
storage plugin by yourself since I don't think such a plugin is available
by now.

I tried with EC2 with no success. Do you have any guide to do it?

I have never encountered a guide specific to Orthanc on EC2, I don't
think there is much of anything special to it.

Just get SSH access to an EC2 Linux VM for example (contact Amazon
support if you're having difficulties), from there the installation
procedure is the same as everywhere else.

I have never encountered a guide specific to Orthanc on EC2, I don't
think there is much of anything special to it.

This is correct - it's just a bog standard linux server.

Just get SSH access to an EC2 Linux VM for example (contact Amazon
support if you're having difficulties), from there the installation
procedure is the same as everywhere else.

The one additional bit that may need to be taken care of is ensuring
that Security Group rules for the host allow traffic to the Orthanc
DICOM and web ports.

I run Orthanc Server (DIMSE and HTTP), also DCM4CHEE ver 2 and ver 5, on AWS EC2 instances. As the other respondents have said, an EC2 instance is a standard Linux (or Windows) machine, so there’s no difference as far as the software is concerned.

Your problem is likely related to the AWS networking, in particular security group rules. AWS is designed to scale to enterprise size, so the minimum level of complexity is higher than some other hosting services (DigitalOcean or Linode instances are simpler to set up). You’ll need to be familiar with the concepts of security groups and CIDRs, VPC (Virtual Private Cloud), and Elastic IPs. In this case, the solution could be as simple as adding your IP address for ports 8042 and 4242 in the security group for your instance.

You can’t run Docker on an EC2 instance, since it is itself a virtual machine. You might be able to run the Docker image on AWS Container Service though I haven’t tried this.

Don’t let this put you off - AWS is a brilliant platform. Just takes some learning.

You can't run Docker on an EC2 instance, since it is itself a virtual
machine.

Just a quick note: there's no problem running Docker inside a virtual
machine. We do it everyday on Azure, have done it for long on AWS and on
our development machines too. Docker is not an additional virtualization
layer; it runs fine inside VM without significant performance drop.

You might be able to run the Docker image on AWS Container Service though
I haven't tried this.

Indeed, that's an option too. Take care that, in this case, you won't have
access to a persistent filesystem -> you won't be able to use any VOLUME ->
you'll have to store your index in an external postgresql DB and you'll
probably need to write a S3 plugin to store your files (you might store
your files in postgresql DB too but we have observed significant file usage
overhead - check the 'remark' in
PostgreSQL plugins — Orthanc Book documentation)