Explore resource placement within the multicloud environment.
- [Instructor] Right now, in cloud computing, there's a big trend toward the use of multi-cloud. The idea behind multi-cloud is that public cloud providers, such as Amazon, Microsoft and some others, basically offer a lot of the same services, even those services might be called something completely different from one cloud to the next. The thing is, one cloud provider might do a little bit better of a job with one service than another or that provider might offer a service a little bit cheaper than another provider. So, organizations very often implement a multi-cloud strategy in order to get the best of both worlds.
So, what we're going to be doing in this course is creating a multi-cloud architecture in which we share resources between Microsoft Azure and Amazon Web Services. So, in this video I wanted to give you a little bit of an overview of where we're going to be going. So, what you see on the screen right now is a visual representation of the Amazon Web Services cloud and Microsoft Azure, so you can see that right now I have a few virtual machines setup in each cloud. When we actually create this architecture, we probably won't have quite this many virtual machines, these are just here for the illustrative purposes.
The important thing to pay attention to on this screen is that the clouds are completely isolated from one another. We have boxes around Azure and around Amazon Web Services indicating that the resources within those clouds are completely self-contained. There is no default way to communicate between clouds, so we're going to have to implement some infrastructure in order to make that possible. Now before I show you what type of infrastructure we're going to put into place, one thing that I need to point out is that were using completely separate IP address spaces within the two clouds.
You'll notice that I have an IP address range for Amazon Web Services of 10.0.0.0/24 and an IP address space for Microsoft Azure of 10.1.0.0/24. Now you're free to use whatever address spaces you want, but the key is going to be that the address spaces can't overlap with each other and they can't overlap with anything that you might already have on premises. So, let's talk about what architecture we're going to put into place to enable communication between the two clouds.
Now, before I show you what we're doing, I need to clarify that this is one of those things that there are many different ways to accomplish. There isn't really a right or wrong way, so if you've got another method than the method that I'm using in this video, feel free to use it. What I'm going to be doing is on the Amazon Web Services side I'm going to be setting up an Amazon EC2 virtual machine and I'm going to be installing the Microsoft Routing and Remote Access Services inside of that virtual machine. Then, on the Microsoft Azure side, I'm going to be implementing two gateways.
I'm gonna be putting into place an Azure Virtual Network Gateway and that's going to work to receive traffic from AWS and then I'm also going to put into place an Azure local network gateway and that's going to handle all of the outbound traffic that's destined for AWS, and both of those gateways are going to be communicating directly with my routing and remote access server inside of the AWS Cloud. Then towards the end of the video series, I'm going to put into place a Microsoft Active Directory. Now you'll notice on the slide that the Microsoft Active Directory exists in the Amazon Web Services Cloud.
Again, there's no right or wrong way to do this. You may prefer to use it as Azure AD instead. I just thought that it would make a fun twist to create an Active Directory environment in the Amazon cloud rather than in the Microsoft cloud. But again, there many ways that you can accomplish this, there is no right or wrong way. This is just how we're doing it for the purposes of this video series. So, that's just a quick preview of where we're going to be going with the architecture that we're going to be deploying to enable communication between the Amazon Web Services and Microsoft Azure clouds.
- Planning a multicloud architecture
- Creating an AWS virtual private cloud
- Setting up an AWS gateway server
- Preparing Azure networking
- Configuring an RRAS server
- Connecting RRAS to Azure
- Testing communication between Azure and EC2
- Building an AD environment in AWS
- Spanning AD across clouds