11 / CLOUD / SUCCESS STORY

Digital-first insurer moves its policy platform to containers on AWS with Azure services for digital channels

A digital-first insurer moved from a monolithic policy platform to microservices on AWS, with Azure services for digital channels — and cut the time needed to launch and change products.

CLIENT SNAPSHOT

Digital-first general insurer · India-first, expanding to Southeast Asia · Growing product catalogue with monthly releases · Web, mobile and partner channels

HEADLINE RESULTS

What changed in production.

001Independent releases per service, monthly platform release cadence retired
002Faults contained to one service instead of affecting the whole platform
003Compute scales with renewal and campaign peaks, then scales back
00440% reduction in infrastructure cost through elastic scaling
01 / THE CHALLENGE

Where the pressure started.

One large application handled quotes, policy issue, endorsements and claims. Any change meant a full release, and a fault in one module could slow the entire platform. Infrastructure was sized for peak renewal periods and sat idle the rest of the year. Digital channels were being built on Azure by a separate team, and the two sides needed a clean way to talk to each other.

02 / WHAT WE DID

Designed for the real operating environment.

  • Designed a container platform on Amazon EKS with separate network zones for customer-facing, internal and data services.
  • Put Amazon API Gateway and load balancers in front of services, with private connectivity to partner and payment systems.
  • Split the monolith into services in phases, starting with the highest-change modules.
  • Automated build, test and deployment pipelines through AWS CodePipeline and infrastructure defined as Terraform code.
  • Moved service databases to Amazon RDS and Amazon Aurora with backup, patching and monitoring built in.
  • Connected the Azure-hosted digital channels through Azure API Management to the AWS platform over private links.
03 / OUTCOMES

The result is more than a platform.

↗ Independent releases per service, so product changes ship without a full platform release.
↗ Faults stay contained to one service instead of affecting the whole platform.
↗ Capacity scales with renewal and campaign peaks, then scales back.
↗ A repeatable infrastructure pattern that works across AWS and Azure.
↗ Product, engineering and infra teams working on shared, documented interfaces rather than bespoke integrations.
TECHNOLOGY STACK

Built on proven enterprise foundations.

Amazon EKS · Amazon RDS · Amazon Aurora · Amazon API Gateway · AWS CodePipeline · Terraform · Azure API Management · Azure Front Door · AWS Direct Connect · Azure ExpressRoute

← Back to Success StoriesDiscuss a similar challenge ↗