Synopsis :CompanyC is an automobile insurance claim processing company, with an external-facing website from which claims are received and processed. A backend processing pipeline processes the claims by connecting to a complex workflow of third party services, legacy systems, content management systems (CMS), and reporting databases. The company maintains an internal back-office portal (Intranet) for Adjusters and Supervisors to manage the end-to-end workflow of processing claims.
CompanyC needed a solution that would enable them to:
· Reduce its IT infrastructure investment and cut costs by lowering the total cost of ownership
· Scale on-demand servers without having to provision for peak capacity due to the sunk costs associated with purchasing additional servers upfront
· Implement a low-cost highly reliable Disaster Recovery Solution for its mission-critical claim processing infrastructure by using “Availability Zone” feature of EC2
The company was slightly skeptical of moving their mission critical claims processing system all at once into the cloud, and decided to first leverage the business continuity benefits of the cloud, and then migrate the entire infrastructure into the cloud.
Agenda : The agenda of this case study is:
· CompanyC, an Automobile Insurance claim processing company – Current Scenario
· Application Architecture (before migration)
· Need for Migration
· Migration Plan, Strategy, & Execution Steps
· Application Architecture (after migration)
· Conclusion
· Demo - Migrating Backend Processing Pipeline to the AWS Cloud
_CC638203878343937016_.png "AWS Certified Security – Specialty (SCS-C01) Training & certification")
_CC638198072654005721_.png "Cloud Security Practitioner Training & Certification")
