未加星标

Case Study: A dual migration across AWS & Azure.

字体大小 | |
[系统(windows) 所属分类 系统(windows) | 发布者 店小二05 | 时间 2018 | 作者 红领巾 ] 0人收藏点击收藏

Written by Ayush Ragesh , Cloud Solutions Architect at Powerupcloud.


Case Study: A dual migration across AWS & Azure.
Problem Statement

The client is a global pioneer and leader providing end-to-end gifting solutions and manage 260Mn+ transactions a year. With over 15000 points of sale across 16 countries, they needed to migrate their platform from an on-premise datacentre to the cloud. In addition, they needed to ready and scale-able for one of the largest e-commerce sales in the country.

Powerup’s approach:

As determined with the client it was decided to host their primary DC on AWS and DR on Azure.

Architecture Diagram
Case Study: A dual migration across AWS & Azure.
Architecture Description The applications were spread across multiple VPCs which are connected to each other via VPC peering. Different VPCs for UAT, Management Production etc. VPN tunnels are deployed from client’s Bangalore location to AWS and Azure environment. Multiple Load Balancers are used to distribute traffic between different applications. NAT Gateways are used for Internet access to private servers. Cisco Firepower/Palo Alto as the firewall. CloudFormation for automated deployments on AWS. Cloudtrail for logging and KMS for encryption of EBS volumes and S3 data. Config for change management. Route53 is used as the DNS service. Guard Duty and Inspector will be configured for additional security. DR site will be deployed on Azure. Outcomes

*Powerupcloud was able to successfully migrate the core for their largest client on AWS.

*The client was able to achieve the required scalability, flexibility and performance.

*The e-commerce sale day was a big success with zero downtime.

Lessons Learned

The customer initially wanted to use a Cisco Firepower firewall for IDS/IPS, DDOS etc.SSL offloading needs to be done in the application server. So we decided to use Network Load Balancers. Instance-based routing was used so that the source IP addresses are available at the application server. The firewall needed 3 Ethernet cards for ‘trust’, ‘untrust’ and ‘management’.

In Cisco, by default, the eth0 is mapped management and we cannot change this. In Instance-based routing, the request always goes to eth0 while the request should go to ‘untrust’.

So we finally had to use a Palo Alto firewall where we can remap eth0 to ‘untrust’.

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

tags: The,client,was,AWS,used,Azure,firewall
分页:12
转载请注明
本文标题:Case Study: A dual migration across AWS & Azure.
本站链接:https://www.codesec.net/view/586963.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(55)