Ngân hàng Thương mại Cổ phần
Accelerate growth by migrating to AWS
The focus of this commercial bank project is to relocate the three most important services of the bank, enhance the robustness of the architecture, and equip the banking system with fault tolerance when incidents occur at the bank. area and automatically expand according to the increase or decrease of business needs.
Industry
Finance - Banking
Technology
Joint Stock Commercial Bank successfully
accelerated growth by migrating to AWS
A commercial joint stock bank was established in the mid of nineties with more than 200 business units spread across all regions and key economic centers across Vietnam. This bank was ranked number One in terms of profit growth rate and number Three in terms of return on capital efficiency as a joint stock commercial bank. As a result, it has been widely recognized as one of Vietnam’s leading banks that sustained good and stable growth for many years.
field:
Finance – Banking
technology:
Amazon S3
Amazon CloudWatch
AWS Control Tower
AWS Migration Acceleration Program
CUSTOMER CHALLENGE
Vietnam’s population will soon reach 100 million and nearly 80% of which are Internet users. This has created a vicious race of digitalization between banks to acquire a larger pool of customers, especially those that are tech-savvy. This bank is not only a competitor, its ambition is to lead this race. In order for this commercial bank to achieve such a rapid growth target, having a highly scalable, reliable, and cost-effective backend infrastructure is of paramount importance.
SOLUTION
Renova Cloud was entrusted with migrating this bank’s three of the most important services, including Treasury, Web of this bank, and Omni, which were previously hosted on an on-premise, legacy system. In order to choose the most plausible migration strategy for this project, Renova had spent a great amount of time and effort reviewing the business requirements, internal policies, and external regulations with constant consideration of related AWS best practices. As a result, Re-host migration strategy was chosen strategy.
Overall, the bank source workloads were migrated in 3 phases as follows:
- Setting up AWS Control Tower for Landing Zone and multi-account environment
- Perform re-host system with VM Export/Import, database backup and restore
- Implement native monitoring, logging, and backup integration for the migrated system.
Figure: The proposed architecture for the system is migrated to the AWS cloud
During the first stage, Renova started with establishing the Landing Zone by using Control Tower to implement the MVP (Minimum Viable Product) of the migration project. Simultaneously, the multi-account framework was also introduced, to which the three above mentioned services must adhere to. On the other hand, Renova employed AWS Infrastructure as Code for pre-defined and pre-approved resource deployment, which considerably helped cut down on time and resources spent on deployment tasks.
With regards to the migration stage, Renova initially recommended the use of an automated lift-and-shift solution – AWS Application Migration Service (MGN), which could have significantly reduced the complexity and duration of migration tasks. However, this would have violated the bank’s internal security policy so the proposal failed to receive final approval. As a workaround, Renova instructed the bank team to manually export and import the source workloads onto S3 to restore the servers themselves. This method was thought to be time-consuming at first but the team of this bank was already using virtualization techniques on-premise so the process took less time than expected without any issues.
Overall, the monitoring and logging approach in the bank project was centered around the Amazon CloudWatch service for infrastructure and migration. For the whole system that was migrated using the Re-host approach, most of the workloads were lifted onto EC2 instances so they would have EC2 metrics by default. With regards to logging, CloudWatch Logs were used to store live logs with the retention at 90 days as short-term storage, while for longer storage duration, Renova Cloud replied on S3 bucket using a Log Archive account. As for back-up strategy, EBS volumes were designed to have backup automatically loaded onto Vault for each EC2 instance. The storage for all back-ups was also centralized for ease of management, in which there was one short retention copy in the resource-hosting account and one replication copy in the shared-service account. In the event of backup restoration, the latest snapshot would be automatically loaded onto a new cluster. The policy used to govern the backup restoration mechanism was not rigid but rather flexible, depending on the system level, which also dictate the length of retention.
In addition, the whole bank system was founded upon multi-AZ deployment with load balancers at the forefront. In order to have this bank architecture further reinforced, Renova Cloud configured an auto-scaling mechanism for some of the applications based on the metrics retrieved from CloudWatch. All of the above equipped the bank’s system with the ability to tolerate fault against AZ outage and to scale automatically in accordance to the rise and fall of business needs.
BENEFITS
Although the client did not disclose their current spending for operating and maintaining the three source workloads, Renova believed that migrating them onto AWS offered great advantages. For instance, the bank’s team benefited from the AWS Migration Acceleration Program (MAP) in terms of receiving incentives and resources for engagement, which helped increase the pace of the bank’s migration and modernization project. In addition, AWS Credits of 25% were also applied which helped the bank’s team to cut down on the final cost, up to a certain extent. Speaking in broader terms, the migration to AWS cloud benefited this bank financially and performance-wise with greater operational excellence, faster releases, more transparency, and simpler maintenance.
