Data Sources

Data sources available for use by the ICS community

Platforms

ICS supported platforms.

Teams

ICS Teams


Menu Button Menu Button

Azure Infrastructure: REDCap PaaS Migration

This document provides a list of resource inventory that are part of the REDCap PaaS migration project. The REDCap PaaS project consist of migrating our redcap application from its current infrastructure as a service to platform as a service. The migration is made up of multiple components such as the application code hosted on an azure devops repo, virtual machines, application gateways and MySQL databases. The goal of this document is to provide an inventory of the current REDCap source inventory to what has been deployed as part of the REDCap PaaS migration project.

Redcap source architecture:

As mentioned earlier, REDCap is currently hosted on multiple azure’s platforms with its application code hosted in the azure DevOps platform see REDCap-devops-repo. Additionally, the current environment is made up of 3 different environments, DEV, QA and Prod. The current Redcap azure resources are as follow:

Virtual Machines:

  • The current Redcap virtual machines are running on an almalinux 8_5-gen2 operating system.
  • These databases are hosted within the main Subnet which is within the i2-redcap-main-vnet that is part of the ICS – Redcap Azure subscription.
  • The VM names are as follow:

i2-redcap-prod-web-vm-01

  • REDCap production virtual machines

i2-redcap-qa-web-vm-01

  • REDCap QA virtual machines

i2-redcap-dev-web-vm-01

  • REDCap development virtual machine.

i2-redcap-build-vm

  • REDCap POC virtual machine

Source Database Servers:

  • The Current REDCap database servers consist of Azure MySQL Flex v5 servers.
  • These databases are hosted within the mysql-flex Subnet which is within the i2-redcap-main-vnet that is part of the ICS – Redcap Azure subscription.
  • The MySQL database servers are as follows:

i2-redcap-prod-mysql-flex - To be decommissioned

  • REDCap production database server.
  • The current database has 32 vcores and has 64GiB of memory.
  • It has a storage capacity of 1024 GB and 10,000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 6 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. customer_service: User database that holds information about projects.
    6. redcap_appp60m1: Database that stores REDCap production data.
  • We are currently paying $1639/month to maintain it.
  • The database will be decommissioned once REDCap production data is migrated to the new V8 database.

Redcapv7-prod-restore-backup-host - Decommissioned on 12/14/24

  • REDCap production database server that served as replication testing from onprem to MySQL flex.
  • The current database has 32 vcores and has 64GiB of memory.
  • It has a storage capacity of 1024 GB and 10,000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. customer_service: User database that holds information about projects.
    6. redcap_appp60m1: Database that stores REDCap production data.
    7. redcap_prod: User database that was used during the replication testing
  • We are currently paying $1639/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

i2-redcap-dev-flex-mysql-02 - Decommissioned on 12/14/24

  • REDCap development database server.
  • The current database has 4 vcores and has 16GiB of memory.
  • It has a storage capacity of 1024 GB and 6,400 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. customer_service: User database that holds information about projects.
    6. redcap_appd87m1: Database that stores REDCap development data.
    7. redcaptestdb: User database that holds obsolete data.
  • We are currently paying $581.82/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

i2-redcap-dev-flex-mysql - Decommissioned on 12/14/24

  • REDCap inactive development database server.
    The current database has 4 vcores and has 16GiB of memory.
  • It has a storage capacity of 1024 GB and 3,372 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. customer_service: User database that holds information about projects.
    6. redcap_appd87m1: Database that stores inactive REDCap development data.
    7. redcap_prod: User database that holds inactive and obsolete REDCap production data.
  • We are currently paying $412.22/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

i2-redcap-migr-mysql - Decommissioned on 12/14/24

  • Temporal and obsolete development database server that was created for migration purposes.
  • It has a storage capacity of 1024 GB and 6,400 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 8 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. customer_service: User database that holds information about projects.
    6. redcap_appo27m1: Database that stores inactive and obsolete REDCap data.
    7. redcap_apppp60m1: Database that stores inactive and obsolete REDCap data.
    8. redcap_prod: User database that holds inactive and obsolete REDCap production data.
    9. tmp_wt: Database that stores inactive and obsolete REDCap data.
  • We are currently paying $587.22/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

redcap-poc-mysql - Decommissioned on 12/14/24

  • Temporal and obsolete poc database server that was created for poc purposes.
  • It has a storage capacity of 64 GB and 1000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 5 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. redcap_poc: User database that holds inactive and obsolete REDCap poc data.
  • We are currently paying $157.59/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

redcap-qa-mysql-flex Decommissioned on 12/14/24

  • REDCap QA database server.
  • The current database has 4 vcores and has 16GiB of memory.
  • It has a storage capacity of 512 GB and 2,000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
  • It currently has 5 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. customer_service: User database that holds information about projects.
    5. sys: system database that stores system views, functions, and procedures.
    6. redcap_appq32ma: User database that holds QA REDCap Data.
  • We are currently paying $358.01/month to maintain it as well.
  • The database will be decommissioned once REDCap data migration is completed to the new V8 database.

Source and Target Database Credentials:

  • Below are the links to the azure keyvault secrets that currently store both the v5(source) and v8(target) REDCap database server credentials.

Dev Database Credentials:

i2-redcap-dev-mysql-admin-password Decommissioned on 12/14/24.
  • This i2-redcap-dev-mysql-admin-password secret stores REDCap development database admin (i2admin) user password.
i2-redcap-dev-mysql-svc-passwordDecommissioned on 12/14/24.
  • The i2-redcap-dev-mysql-svc-password secret stores REDCap development database application (redcap_svc) user password
i2-redcap-dev-v8-mysql-password
  • This i2-redcap-dev-v8-mysql-password secret stores REDCap development v8 database admin (i2adminv8) user password.
i2-redcap-dev-v8-mysql-svc-password
  • The i2-redcap-dev-v8-mysql-svc-password secret stores the REDCap development v8 database application (redcapv8svc) user password.

QA Database Credentials:

i2-redcap-qa-mysql-admin-password Decommissioned on 12/14/24.
  • This i2-redcap-qa-mysql-admin-password secret stores REDCap QA database admin (i2admin) user password.
i2-redcap-qa-mysql-svc-password Decommissioned on 12/14/24.
  • The i2-redcap-qa-mysql-svc-password secret stores REDCap QA database application (redcap_svc) user password.
i2-redcap-qa-v8-mysql-password
  • This i2-redcap-qa-v8-mysql-password secret stores REDCap QA v8 database admin (i2adminv8qa) user password.
i2-redcap-qa-v8-mysql-svc-password
  • The i2-redcap-qa-v8-mysql-svc-password secret stores REDCap QA v8 database application (redcapv8svc) user password

Prod Database Credentials

i2-redcap-prod-mysql-admin-password Decommissioned on 12/14/24.
  • This i2-redcap-prod-mysql-admin-password secret stores REDCap production database admin (i2admin) user password.
i2-redcap-prod-mysql-svc-password Decommissioned on 12/14/24.
  • The i2-redcap-prod-mysql-svc-password secret stores REDCap production database application (redcap_svc) user password
i2-redcap-prod-v8-mysql-admin-password
  • This i2-redcap-prod-v8-mysql-admin-password secret stores REDCap production v8 database admin (i2admin) user password.
i2-redcap-prod-v8-mysql-svc-password
  • This i2-redcap-prod-v8-mysql-svc-password secret stores REDCap production v8 database user (redcapv8svc) user password.

Target Database servers:

The Current target REDCap database servers consist of Azure MySQL Flex v8 servers. These databases are hosted within the mysql-flex Subnet which is hosted within i2-redcap-main-vnet that is part of the ICS – Redcap Azure subscription.

i2-redcap-dev-v8-flex

  • REDCap development v8 database server.
  • The current database has 4 vcores and has 16 GiB of memory.
  • It has a storage capacity of 1099 GB and 6,400 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. redcap_appd87m1: New V8 database that stores REDCap development data.
      • The database has gone live and the REDCap dev application is pointing to this database.
  • We are currently paying $584.74/month to maintain it as well.

i2-redcap-qa-v8-flex

  • REDCap QA v8 database server.
  • The current database has 4 vcores and has 16 GiB of memory.
  • It has a storage capacity of 1099 GB and 4,000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 7 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. redcap_appq32m1: New V8 database that stores REDCap QA data.
      • The database has gone live and the REDCap QA application is pointing to this database.
  • We are currently paying $447.94/month to maintain it as well.

i2-redcap-prod-v8-flex

  • REDCap production v8 database server.
  • The current database has 32 vcores and has 128 GiB of memory.
  • It has a storage capacity of 1600 GB and 14,000 Max IOPs
  • It is backed up daily and has a retention period of 30-days.
  • It currently has 5 databases running on it, the databases are as follows:
    1. information_schema: System Database that allows users to query metadata about database.
    2. mysql: System database where user information are stored.
    3. performance_schema: System database that monitors performance and resource usage.
    4. sys: system database that stores system views, functions, and procedures.
    5. redcap_appp0m1: New V8 database that stores REDCap prod data.
      • The database has not yet gone live,however, the current REDCap production database is replicating data to this data.
      • The schedule go live data is November, 7th, 2024
  • We are currently paying $2972.94/month to maintain it as well.
    • it will be downsized pre-go live to save on cost.
    • The compute is needed to avoid replication disruptions.

Keyvault Certificates

The current REDCap keyvault certificates consists of multiple SSL certificates for our development, QA and Production environments together with certificates for the application gateway. Additionally, there are a few database certificates that can be used to connect to the databases when SSL is enabled. However, the current REDCap database and REDCap application only communicate within Washington University’s virtual network interface (i2-redcap-main-vnet). Below is a list of a few certificates within the REDcap keyvault certificates:

i2-redcap-dev-gateway-cert

  • The i2-redcap-dev-w-cert keyvault certificate stores the SSL certificate for the REDCap development application gateway.

i2-redcap-qa-app-cert

  • The i2-redcap-qa-app-cert keyvault certificate stores the SSL certificate for the REDCap QA application gateway

i2-redcap-prod-gateway

  • The i2-redcap-prod-gateway keyvault certificate stores the SSL certificate for the REDCap production application gateway.

i2-redcap-prod-web-vm-01

  • The i2-redcap-prod-web-vm-01 keyvault certificate stores the SSL certificate for the REDCap production virtual machine.

Application Gateways

The current REDCap architecture consists of multiple application gateways that directs traffic to the REDCap virtual machines. There are currently three application gateways in the within the ICS – Redcap Azure subscription subscription, the three application gateways are as follows:
i2-redcap-dev-gateway - Microsoft Azure

  • The i2-redcap-dev-gateway is currently used to route traffic to the i2-redcap-qa-web-vm-01 virtual machine that currently host the redcap development application.
  • This application gateway is currently fronted by https://redcapdev.wustl.edu/
  • The goal is to replace the virtual machine with an azure application service.

i2-redcap-qa-gateway - Microsoft Azure

  • The i2-redcap-qa-gateway is currently used to route traffic to the i2-redcap-qa-web-vm-01 virtual machine that currently host the redcap QA application.
  • This application gateway is currently fronted by https://redcapqa.wustl.edu
  • The goal is to replace the virtual machine with an azure application service.

i2-redcap-prod-gateway - Microsoft Azure

  • The i2-redcap-prod-gateway is currently used to route traffic to the i2-redcap-prod-web-vm-01 virtual machine that currently host the redcap dev application.
  • This application gateway is currently fronted by https://redcap.wustl.edu.
  • The goal is to replace the virtual machine with an azure application service.

Table of Contents

Updated on August 12, 2025