Boosting Productivity, Optimizing Applications, Reducing Development Time Using AWS AML with Verisk

Verisk was founded in 1971 as a private adjunct company to insurance agencies. Since then, the company has grown into a multinational firm serving the global insurance industry with strategic data insights and risk analyses. Several years before the AWS AML project started, Verisk had taken steps toward cloud adoption, migrating from physical data centers to Amazon Elastic Compute Cloud (Amazon EC2), which provides secure, resizable compute capacity for virtually any workload; however, the cost and inflexibility associated with commercial OS licensing remained.

Despite having its data centers and applications on AWS, Verisk had not fully optimized its legacy commercial OS technology stack with all the appropriate AWS solutions to achieve ideal cost efficiency, scalability, and performance. So the company’s Casualty Solutions team connected with the AWS AML team. “The AWS AML program was our attempt at using the AWS infrastructure properly,” says Christopher Queenan, vice president of business technology at Verisk. “We wanted to learn how to increase our usage of Amazon Linux-based OSs and optimize our suite of solutions with guidance and upskilling from the AWS AML team.”

The AWS AML hands-on lab portion of the engagement took about 8 weeks to complete after the AWS AML Technical Discovery phase. Two teams from Verisk worked on the project, one strictly on the development side and the other on the DevOps side. In the first phase, the company worked alongside AWS solutions architects to dive into the existing architecture. “The AWS AML team did a great job going through a deep dive of the entire application architecture,” says Linto Mathew, assistant vice president of business technology for the Casualty Solutions team at Verisk. “We could immediately see how those initial deep-dive questions eventually led to delivering the ideal final product for us.”

After the lab completion, the team transitioned to the final phase: the AWS AML Phase 2 DIY Modernization. In this phase, the modernization of Verisk’s Liability Navigator continued through production deployment. Alongside the AWS AML team, the Verisk development team chose the solutions that it believed worked well for modernizing the legacy application. Liability Navigator was modernized to run on a serverless infrastructure using AWS Lambda, a serverless, event-driven compute service, thereby removing the need for and dependencies on commercial OSs.

Completing the migration from the SQL Server single-tenant environment to a multitenant application boosted performance tremendously. The multitenant application was powered by Amazon DynamoDB, a fast, flexible NoSQL database service for single-digit millisecond performance at any scale. With the modernized application, Verisk saw improvement in its overall productivity by staying on a single instance while serving many customers. By going serverless, the company also saved resources and improved performance.

After gleaning technical learnings using AWS AML, Verisk applied these techniques to build products from scratch using AWS technologies. In product development, it continues to use AWS Lambda and Amazon Elastic Container Service (Amazon ECS), which simplifies the deployment, management, and scaling of containerized applications. Several new products use architecture and infrastructure ideas that came out of the AWS AML project. One example is Discovery Navigator, a medical information retrieval tool, powered by natural language processing, that helps expedite insurance claim resolution. “Modernization best practices we learned through the training could be applied to real-world scenarios,” says Anilkumar Kukkal, development manager at Verisk. “We use that knowledge in our cloud center of excellence and all our current and downstream projects.”

During the AWS AML program, the Verisk DevOps team learned about the AWS Cloud Development Kit (AWS CDK), a software development framework that accelerates cloud development using familiar programming languages to model applications. Receiving sufficient training in AWS CDK, the company is now using it across many of its pipelines. Using AWS CDK in conjunction with Python, Verisk accelerated its serverless deployments. Another benefit was the time savings from the reusable frameworks that were developed during the AWS AML project. “Working alongside the AWS AML team, we built libraries that we can reuse for future application development,” says Ranjith Panakal, a technical architect at Verisk. “This has saved us a lot of time.”

After completing the AWS AML project, Verisk continued upskilling its teams and developing best practices by promoting AWS education among its workforce. Everyone who worked on the project became AWS Certified through the AWS AML program. Now, it has become an ongoing initiative for the company to add AWS Certifications each year. This initiative has boosted employee morale and engagement as the company works toward completing these training events. “AWS AML shaped our goals of attaining one new AWS Certification per year per employee. Getting AWS Certified means gaining a new mindset about new products and new solutions,” says Mathew. “We make sure these learnings benefit our individual employees and in turn the whole company.”

Experiencing the benefits of successfully modernizing its legacy commercial OS applications using AWS AML, Verisk plans to continue building and transforming its architecture with future projects. The company believes strongly that the learnings gained through AWS AML will encourage more growth and cost savings down the line.

“Using AWS AML, we can empower our employees,” says Queenan. “They gain skills and emerge with a deliverable that benefits the company. Our company wins and our employees win using AWS AML.”