 So I'm Chaitra Acharya, I'm the lead SRE at the Economist Intelligence Unit. So I'll be giving talk on lessons from the migration of Microsoft and Windows-based application. So I'll just go to the legacy side of the migration. So how our applications are made is, so legacy.NET applications like 3.5, and we are now evolving and moving to .NET core and AWS-based and Microsoft-based applications and moving there. So in 2018, our entire infrastructure was maintained by on-premise, and then we decided to move to the cloud-based application, so which was so hectic because it's a legacy-based application, and SQL 2008 we were running, and we had to do a migration and think about all the dependencies that took like since 2000, and then entire 10 years of migration it was hectic, and so it's a small talk and what were the decisions? So behind moving AWS, and there were like three initiatives that we took, business initiatives and partner selection and application architecture. Though the monitoring and alerts, so those are managed by our Cloud Service Provider, but still, so we have a DevOps team and we entirely take care of all the AWS infrastructure, and I'll talk about the major learnings of after moving to AWS. So just think that when you migrate to anything any cloud-based infrastructure, so not just migrating to the AWS is end of your journey, so re-eventing your infrastructure and make it easy, secure, scalable by accessing the deep set of tools, and one important thing that we were having a lot of struggle at is the data copy, because we had around 500 gigs of data which we had to move to AWS, and I mean we could have maybe used FTP, but we just did the RoboCopy and then moved our infrastructure from old environment to the AWS. Everybody says maybe the cloud-based infrastructure suits the best for the Linux-based application, so which I think now is not true, but when we directly moved to the AWS infrastructure, I thought that it's a difficult thing, maybe we could have had the Linux-based application and which are lightweight, but I don't think it's true now, because we have a lot of services which are provided by AWS and which are really suitable for the.NET-based application. So Windows opportunities are a little less and make sure you study well before you take any decisions or move to any of the services in AWS. We went ahead with the discovering what are all the dependencies we have from a lot of applications because we did a lift and shift. I mean there is something called a concept called lift, sinker, and shift, so we did not upgrade any of our applications, we just migrated, we did a lift and shift to the AWS. So challenges in the culture. So understanding the server, application, database, data dependencies followed by sizing, which was a lot of decision and we had to have a lot of discussion on how to have the right sizing on AWS and everything. For example, so we had a lot of SQL jobs, which were running in Microsoft SQL. When we moved to AWS, we took the decision of moving to Amazon-based RDS, and RDS did not support SSIS. So in that case, we made use of AWS Glue, which had similar experience of how the SSIS used to work, and the glues are very good. So long-term vision and the roadmap on AWS, which is very important when you move to AWS or any cloud-native infrastructure. So where do you want to be in AWS in the next five years? For example, we did not have anything like CI-CD implementation, because we used to use Hudson. I mean, it's a legacy-based CI-CD tool, but we have now started using elastic beanstalk, and we are also introducing ECS. So it's evolving. I mean, maybe you can establish a CCOE, which is a Cloud Center of Excellence. You can make use of within your DevOps team, within your SRE team, have a Cloud Center of Excellence, and they will be researching on the new technologies that are going to come, which are in the market, and which are in AWS, and which are in GCP, maybe if you decide to move there. So they will be researching on what are new in the market, and what is suitable in your infrastructure, which is very good option, and concentrating on the new business initiatives, which are going to come, and always rewrite your applications, and resizing the instances, because it's going to be very helpful in the long run. I think that's it. It's a short talk on how the migration helped us in AWS, and one thing is that, I have a plan for the execution and shoot for the success, but not for the perfection. Thank you.