Install Custom JAR Files Into the server-launcher-lib Folder

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_DOWNLOAD - The S3 Object URL of the Mirth® Connect keystore file. This file will be downloaded into the container and Mirth® Connect will use it as its keystore. ALLOW_INSECURE - Allow the insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. Parent topic: ECS File Storage

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

Install Extensions

Create a zip file containing all the extension zip files that you wish to install. Upload the created zip 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: EXTENSIONS_DOWNLOAD - The S3 Object URL of the zip file containing the extensions. This file will be downloaded into the container, and the extensions will be installed on the Mirth® Connect server. ALLOW_INSECURE - Allow insecure SSL connections when downloading files during startup. This applies to keystore downloads, plugin downloads, and server library downloads. Parent topic: ECS File Storage

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

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

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

Install Plugins

See ECS File Storage Parent topic: Manual Steps To Setup ECS

Install Custom JAR Files Into the server-launcher-lib Folder

Recommendations

Use a Shared Keystore Across the Cluster

Install Extensions

ECS File Storage

Use a Shared Keystore Across the Cluster

ECS: Create the Cluster:

Install Plugins

Install Custom JAR Files Into the server-launcher-lib Folder

Use a Shared Keystore Across the Cluster

Install Extensions

ECS File Storage

Use a Shared Keystore Across the Cluster

ECS: Create the Cluster:

Install Plugins