View a markdown version of this page

Verify environment creation - Amazon Elastic VMware Service

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
Console
  1. Open the Amazon EVS console.

  2. In the navigation pane, choose Environments.

  3. Select the environment.

  4. Choose the Details tab.

  5. Check that the Environment status is Passed and the Environment state is Created. If the Environment state still shows Creating, refresh the page.

  6. Choose the Hosts tab and check that the four hosts that you specified are listed.

AWS CLI
  1. Open a terminal session.

  2. Run the following command with your environment ID and the Region that contains your resources.

    Replace the example environment ID with your own value, and replace <region-code> with the Region where you created the environment.

    aws evs get-environment --environment-id env-abcde12345 --region <region-code>

    The environment is ready to use when environmentState is CREATED. If it still shows CREATING, run the command again. The following is a sample response.

    { "environment": { "environmentId": "env-abcde12345", "environmentState": "CREATED", "createdAt": "2025-04-13T13:39:49.546000+00:00", "modifiedAt": "2025-04-13T13:40:39.355000+00:00", "environmentArn": "arn:aws:evs:us-east-2:111122223333:environment/env-abcde12345", "environmentName": "testEnv", "vpcId": "vpc-1234567890abcdef0", "serviceAccessSubnetId": "subnet-01234a1b2cde1234f", "vcfVersion": "VCF-5.2.2", "termsAccepted": true, "licenseInfo": [ { "solutionKey": "00000-00000-00000-abcde-11111", "vsanKey": "00000-00000-00000-abcde-22222" } ], "siteId": "my-site-id", "checks": [], "connectivityInfo": { "privateRouteServerPeerings": [ "rsp-1234567890abcdef0", "rsp-abcdef01234567890" ] }, "vcfHostnames": { "vCenter": "vcf-vc01", "nsx": "vcf-nsx", "nsxManager1": "vcf-nsxm01", "nsxManager2": "vcf-nsxm02", "nsxManager3": "vcf-nsxm03", "nsxEdge1": "vcf-edge01", "nsxEdge2": "vcf-edge02", "sddcManager": "vcf-sddcm01", "cloudBuilder": "vcf-cb01" }, "credentials": [] } }

    The ARN in the sample uses the aws partition. In other partitions, the ARN starts with that partition name.

  3. List the hosts in the environment and check that the four hosts that you specified are listed.

    Replace the example environment ID with your own value, and replace <region-code> with the Region where you created the environment.

    aws evs list-environment-hosts --environment-id env-abcde12345 --region <region-code>

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.