Upload Mirth® Connect by NextGen Healthcare Docker Image to ECR

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

ECS: Create the Cluster:

Under Get Started - Create custom Container(configure). Edit Container: Provide container name Provide image, this refers to the image pushed to your ECR repository, and it has the following format: <aws_account_id>.dkr.ecr.<region>.amazonaws.com/<repository>:<tag>. Add Port Mappings 8080 and 8443 under Private repository authentication. Health Check: Provide command: curl -f http://localhost:8080/ || exit 1 Interval: 300 Timeout: 60 Start Period: 300 Retries: 3 Environment: CPU units: 1024/2048 GPUs: 1 Entry point: /entrypoint.sh Command: ./mcserver Working directory: /opt/connect Environment Variables: DATABASE=postgres KEYSTORE_STOREPASS=docker_storepass KEYSTORE_KEYPASS=docker_keypass DATABASE_URL=jdbc:postgresql://serverip:5432/mirthdb DATABASE_USERNAME= database_username DATABASE_PASSWORD= database_password STORAGE AND LOGGING Mount points: /opt/connect/appdata Log configuration: Check - "Auto-configure CloudWatch Logs" Provide Task definition details: Task definition name Networ

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

Use a Shared Keystore Across the Cluster

Upload the keystore file into S3. The file must be accessible by your ECS cluster. Note the Object URL of the file in S3. Include the following environment variables in your ECS configuration: KEYSTORE_TYPE - The type of keystore, for example, JKS. KEYSTORE_DOWNLOAD - The S3 Object URL of the Mirth® Connect keystore file. This file will be downloaded into the container and Mirth® Connect by NextGen Healthcare will use it as its keystore. ALLOW_INSECURE - Allow insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. OS and CPU/Ram recommendations - depends on research item on S,M,L and XL setups Small Medium Large ECS Task vCPU=2048, 4GB RAM vCPU=2048, 8GB RAM vCPU=4096, 16GB RAM Parent topic: Manual Steps To Setup ECS

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

Manual Steps To Setup ECS

RDS: Create the Database ECS: Create the Cluster: Install Plugins Use a Shared Keystore Across the Cluster Upload Mirth Connect by NextGen Healthcare Docker Image to ECR With these steps, you can upload docker images to your local docker repository. RDS: Create the Database ECS: Create the Cluster: Install Plugins Use a Shared Keystore Across the Cluster Parent topic: Elastic Container Service (ECS)

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

Preface and Assumptions

This document provides recommendations for Mirth® Connect by NextGen Healthcare users on how to deploy Mirth® Connect by NextGen Healthcare within their Amazon Web Services (AWS) account. This includes a set of services and configurations for those services which focus on security, durability, and efficiency. This is a high-level guide for users who have a working knowledge of AWS and a general understanding of the identified services who want examples of known tested and working infrastructure to house Mirth® Connect by NextGen Healthcare in Amazon's cloud. Networking ECS File Storage Database EC2 Elastic Container Service (ECS) Costs

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

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

ECS File Storage

When running Mirth® Connect by NextGen Healthcare in ECS, the local file system of each container is ephemeral, so certain Mirth® Connect features do not work as usual. Installing extensions, installing custom JAR files into the server-launcher-lib folder, and using a shared keystore across the cluster will not work without additional configuration. To use these features, we recommend storing the appropriate files in S3 and setting environment variables that tell the containers where to download the files from. Install Extensions Install Custom JAR Files Into the server-launcher-lib Folder Use a Shared Keystore Across the Cluster

Upload Mirth® Connect by NextGen Healthcare Docker Image to ECR

Recommendations

ECS: Create the Cluster:

Use a Shared Keystore Across the Cluster

Manual Steps To Setup ECS

Preface and Assumptions

Launch a New EC2 Instance Using This Image

ECS File Storage

Upload Mirth® Connect by NextGen Healthcare Docker Image to ECR

ECS: Create the Cluster:

Use a Shared Keystore Across the Cluster

Manual Steps To Setup ECS

Preface and Assumptions

Launch a New EC2 Instance Using This Image

ECS File Storage