Inofab Health migrates to AWS with Commencis for increased scalability
and reliability

Inofab Health

"We needed an expert partner with significant experience in complex AWS migration and modernization projects. The expertise of Commencis helped us successfully navigate our AWS journey and design a robust and secure solution."  


Ersin Yılmaz - Director of Digital Operations at Inofab Health

About Inofab Health

Founded in 2014, Inofab Health is a startup focusing on creating digital health platform solutions for patients of Asthma, COPD, Cystic Fibrosis patients and respiratory health enthusiasts. The company offers revolutionary respiratory care solutions for home and professional use with a human-centric approach and cutting-edge technology. It provides a software platform for functional respiratory care management, state of the art ultrasonic personal & clinic spirometers along with connected inhaler attachments with a strong focus on misuse detection. Inofab Health alerts any declines in lung health, allowing quick intervention against symptom onset and prevents unnecessary hospitalizations.

Business Challenge

Healthcare organiations as like InofabHealth seeking a flexible and secure strategy for storing and accessing their data assets are increasingly turning to cloud modernization.In this case, since the customer’s database contains critical health metrics of Inofab Health customers, this Project should be complated without any interruption.In order to complete this critical Project, they did not have the technical knowledge to modernize their applications and database by applying best practice on AWS.


The first important thing is that application logic implemented in EC2 server managed by AWS Elastic Beanstalk which component meet the constantly on the lookout for software and services that will help us quickly and reliably build out these new solutions. In this project, we used AWS Elastic Beanstalk to manage the web servers that power SaaS projects. Specifically, these are two dynamic web-based platforms that power internal innovations and creativity. It’s a great service that allows Inofab to deploy web applications without having a lot of in-house DevOps expertise. There are two reasons why Elastic Beanstalk needs to use in Inofab DevOps expertise side.

– Scalability: Whether it is scaling in or scaling out, scalability is an indispensable prerequisite of efficient cloud infrastructure. Inofab Health can achieve it by making the most of cloud elasticity, which means that they are able to easily acquire or release resources depending on their requirements. If configured properly, Elastic Beanstalk leverages cloud elasticity by automatically scaling up or down, in response to a specific situation based on resource metrics from their environment. Autoscaling functionality allows Inofab to vary capacity against usage fluctuations.

– Fault-Tolerance:  When designing Inofab software that is to be deployed in the cloud, the key is to foresee possible outages and aberrations and make an app ready to withstand them. That is why Inofab developers should always consider automatic failover and design, implement and deploy having this consideration in mind.

To summarize, Commencis DevOps team used AWS Beanstalk for our Client Inofab Health, we can quickly deploy and manage their applications in the AWS cloud without sizing of infrastructure that runs those applications.AWS Elastic Beanstalk reduces management complexity without restricting choice or control. We simply upload customer application and Elastic Beanstalk will automatically handle the details of capacity of provisioning, load balancing, scaling and application health monitoring.

The second significant point of view, reliability automates the deployment process and many businesses choose the service over it. Commencis got the chance of helping to Inofab building CI/CD pipeline using AWS CodePipeline for DevOps expertise side. We sat with our client and discussed their issues that forced them to take the path of digital transformation. The Inofab Health scaled so rapidly that build and deploy codes faster with less legroom for bugs. Stable build, automated testing and monitoring and automated deployment were the things that the Inofab wanted. After a detailed discussion, we identified two things that needed to be done:

– Building a CI/CD pipeline using AWS CodePipeline.Since much of the work of Inofab is done online, it appeared prudent to take the help of AWS as opposed to Jenkins since the latter would have needed a physical server as well. With AWS, everything happens on cloud.

– With CI/CD pipeline in place, the next step should be ensuring an efficient, continuous, automated deployment process.

We employed DevOps best practices and built an end-to-end pipeline for Inofab Health. Let’s dive deeper and see what exactly we did:

– As already decided, we took the help of AWS CodePipeline to create Inofab’s continuous integration and continuous deployment pipeline.

– In order to have seamless integration with other AWS services, we migrated the Inofab’s software codes from Bitbucket to AWS CodeCommit. One additional benefit that the company got by opting for Code Commit is having a free private repository up to 50 GB.

– Again, in order to have synchronicity in the pipeline, we used Amazon’s CodeBuild to build and test the codes. As an added advantage the client got the option of pay per minute CodeBuild.This proved to be a great cost-efficiency strategy.

– The great thing about AWS is it provided every DevOps solution, making the deployment a wholesome process without relying on third-party resources. Also, Cloudwatch is used in this project. We used it to monitor various AWS resources.

In this way, we complimented AWS CodePipeline by using other AWS Services and created a stable end-to-end Continuous Integration and Continuous Deployment pipeline.

Outcomes & Benefits

– Till now we had not calculated ROI as the Project is still evolving and we had to keep on changing the environment implementation. It meets our purpose of quick deployment as compared to previous deployment experience.

– Until now we look good as we also controlled our expenses which increased suddenly in the middle of deployment activity. Deployment time was significantly reduced. The time gap between putting the code in Code Commit and deploying it was only around two minutes comparing the previous experience.

– By using other AWS services like Code Commit, Code Deploy. we are able to automate the entire deployment process for the devops expertise side.

– With continuous integration and the subsequent automated build-test sequence, the developers were able to reduce bags and increase the quality of codes before actual deployment.

– With an automated build-test sequence, the hiccups during deployment are greatly reduced. Failed tests were not allowed to pass to the deployment phase.

– Avoid repetitive tasks like setting up environments.

– Reduced extra human resources (devops/developers) and increased automation processes with the use of AWS Codepipeline.

– Inofab reduced costs as a result of adopting cloud technology is reinvesting the saved money back into their business

Let’s start your cloud journey
Get in Touch