In this module, we will cover the main components of Migrate for Compute Engine and how they work together. Migrate for Compute Engine is comprised of three major components: the Migrate for Compute Engine Manager, the Cloud extension, which is hosted in Google Cloud Platform, and the backend, which is hosted in your source environment. The managers of Compute Engine virtual machine that orchestrates the migration process and provides a web user interface. It is also where you define wave migrations, which are groups of machines that will be migrated together. The Migrate for Compute Engine Manager connects to your on-premises infrastructure over secure tunnel either via a VPN connection or a physical Cloud Interconnect. The manager communicates with the VMware vCenter plugin, which in turn communicates with Migrate for Compute Engine's on-premises backend virtual machine. The backend is a virtual machine that's streams virtual machine disks in your on-premises data-center to Google Cloud. If you're source environment is AWS, a migrate for Compute Engine importer virtual machine will be installed automatically in your AWS Cloud environment, which provides the same functionality as the backend on-premises. Every time a migration is initiated, the manager creates an importer in your AWS environment to stream the source virtual machine disk to Google Cloud Platform over a secure connection. When the migration is completed, the importer is deleted. The receiving end of the importer from AWS or the backend from your on-premises infrastructure is the Cloud extension, which runs in Google Cloud. Cloud extensions works with these components to create a highly optimized data-streaming and caching layer for the virtual machines which are being migrated to the Cloud, thus reducing downtime to minutes. The Cloud extension is composed of a pair of Cloud Edge Nodes for redundancy, with one in each zone. They serve data to the migrated virtual machine over an [inaudible] interface.