Customer Success Story - A SaaS Startup

---

Briefing Session

• Customer did not have the bandwidth, resources to create any sort of documentation, C-level diagrams for overview.
• Customer is facing hardships on clearing clients compliance requirements.
• Customers are stressing security at application and infrastructure level as a focus point over the sales conversations repeatedly.
• We got some fair understanding on the current framework from Application and Infrastructure perspective driven one of their leads.
• Data is sensitive, so rest and moving has been critical

Infrastructure Stack

• EC2
• Lambda
• RDS-MySQL

Gap Analysis:

Initially, we got limited information and with that, we could create fair understand at cloud resource level

We understood  end-to end operations flow and created a gap analysis reports from the point of view of Modernisation, Performance, Security and Costing.

Implementation Phase 1:

• Created some native services of AWS for security and created a security score which lists the basic vulnerabilities
• Created an impact review process document on what changes are needed and impact they can create.
• We delivered a C3-level diagrams for customer's understanding.
• As it the product is a customer is facing application,  a monolithic and standalone, we went through and created below to reduce security and performance risk as an immediate step.

Backups 

• AWS backup service

High Availability 

• load balancer
• AMI creation on current setup and used the same for auto-scaling as this is a high-cpu consumed application

Security 

• Implemented Web Application Firewall and fine tuned rules
• Network level ports blocked. Hardened the application environment and network

CI-CD

• Customer was using AWS code commit earlier so we strengthened a basic branching strategy and created a code pipeline and code deploy

Internal Security

• Strengthened on-prem setup using firewalls and VPN service inclusion to protect data, ownership etc.,

Cost Optimisation

• Identified issues in branching and environments deployment in a wrong way.
• Fine tuned with Dev environment into hybrid model so Dev env cost is minimised too negligible

Phase 2 is Under progress

In this phase, we emphasise on containerising the application and moving away from VMs to reduce operational burden. This ensures the customer leverages serverless architecture that is available from cloud service providers.