hello everyone welcome to this demo on migrating a virtual machine from gcp to AWS using AWS application migration service I am vami I'm a Solutions architect here at AWS in this video we'll start with a quick overview of network architecture to understand how AWS mgn works in the background for replicating servers then we'll take a quick look at demo uh itself it starts by installing a replication agent on a source virtual machine it could be VMS running in corporate data center or any cloud provider when we install a application agent on a source VM it appears as a source server in AWS mgn service console mgn service will create replication servers automatically to constantly replicate Source diss from The Source VM onto a staging area subnet it creates equal number of EBS volumes to match with the source diss when we actually launch a test instance or a cutover ec2 instance mgn service will create a conversion server for for making the staging area EBS volumes bootable and attaches them as new EBS volumes to the new E2 instances this whole process can be monitored using mgn service console and easy to service console let's dive into it I'm in gcp console I've created a simple Linux web server running a at using compute engine it's a simple um hello world kind of application and I want to migrate this server to AWS without having to make any changes let's switch to AWS console search for application migration service if this is your first time uh setting up uh application migration service you'll be asked to configure replication settings and launch settings we'll take a quick look at how the replication template looks like and the launch template replication template defines configuration for the replication servers which constantly replicates the desk from sours to destination the launch template defines the configuration for test ec2 instances and actual cutover ec2 instances you can choose to configure and customize IP address settings subnet Choice even security groups all those settings can be configured in these templates okay going back to the homepage again click on ADD server it will give you a quick installation instructions it will prepare uh the commands for you I'm going to stop the recording here and provide I IM access key ID and secret access key along with the session token for this you can either create an I am user or use single sign on credentials I'll be using single signon credential s in this demo once we provide the access key ID secret access key along with the session token you can see that a downloader command and uh the installation command are prepared for you we can use this as quick getting started guides as in the source server other optional things uh here are you can choose the operating system and uh the preferences for replication whether to replicate all this or you want to customize the the diss to be replicated I'll copy the downloader command switching back to gcp console let's connect using SS paste the command to download the replication agent and copy the next command to install the agent this will take few minutes to identify the volumes attached to the source server and this will show up in the source servers on AWS mgn console once the replication agent installation is finished it appears as a source server over in mgn console however it's still initiating and it will create a replication server start replicating the discs the whole process can be monitored using this console as you can see in the replication initiation steps it's creating bunch of things for us starts by creating security groups launching the replication server boot replication server and so forth it might take few minutes for this process to finish and the replication status to be ready meanwhile let's check the ec2 console as you can see a new replication server has been created automatically and this will be used to replicate The Source diss I'll pause the recording for a few minutes until the replication status is ready okay after a few minutes the initial replication has finished and the server is now ready for testing let's go ahead and launch test instance and we'll come back to understand some of these settings available while this service is launching a test instance we'll take a look at the uh job history here in a minute but before that let's understand so far what is the information that the replication agent has captured from The Source server starting with the server info it identifies the host name um number of CPUs that are running in the source server operating system plus uh memory discs all information that's required to replicate similarly there is disk settings available you can choose to change the staging Disk type by default um the service would launch a standard htd as identified um better suitable for the source disk you can also override replication settings and launch settings for this particular server in addition to what's available at the account level let's take a look at the launch settings as well here by default um because of the launch template it will launch a C5 large instance but uh you can customize you can change um to appropriate size if required let's take a quick look at the chop details here you can see that the conversion has started we will go to ec2 instance and take a look at that quickly but just a quick snapshot um it uses the recent available Snapshot from the EBS volume and converts into a bootable dis launches a test or cutover E instance in the ec2 console you can see that a temporary conversion has been started which will convert all the staging EBS volumes to bootable and then launch a new E2 instance when the conversion job is finished a new E2 instance appears in the console this is an exact replica of our source gcp server so we should be able to test it right away select the E instance to copy the public IP address and paste it in a new browser window there you go this confirms that we were able to migrate omm from gcp to AWS using AWS migration service once the testing is finished we can go back to the mgn console click on the source server and you can mark this server as ready for cut over this will terminate any test servers that were launched and it will Mark the server for the actual cut over it's important to understand that when you launch a test instance or a cutover instance the source server and the newly launched servers are no longer in sync it will use the latest snapshot that's available to spin up a new instance however as long as the replication server is active data is continuously replicated from the source to the staging area that's all for this demo I thank you for watching the whole video please feel free to leave a comment