AWS Migration and Transformation of a Diagnostic Product

Our client asked us to complete the cloud migration of their services for ongoing scalability and simplified IT maintenance.


AWS Migration and Transformation of a Diagnostic Product

Health Cloud Solution

.NET, REactJS, AWS, Docker, Terraform, GitLab

Technology and Tech Stack - Case Study Icon

4 Months

Project Duration - Case Study Icon


Our client was a fast-growing, FDA-approved diagnostic product start-up. Their IT infrastructure was costly and complex to maintain. They ran it on the Kubernetes cluster, a suboptimal solution due to the rising maintenance costs. That is why they asked us to deliver AWS migration services.

Our client lacked the expertise to develop cloud migration solutions while remaining HIPAA compliant.

Because they built their services as monolithic, they suffered many potential business risks. Additionally, the lack of dev-stage and automation slowed their deployment to production.

Case Study, AWS Migration and Transformation of a Diagnostic Product , Diagram


We developed the initial product as on prem solution. After careful consideration, we outlined the key features of AWS cloud migration strategy: scalability, maintenance, and ease of use. The goal was to utilize serverless computing as much as possible (moving from servers to containers and from containers to functions) while also maintaining all the necessary compliances. Our cloud migration strategy was the optimal solution for the client’s needs.

Due to the complexity of the initial system, there were several necessary steps we needed to take to complete the process of migration and restructuring for the AWS migration.

  • The existing stack was moved to Amazon EKS (Elastic Kubernetes Service) cluster
  • EKS was transformed to ECS (Elastic Container Service)
  • Containers were transformed to Lambda functions (wherever possible)
  • Infrastructure deployment was automated via code

To achieve fast deployment to the market, we opted to start with a simple “lift and shift” followed by additional optimization and re-architecting.

In the first phase of the delivery of AWS migration services, we used single Fargate containers with network load balancers and S3 buckets and databases. Upon moving all the code repositories into the cloud environment, we broke down all the infrastructure into smaller pieces. We’ve also automated all the builds/deploys via pipelines to reduce complexity.

By eliminating containers and replacing them with functions that perform the same tasks, we’ve drastically reduced the price of operations for the client. Our AWS migration moved the complex multi-repo projects to self-contained mono-repo services with no outside dependencies. We moved all stages to cloud infrastructure and removed locks to specific code editors, operating systems, and shells. We built everything as agnostic as possible with regards to the tooling selection.


Monolithic services carried a great deal of risk pertaining to the running of our client’s operations. By implementing the AWS cloud infrastructure, we’ve eliminated all associated risks. We decreased the client’s costs by 98% percent, and all subsequent expenses were based on product sales.

By utilizing services like AWS Lambda, advanced automation capabilities are now possible – resulting in savings, faster and simpler deployment, and higher reliability. Additional benefits of cloud migration include:

  • Increased security
  • Reduced risk of interrupted operations
  • Significant cost reduction
  • AWS cloud migration improved the overall operations of our client and found ongoing applications in the future