PetaBytz

Facebook Twitter Linkedin Youtube Instagram
USA CANADA
PetaBytz Technologies

VM Migration : AWS to GCP by Cloudendure

Prerequisites

Both AWS and GCP Accounts required.

First make sure you must have an EC2 instance with small application installed in it.

here, In EC2 instance apache2 is installed.

Cloudendure Configuration

Cloudendure is used for VM migration. It is agent base migration tool so you have to install an agent in VM that will be migrated.

  • Go to Compute Engine in GCP Console.
  • Click on Import VM.
  • Once you click on that you find the bellow screen
  • Click on Cloudendure
  • Login in this using you GCP account
  • Click on create new project or you can use default project.

Note: Cloudendure and GCP projects are different from each other so you can set any name for project it will not effect your GCP account

  • Enter your GCP project id
  • Enter Service Account private key in Google Cloud Platform JSON Private Key
  • You can get that from GCP Console -> APIs & Services -> Credentials
  • Create Credentials for Service Account
  • Select Compute Engine default service account
  • After creating credentials it will automatically download JSON file. Open that JSON file in Cloudendure Console for private key
  • Next enter details to where you want to create you Compute Engine

NOTE : Here is one option Use VPN or Cloud interconnect. If we not enable this then it use public internet to migrate our VM, so it slow down the process of migration. So we can use VPN connected with AWS VPC via tunnel then it will do secure and fast migration.

  • Setup is completed
  • Install Cloudendure agent on AWS EC2 using given configuration.
  • Since we using Linux instance on EC2 so we use linux configuration.
  • Downloading agent in EC2 instance
  • Execute using next command to verify the cloudendure in EC2
  • Back to the Cloudendure console you can see the process of data replication has just started. It take 25–30 minutes to replicate because we using public internet for migrating the VM.
  • Once Replication is completed you have to create Blueprint for configuration of machine of GCP
  • Now click on LAUNCH TARGET MACHINE you will see there is 2 option:
  1. Test Mode : When you launch target machine in test mode you can do continuous data replication from AWS to GCP.

2. Cutover : In this mode you have no further contact with your AWS instance.

  • Here we launch machine in Test mode.
  • You can see progress in Job Progress
  • After a few minutes you can see 2 instance is launched in your GCP console.

the one is our actual VM which is migrated from AWS and another one is Cloudendure replicator, since we are doing in Test mode so it create replicator, if you launch in cutover mode you will not find that instance.

  • This is migrated VM on GCP
  • If you want to ssh in GCP instance you can not directly do that by clicking on ssh button, you have to use PUTTY or SSH client to connect to that instance using same ssh key which is generated form AWS EC2 instance.

Conclusion :

As you can see, cloud migration is quite a doable endeavor, if it is executed according to a straightforward checklist. However, there are multiple underwater reefs that pose a grave danger for the project.

Thus said, cloud migration is one of the most popular services provided by reliable Managed Services Providers worldwide. These companies have ample experience designing and implementing the cloud migration plans, allowing their customers reach the business goals set, optimize their product or services performance and deliver more value to their customers while spending less on their IT infrastructure maintenance.

Velostrata also provide cloud migration platform.