Loading...
Recommendations
Explore
View an EC2 Log File
Open the Amazon RDS console at
https://console.aws.amazon.com/ec2/
.
Click
Running Instances
to view list of running EC2 instances.
In the list of running EC2 instances, select EC2 instance(s) which is running connect application by clicking Instance ID.
In the
Instance
section, copy the
Private IPv4 addresses
.
Login to EC2 instance by doing SSH.
Example:
> ssh i "rocksolid.pem" ec2
user@10.10.10.20
Once the login is successful, go to directory 'connect'
Execute
>cat logs/mirth.log
View an EC2 Log File
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
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
Install Mirth® Connect on the EC2 Instance
SSH into your newly created EC2 instance using your key pair. Edit the mirth.properties file to point to the RDS database that you created in a previous step. In the terminal, enter the following: EC2 Terminal Window $ wget http://downloads.mirthcorp.com/connect/3.11.0.b2609/mirthconnect-3.11.0.b2609-unix.tar.gz$ sudo yum update$ sudo yum install -y java-11-amazon-corretto-devel$ tar -xzf mirthconnect-3.11.0.b2609-unix.tar.gz$ cd "Mirth® Connect"$ cat docs/mcservice-java9+.vmoptions >> mcserver.vmoptions$ echo "server.id.ephemeral = true" >> conf/mirth.properties$ . /mcserver & Parent topic: Single EC2 Instance
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
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
Using Docker Images
With this topic, you can download Docker images and launch instances in Mirth® Connect. Supported Architectures Docker images for Mirth® Connect 4.6.0 and later versions support both linux/amd64 and linux/arm64 architectures. Download a Connect instanceThere are two methods for loading a Mirth® Connect image into your local Docker repository. Log on to Mirth® Connect Command Center, navigate to the Docker Dashboard from the Main Side Menu, and follow the instructions for getting a token and pulling the desired image. Download a Docker image file from the Success Community, and then load it into your repository using the following command: docker load -i FILENAME.tar.gz Start a Connect instance Quickly start Connect using embedded Derby database and all configuration defaults. At a minimum you will likely want to use the -p option to expose the 8443 port so that you can login with the Administrator GUI or CLI: docker run -p 8443:8443 -e _MP_LICENSE_KEY='0000-00000000000-000000000-000000
