Many customers are excited about the ability to allow EC2 instances to communicate with VMware virtual machines. This capability provides customers with the ability to choose which applications run on each technology. In this task we will deploy an EC2 instance that we will use to ping a VM workload with its private IP, and vice versa.

Build an EC2 Instance
  1. From within the AWS Console, select ‘EC2’
  2. Click ‘Instances’
  3. Click ‘Launch Instance’
  4. Find and select “Microsoft Windows Server 2016 Base’
  5. Select ‘t2.micro – Free tier eligible’
  6. Click ‘Next: Configure Instance Details’
  7. Under ‘Network’, select the VPC that is connected to your SDDC
  8. Under ‘Subnet’, select the subnet of the SDDC
  9. Under ‘Auto-assign Public IP’, select ‘Enable’
  10. Click ‘Next: Add Storage’
  11. Click ‘Next: Add Tags’
  12. Click ‘Add Tag’
  13. Configure the following values:
    • Key = ‘Name’
    • Value = ‘Test EC2 to VM’
  14. Click ‘Next: Configure Security Group’
  15. Choose ‘Select an existing security group’
  16. Select the security group configured in the previous steps
    • Note: We will need to add additional rules after the EC2 instance is deployed
  17. Select ‘Review and Launch’
  18. Select ‘Launch’
  19. Create a new Key Pair
  20. Give the new key pair a name
  21. Click ‘Download Key Pair’
  22. Click ‘Launch Instances’

While we wait roughly 5 minutes for the instance to be in a running state, we can go ahead and edit the security group configuration.

Edit the Security Group
  1. Click ‘View Instances’
  2. Scroll down in the left-pane and click on ‘Security Groups’
  3. Select the corresponding Security Group and click the ‘Inbound’ tab
  4. Click ‘Edit’
  5. Click ‘Add Rule’
  6. Configure the rule as follows:
    • Type = ‘RDP’
    • Source = ‘’ (or your public IP if you choose) o Description = ‘RDP to EC2 Test Instance’
  7. Click ‘Save’
  8. In the left-pane, find and select ‘Instances’
  9. Select the instance you previously deployed and click ‘Connect’
  10. Download the Remote Desktop File to your local machine
  11. Click ‘Get Password’
  12. Click ‘Choose File’ next to ‘Key Pair Path’ and select the Key Pair you created when deploying this instance
  13. Click ‘Decrypt Password'
  14. Copy the password and open an RDP session to your EC2 instance using the Remote Desktop File
Check traffic flow
  1. Before we begin working in the EC2 instance, login to the SDDC’s vSphere Client, select the ‘Server-2012-01’ VM and take note of its IP Address from the VM summary page
    • Note: If the VM is not powered on, power it on at this point and wait for the IP Address to populate
  2. Return to the RDP session and open the command prompt
  3. Ping the IP address of ‘Server-2012-01’

You are now pinging an internal IP address located in the VMware Cloud on AWS account from an internal IP address of an EC2 instance running in your own AWS account.

Remove the EC2 Instance

If you wish to terminate the EC2 instance to avoid hourly charges, close the RDP session and return to the AWS Console

  1. Select your EC2 Instance and click ‘Actions’
  2. Maneuver to ‘Instant State’ > ‘Terminate’
  3. The EC2 Instance will power off and be deleted


check-circle-line exclamation-circle-line close-line
Scroll to top icon