End of life data center migration
The course is part of these learning paths
This course is a "live" scenario discussion where the Cloud Academy team tackle a migration project. Our customer needs to migrate out of their current data center by a certain date. They also would like to modernize their business applications.
Our brief in the exercise is to deliver:
- A target architecture that addresses the challenges described by the customer
- A migration plan detailing how to move the service to AWS with minimal interruption
- A recommendation on how to approach DR to achieve RPO of 24 hours and RTO of 4 hours
- An application optimization plan with a proposed enhancement roadmap
As a scenario, this series of lectures is recorded "live" and so is less structured than other Cloud Academy courses. As a cloud professional you often have to think and design quickly, so we have recorded some of the content this way to best emulate the type of conditions you might experience in the working environment. Watching the team approach this brief can help you define your own approaches and style to problem-solving.
This course discusses AWS services so it is best suited to students with some prior knowledge of AWS services.
We recommend completing the Fundamentals of AWS learning path before beginning this course.
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
- So for stage one, we're doing lift and shift.
- You were saying earlier that the servers have a, the multi-homed, they have a public private-
- Yeah, public private interfaces.
- So we'd probably deploy into a VBC across AZs, so perhaps three, three AZs?
- [Man On Right] Yep.
- AZ1, AZ2, AZ3 would have a, perhaps a public front end subnet.
- And the back ends behind that would have the private zone. And at the bottom layer would have run from the databases.
- So we would deploy our instances so that they had an elastic network interface at the, in the public subnet.
- And the one in the ... One of the private. So we'll just repeat that across the Azs.
- The private subnets would be sent out with a route table that allowed a route back out, a virtual private gateway, to the corporate network.
- So it's got a VPG, and we would have, all tunnels out to, to the corporate network.
- [Man On Right] That's just the LIPC connection from the
- Yeah. Public subnets would have a route table that routed internet traffic out an IGW, internet gateway.
- So it's a fairly, it's a fairly typical and standard VPC design.
- [Man On Right] Yeah.
- And in the bottom layer, we wouldoracle database.
- [Man On Right] Yeah.
- And that would have the sync running through the IBC tunnel to-
- [Man On Right] Back to execute storage.
- [Man On Left] Yeah.
About the Author
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.