Heavy Channels

	Small	Medium	Large
Container CPU	2048	2048	4096
Container RAM	4GB	8GB	16GB
Count	1	2	2
RDS Instance Type	db.t3.medium2vCPU/4GB	db.m5.large2vCPU/8GB	db.m5.xlarge4vCPU/16GB
Messages per Second	6.37	12.23	29.97

	Small	Medium	Large
Instance Type	t3.medium2vCPU/4GB	m5.large2vCPU/8GB	m5.xlarge4vCPU/16GB
RAM	4GB	8GB	16GB
Network Bandwidth	Up to 10 Gbps	Up to 10 Gbps	Up to 10 Gbps
Count	1	2	2
RDS Instance Type	db.t3.medium 2vCPU/4GB	db.m5.large 2vCPU/8GB	db.m5.xlarge 4vCPU/16GB
Messages per Second	7.81	14.31	13.33

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

Basic Channels

ECS Fargate Small Medium Large Container CPU 2048 2048 4096 Container RAM 4GB 8GB 16GB Count 1 2 2 RDS Instance Type db.t3.medium2vCPU/4GB db.m5.large2vCPU/8GB db.m5.xlarge4vCPU/16GB Messages per Second (Full Storage) 232 420 719 Messages per Second (No Storage) 2,135 5,976 12,463 EC2 Small Medium Large Instance Type t3.medium2vCPU/4GB m5.large2vCPU/8GB m5.xlarge4vCPU/16GB RAM 4GB 8GB 16GB Network Bandwidth Up to 10 Gbps Up to 10 Gbps Up to 10 Gbps Count 1 2 2 RDS Instance Type db.t3.medium 2vCPU/4GB db.m5.large 2vCPU/8GB db.m5.xlarge 4vCPU/16GB Messages per Second (Full Storage) 320 344 758 Messages per Second (No Storage) 3,469 4,747 10,911 Parent topic: Database

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

Amazon Relational Database Service (RDS)

To create your Postgres database in AWS, first sign into your account and search for RDS in the AWS Management Console. Click Databases on the left sidebar. Click the orange Create database button on the top right side of the page. Now you can start selecting options for your new database. Select Standard Create to customize the database configuration. Select PostgreSQL to create a Postgres database, then leave the default version. Select a template for your use case Production - For production-grade deployments. Dev/Test - For development, testing and performance measurements. In Settings enter the following: DB Instance Identifier - prod-mirthdb Master Username - postgres (username for your database such as admin, dev, qatest, etc..) Master Password - XXXXXX (Password for your database) DB Instance Size - The DB instance class determines the computation and memory capacity of an Amazon RDS database instance. The database instance class you need depends on your processing power and me

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

CPU/RAM Recommendations

When considering the CPU and RAM settings for your Mirth® Connect by NextGen Healthcare infrastructure, there is no single recommendation that will work across all environments. Because you can do practically anything with Mirth® Connect by NextGen Healthcare it may take deploying, testing, and monitoring Cloudwatch metrics to determine if your settings are sufficient for your deployed channels. Both CPU and RAM are important in different ways. If your Mirth® Connect by NextGen Healthcare instances are running out of memory (this can happen if you have a lot of channels deployed or if your channels process very large messages) then it will cause your Fargate containers to stop and get recreated. Luckily with Fargate you can control CPU and RAM independently but for EC2, you have to step up to increasingly large instance types which increase both CPU and RAM. In addition, in order for Guaranteed Message Delivery to work properly, the channel message storage setting must be set to Develo

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

Database

Amazon Relational Database Service (RDS) CPU/RAM Recommendations Basic Channels Heavy Channels Cloudwatch Logs Amazon Relational Database Service (RDS) CPU/RAM Recommendations Basic Channels Heavy Channels Cloudwatch Logs

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 User Guide

3.1.0 Upgrade Notes

A new index has been added to the message metadata table for each channel to improve queue performance . Channels created in 3.1.0 will automatically create this index, but existing channels will need to have the index created manually: Stop all channels that require the index Navigate to Settings > Database Tasks Select the "Add Metadata Index" task Select Run Task If you do not see the "Add Metadata Index" task, then the index already exists for all of your channels and there is no action needed. If the task fails to add the index for all of your channels, ensure that the remaining affected channels are stopped or undeployed and run the task again. Ensure you have enough disk space before adding the new index. The index will require roughly 45 megabytes of disk space per connector for every million messages currently stored in the database. It may take some time depending on how many messages are currently stored, so it is recommended to schedule some downtime for adding the index. P