AWS Qualification

xLM for TestOps - Continuous Qualification for AWS/Azure

xLM for TestOps - Continuous Qualification for AWS/Azure

Many life-science companies are asking the question “Can I move my GxP workloads into the public cloud?” Answering “yes” to this question leads to another question: “What toolset do I need to qualify the various IaaS/PaaS services that are constantly changing?”.

Our customers are leveraging our robust framework that we call TestOps. TestOps provides an end to end automation for continuously qualifying any IaaS/PaaS service running on AWS or Azure.

xLM for DevOps - Introducing vCD (Validated Continuous Delivery)

xLM for DevOps - Introducing vCD (Validated Continuous Delivery)

The main objective of this post to answer the following questions.  I know a picture is worth a thousand words and so I will do this with illustrations.

  1. Can "Validation" and "DevOps" be used in the same sentence (like vCD - Validated Continuous Delivery)?

  2. Is DevOps a viable model for validated apps in GxP Environments?

  3. How can one ensure the "validation fidelity" in a DevOps environment?

Continuous Qualification for AWS or Microsoft Azure - How is it done?

Continuous Qualification for AWS or Microsoft Azure - How is it done?

The question is "Can Amazon AWS or Microsoft Azure be qualified so that I Life Science companies can run validated apps on it?"   

Cloud releases updates and changes at such great velocities that leaves all validation specialists continuously wondering on how to qualify it.  Traditional strategies including GAMP 5 was never designed to address continuous changes.  These models were designed for a "waterfall" world and not an "agile" one.  It is not possible to qualify an infrastructure where changes are released without release notes with such an outdated mindset and toolset.