Database

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

Cloudwatch Logs

View a RDS/Database Log File View an EC2 Log File View a RDS/Database Log File View an EC2 Log File 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

Heavy Channels

Note: The Advanced Clustering extension is used in all tests. The results vary greatly and in this scenario the small configurations are 1/3rd to 1/2 the power of the medium and large. The largest jump is from small to medium but, keep in mind that throughput isn't everything and the large may often be necessary if you are running hundreds of channels and need the increased multithreaded CPU power and RAM. Multi-node setups using Advanced Clustering also yield the benefit of high availability since the cluster nodes would exist in separate AWS Availability Zones (AZ) and, in a case where one AZ goes down, would continue processing messages. 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 6.37 12.23 29.97 EC2 Small Medium Large Instance Type t3.medium2vCPU/4GB m5.large2vCPU/8GB m5.xlarge4vCPU/16GB RAM 4GB 8GB 16GB Network Bandwidth Up

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

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

View a RDS/Database Log File

Open the Amazon RDS console at https://console.aws.amazon.com/rds/. In the navigation pane, choose Databases. Choose the name of the DB instance 'prod-mirthdb' that has the log file that you want to view. Choose the Logs & events tab. Scroll down to the Logs section. In the Logs section, choose the log that you want to view by clicking the radio button of the logs, and then choose View. Parent topic: Cloudwatch Logs