| | | | | | --- | --- | --- | --- | * * * [[_TOC_]] * * * Summary ------- When the decision is made to migrate applications to a cloud like [VMware Cloud on AWS](https://cloud.vmware.com/vmc-aws?int_cid=70134000001CaZ5&src=WWW_us_VMW_0cnHu1FmS2pidRE57WJU) (VMC on AWS), a few things need to happen. First and foremost, insight into your applications and application behavior is critical. One of the perks of migration to a public cloud is that you can choose the optimal location to make sure your end-users benefit. But, without networking insights, this is often overlooked. Below is a checklist of the list of documentation to gather from the client during the discovery and planning phase of a VMC engagement. Checklist --------- **Current State Landing Zone (or) Control Tower ** - VPC Structure - Connectivity - Architecture Design - Security Groups - Disaster recovery - Regions and Availability Zones - Organizations - Account structure **Portfolio** - Previous Application Discovery tool's output - RVtools Output - Customer's CMDB (e.g. ServiceNow) - vRealize Network Insight tool installation pre-requisites - Application Owners identified - Portfolio of applications (or) virtual machines for migration - Business critical applications **Operations** - Change Management - Change Request Board (CRB) and Change Advisory Board(CAB) - Problem and Incident Management - Monitoring and logging tools - Application decommissioning process - Reporting requirements **Security** - Data governance policy - Encryption in-transit and in-flight - Laws and regulations adherence based on customer's business - Review security posture **VMware on AWS** - Existence of an SDDC - Use of VPN vs. Direct Connect pre- and post-migration - Subnets for Management and Compute networks - Existence Virtual Distributed Switch (vDS) - Current on-premises vCenter version - Cluster organization in on-premises vCenter - Total data requirement (sum of data in TB of all the virtual machines) **Attachments:**