Loading...
Recommendations
Explore
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 .
Launch a New EC2 Instance Using This Image
Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment
Clone the EC2 Instance by Creating an AMI
Create an AMI of the EC2 instance with Mirth® Connect by NextGen Healthcare and the advanced clustering and SSL plugins by navigating to the EC2 page, listing the instances and right-clicking the EC2 Mirth® Connect instance you created. Select Image and Templates > Create Image from the menu. Enter a name for this image, like "Connect 3.11 Node". Click Create Image. Parent topic: Clustering in EC2
Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment
Upgrading
To Upgrade Mirth® Connect by NextGen Healthcare: SSH into each node and replace the Mirth® Connect folder with the latest version of Mirth® Connect by NextGen Healthcare from the Success Community. Update the plugins in the extension folder to match the new version of Mirth® Connect by NextGen Healthcare. Parent topic: Clustering in EC2
Mirth® Connect by NextGen Healthcare Amazon Web Services (AWS) Preferred Deployment
EC2 Diagram
Figure 1. Mirth® Connect by NextGen Healthcare Clustering in AWS with EC2 Parent topic: Clustering in EC2
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
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
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
