In this demo, you will learn how to install the Migrate for Compute Engines Infrastructure components on GCP and AWS. Once you install all the components, you'll be ready to start migrating virtual machines. In this demonstration, we will teach you how to migrate from Amazon ec2 to Google Cloud platform leveraging by great for compute engine. When migrating from AWS ec2, there are several prerequisites that you will need in preparation for the migration itself. First, you will need an AWS account and an ec2 instance to migrate. Second, an AWS VPC subnet with appropriate VPN connectivity to Google Cloud. And third, migrate for compute engines IAM roles and access policies deployed on the AWS account. To begin, we first want to download and unzip the cloud formation stack template from the Migrate for Compute Engine download page. When we go to the download page, you will see the cloud formation stack. Click on it to download it. Next, unzip the file. To begin, let's first access cloud formation within the AWS Management console. Next we're going to create a new stack with new resources and we're going to upload a template file, which is what we've downloaded. And then click Next. We now want to enter stack name and also selecting the appropriate VPC. So we're going to want to click Next to move forward. And then we're going to go ahead and create the stack. After several minutes, you'll notice that the stack that we just deployed has created successfully. Now that our stack has been successfully, we want to go ahead and create an AWS access key and corresponding secret key. The access key and secret key will enable Migrate for Compute Engine to programmatically interact with AWS without our need to supply a username and password. To create the key, I will click on my username and go to my security credentials. Next I will click where it says Create access key. You will notice that the new access key is already available. You will want to download the CSV file which will contain the access key and the secret as well. Let's open the file to get an idea of what's inside. As you can see, we have an access key and a secret access key. You will notice that Amazon warns you that this is the only time that the secret access key can be viewed or downloaded. It is for this reason that we downloaded the CSV file because we will need these later to input into Migrate for Compute Engine for programmatic access to AWS. Let's go ahead and click close. To continue the configuration, click on Source Cloud. We'll first want to configure cloud credentials. So click on the Cloud Credentials tab, then click Create. Fill out the form, in this case, we're going to use US West Oregon, and paste in the access key. Once you enter the appropriate information within the cloud credentials, you can click OK. Next, we will configure cloud details. Cloud details define the specifics for the AWS environment that migrate for compute engine will operate in. This includes IAM credentials, region, VPC, subnet, and security group. To begin, click Create. Make sure to enter all of the appropriate options. You can see once the cloud details are completed when they show a status of ready. Now that the cloud details have been created, let's go to the home screen and go ahead and create the cloud extensions. To do so, click on TARGET CLOUD, then click Create. We'll want to select our project which will be Velo sandbox. The region in which we want to deploy our cloud extensions, which is going to be US EAST-1. The corresponding VPC which in this scenario will be default. The Edge node network tags, which is FW- Ilustrada. And the default network tag for workload, which is FW-workloads. The default destination project for the workloads. The default service account for the workloads, which we have created previously. We will then click on Cloud Extension and enter cloud extension name. We will then select the service account for the edge nodes. And we will go ahead and we will select small for the cloud extension size. If this is a large production migration, you will want to choose large for the cloud extension size. Next we will click Zones. And select the zone in which will deploy cloud extension node a and node b as well as the corresponding subnets for each of the zones and the default workload subnet. We will then add labels and then click OK once done. At this point, the cloud extension is being deployed within Google Cloud. In summary, now that we've set up our cloud details and cloud credentials for AWS. And the fact that we already have our Cloud extension running in Google Cloud. We will be able to move forward with the migration in a future demo.