Single EC2 Instance

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Set up the Single EC2 Instance

Before you begin To run Mirth® Connect by NextGen Healthcare in a single EC2 instance, you will need the following prerequisites: Set up a virtual private cloud (VPC) with at least two private subnets An RDS database. Select EC2 from the Main Menu of the AWS console. Click Launch Instance, then select Launch Instance. Select Amazon Linux 2 AMI (HVM), SSD Volume Type for the AMI. For this single node setup, selectt3.medium (2 CPU, 4 GB RAM). Click Next: Configure Instance Details. Network: Select the VPC that you created in the Networking section of this document. Subnet: Select one of the subnets created in the Networking section of this document. Auto-assign Public IP: Select Disable (you are in a private subnet and will be behind an elastic load balancer). Keep the rest of the defaults on this page and select Next: Add Storage. Keep the default size for the root EBS volume (8GB) and select Next: Add Tags. Select Next: Configure Security Group. Next to Assign a security group, select

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Install Mirth® Connect on the EC2 Instance

SSH into your newly created EC2 instance using your key pair. Edit the mirth.properties file to point to the RDS database that you created in a previous step. In the terminal, enter the following: EC2 Terminal Window $ wget http://downloads.mirthcorp.com/connect/3.11.0.b2609/mirthconnect-3.11.0.b2609-unix.tar.gz$ sudo yum update$ sudo yum install -y java-11-amazon-corretto-devel$ tar -xzf mirthconnect-3.11.0.b2609-unix.tar.gz$ cd "Mirth® Connect"$ cat docs/mcservice-java9+.vmoptions >> mcserver.vmoptions$ echo "server.id.ephemeral = true" >> conf/mirth.properties$ . /mcserver & Parent topic: Single EC2 Instance

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Create an Internet-Facing Load Balancer

From the AWS console, select EC2. On the left panel, scroll down and select Load Balancers. Click Create Load Balancer. Select Network Load Balancer by pressing the Create button for that option. Give your load balancer a name, then select internet facing and IPv4. For Network Mapping, select the VPC that you created in the Networking section of this document. Map the desired availability zone(s) and desired subnet(s). Create listener(s) for your load balancer: First, create a target group by clicking the Create target group shortcut. It opens a new window. Choose the instance target type. Create a target group name: TargetGroupPort8080. Choose TCP port 8080. Select the VPC you created for this instance . Click Next Register your instance target, (the EC2 instance created in the previous step) by checking the box next to this instance and entering the ports for this instance (8080, 8443, etc.). Click Include as pending below. Click Create Target Group. Go back to the load balancer page

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Clustering in EC2

To run a cluster of 2+ nodes in EC2, you will need to add the following plugins: Advanced Clustering SSL Download these plugins (and any other plugins you may need) and place them in the extensions folder of your Mirth® Connect by NextGen Healthcare installation on your EC2 instance created in the previous step. Clone the EC2 Instance by Creating an AMI Launch a New EC2 Instance Using This Image Clone the EC2 Instance by Creating an AMI Launch a New EC2 Instance Using This Image EC2 Diagram Upgrading Parent topic: EC2

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

EC2

Mirth® Connect by NextGen Healthcare can be run in AWS using a single EC2 instance or a cluster of multiple EC2 instances. Single EC2 Instance Clustering in EC2 Single EC2 Instance Clustering in EC2

Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment

Launch a New EC2 Instance Using This Image

From the EC2 page, click Launch Instance, then select Launch Instance. In the left menu, select My AMIs, then select the image you created in the previous step. Finish the prompts to launch an instance using this AMI and add it to the same subnet as the previous node. SSH into the instance and start the Mirth® Connect by NextGen Healthcare server. Verify that the node has joined the cluster using the server logs . Parent topic: Clustering in EC2

Single EC2 Instance

Recommendations

Set up the Single EC2 Instance

Install Mirth® Connect on the EC2 Instance

Create an Internet-Facing Load Balancer

Clustering in EC2

EC2

Launch a New EC2 Instance Using This Image

Single EC2 Instance

Set up the Single EC2 Instance

Install Mirth® Connect on the EC2 Instance

Create an Internet-Facing Load Balancer

Clustering in EC2

EC2

Launch a New EC2 Instance Using This Image