Introductions:
Easypolicy.com was created to provide transparent and top-notch services through technology to simplify, advise, inform, educate, and make insurance more accessible and available across India. The company is an insurance comparison website holding a web aggregation license from IRDAI (Insurance Regulatory and Development Authority of India). Being one of the fastest-growing Insurance aggregators, the Customer was expecting increased traffic on the application, and the current deployment on-premise was not conducive to handling high loads for a short time.
Business Need:
The Customer wanted to be cloud-ready with scaling capability to use at an appropriate time. Easypolicy.com was also looking for a near DR option on AWS to prevent any unforeseen disruption in business.
To address some of these challenges, Rapyder proposed the below Architecture keeping in mind the Best Practices and Business Continuity.
AWS Services
EC2, S3, CloudWatch, Config, VPC, Lambda, CloudTrail, Systems Manager
Third-Party Services
Microsoft SQL Standard 2016 Version: 13.0.5337.0, Glasswire Version 2.1.58
Solution Approach
- All the servers have been launched in a private subnet so that the servers are not exposed to the public directly.
- High availability has been factored in, and servers have been launched in HA mode across availability zones.
- Bot Application is set up on different servers to be used along with the Application layer.
- SQL Server is set up in HA mode across availability zones using Mirroring.
- SQL Server Standard 2016 is used as the database layer.
- Replication for the Database has also been configured using Log Shipping technique to On-Premise for local Reporting and analytics over a secured AWS Managed VPN.
- Native Backups with Full, Differential, and Transactional Log backups are enabled with AWS Backups such as AMI; Snapshots are also taken daily.
- Failover of the DB has also been tested by leveraging Route53 private hosted zone with Lambda, which is configured to update the DNS in case of failover.
- AWS Config has also been enabled to monitor and record resource configurations.
- Failover of the DB has also been tested by leveraging Route53 private hosted zone with Lambda, which is configured to update the DNS in case of failover.
Reaping Rewards
- Today, the migrated workloads are running successfully on AWS without any downtimes.
- After successfully implementing the solution, the client has achieved 99% application availability on Cloud.
- Applications response time has improved.
Next Case Study: Read how Rapyder migrated a Ride-Sharing Startup from GCP to AWS
Keep up to date with the latest Case Studies and Stories from Rapyder. Sign-up for our Monthly Newsletter here.
