Verify environment creation
This page applies to EVS-deployed environments (VCF 5.2.x). For Self-deployed environments that run VCF 9.x, see Deploy in Self-deployed mode.
After you create an environment, check that Amazon Elastic VMware Service finished the deployment and that the environment and its hosts are ready.
Environment creation can take several hours. If the environment is still being created, wait and check again.
Check the environment and its hosts
You can check the environment by using the Amazon EVS console or the AWS CLI.
Example
The environment is ready when its state is Created (CREATED).
In the console, its status also shows Passed.
If the environment status is Failed
When the environment status is Failed, the console shows the results of the environment status checks. The checks are Key re-use, Host count, Key coverage, and Reachability. For what each check means, see Monitor environment status. For causes and solutions, see Troubleshoot environment status checks.
Next steps
After you verify the environment, complete the following tasks.
-
Explicitly associate the Amazon EVS VLAN subnets with a route table in your VPC. NSX connectivity requires this association. For more information, see Associate VLAN subnets with a route table.
-
Retrieve the VMware Cloud Foundation (VCF) credentials and sign in to the management appliances. For more information, see Retrieve VCF credentials and access appliances.
-
If you chose HCX internet connectivity, associate Elastic IP addresses with the public HCX VLAN subnet. For more information, see Configure HCX public internet connectivity.
-
If you connect to on-premises networks through a transit gateway, update the transit gateway route tables. For more information, see Set up VPC Route Server and on-premises connectivity.