A payment service supports the business growth of other companies by simplifying payments such as credit cards, debit cards, wallets, and QR codes, either online or in a physical place. Due to accelerated growth with an average of 240 million transactions annually, they need scalability and seek to improve the performance, capacity, and availability of the current application hosted on AWS using Edge Services to provide better customer service.
Analysis and redesign of the current payment solution’s architecture which does not follow the AWS Well-Architected Framework.
With the following AWS services, requests could be adequately handled, secured, and distributed with high response time to end clients:
The on-premises DNS server was migrated to Route 53 to handle all domain records. In accordance to AWS SLA, 100% service availability was leveraged.
Distributions CloudFront was configured for the frontend and backend to intercept and validate all web requests. In addition, the website was improved by its Edge Locations and static content delivery.
The input traffic balancer for the EKS cluster nodes distributes in different availability zones.
S3 stores the static website assets.
The WAF service was integrated into the CloudFront distributions to protect the frontend and backend of common web attacks and have visibility of the requests.
AuroraDB was configured globally with two nodes, one as the reader endpoint. In case of an event, the DB can failover from Region1 to Region2.
Client expectations were met with the following results standing out:
The infrastructure is scalable, and the service is stable when user demand increases. The solution is capable of sustaining load peaks through its Edge locations.
The corresponding AWS services, configured according to the client’s needs, are aligned with the best practices of high availability and performance.
Amazon CloudFront and Lambda@Edge are services that ease the implementation of the solution because of their simplicity and range of options for configuration.