Private Cloud Infrastructure

The Private Cloud is a customer-specific, fully managed hosting solution that offers a turn-key ELN solution for any organization. The Private Cloud is hosted in an AWS (Amazon Web Service) Cloud chosen by the customer. The AWS Cloud infrastructure is built around Regions and Availability Zones (AZs). AWS Regions provide multiple, physically separated, and isolated Availability Zones that are connected with low latency, high throughput, and highly redundant networking. These Availability Zones offer AWS customers an easier and more effective way to design and operate applications and databases, making them more highly available, fault-tolerant, and scalable than traditional single datacenter infrastructures or multi-data center infrastructures. You can find the availability of an AWS Cloud in your region here.

Private Cloud Architecture

The application encompasses a multi-server architecture that collectively offers all functionalities as available in the Cloud. Multi-server setups allow for optimal application performance and scalability. Customer end-users login to eLabJournal to a customer-specific URL (e.g. https://customername.elabjournal.com). Note that the application and database server are separated (either physically or virtually). The use of the Office Online Server is optional and licensing should be handled by the customer in the Microsoft Office365 license plan. The architecture of the Private Cloud also provides the option to only make the application available within the organization’s IP range alone.

High Availability Private Cloud

eLabJournal ELN can also be deployed as a High Availability (HA) system installation. In the HA Private Cloud installation, a duplicate system installation is configured and hosted in a physically different AWS Cloud data center. Data is replicated in real-time to both systems and traffic is automatically routed by a load balancer to both installations. In case of an event in one of the AWS Cloud data centers that results in downtime of one of the servers (e.g. power failure in a data center, fire, natural disasters, etc.), system uptime is unaffected as this server is taken out of the cluster and all communication is automatically diverted to the available server. A third database server is configured which can be used for API calls, back-ups, reporting, and exporting. The HA installation is typically used for large system installations (> 500 active users) but is also available for customers that require the highest possible uptime with more than 99.9%.

 

Security

Security is a major concern to organizations choosing a managed hosted Cloud ELN solution. eLabNext is a brand of Bio-ITech BV, part of Eppendorf group. Bio-ITech is certified for ISO/IEC 27001 since 2016 and implemented all generally accepted measures for cloud hosting security. In addition, eLabJournal supports all required security features to enforce system security. An overview of all Bio-ITech security measures and eLabNext products’ security features can be found here. We exclusively use AWS Cloud (Amazon) for hosting of Private Cloud installations in SOC II compliant data centers. You can find more information about Amazon Security here.

Get started with eLabNext today

Personal demo, free lab workflow assessment, and friendly expert guidance.