Create an environment
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.
Create an Amazon Elastic VMware Service environment in EVS-deployed mode with the Amazon EVS console or the AWS CLI. In this mode, environment creation adds the hosts and deploys VMware Cloud Foundation (VCF) on them. In Self-deployed mode, you add hosts and install VCF after you create the environment.
You can configure an environment only when you create it. You can’t change the environment settings after you create it. You can’t add VLAN subnets or change their CIDR blocks after you create the environment. For an overview of all environment settings, see the Amazon EVS API Reference Guide.
Before you begin
Complete the following tasks before you create the environment.
-
Check that you meet the Amazon EVS service requirements. Environment deployment fails if they aren’t met. For more information, see Prepare your AWS account.
-
Build the network foundation in the same Region and Availability Zone where you create the environment. This includes the VPC, the service access subnet, DNS and NTP, a route server in Amazon VPC Route Server with two endpoints and two peers, and a network ACL. For more information, see Build the network foundation.
-
Size the Amazon EVS VLAN subnets. You can’t add VLAN subnets or change their CIDR blocks after you create the environment. For more information, see Plan your VPC and VLAN subnets and VLAN subnets, VLAN IDs, and IP addresses.
-
If you plan to use HCX over the internet, create a custom network ACL for the HCX VLAN. We recommend a dedicated network ACL so that you can control HCX internet traffic separately. For more information, see Create a network ACL for VLAN subnet traffic.
-
If you plan to use HCX over the internet, create the IPAM, the Elastic IP addresses, and the public CIDR block in your VPC. For the steps, see Part 1 of Configure HCX public internet connectivity.
-
Have your Broadcom Site ID, a VCF solution key (VMware vSphere 8 Enterprise Plus for VCF), and a vSAN license key. For the license requirements, see License key requirements.
-
Create a DNS A record in a forward lookup zone and a PTR record in a reverse lookup zone for each host and each VCF management appliance. For the list of records, see Deployment prerequisite checklist.
-
Create an Amazon EC2 key pair for SSH access to the hosts.
License key requirements
Your license keys must meet the following requirements.
-
The VCF solution key must have sufficient cores, and the vSAN license key must have sufficient vSAN capacity. The thresholds depend on the instance type. For more information, see VCF licensing.
-
Neither key can be in use by an existing Amazon EVS environment.
-
Amazon EVS doesn’t validate license keys. To validate them, go to Broadcom support
. -
You must keep a valid VCF solution key and vSAN license key in SDDC Manager for the service to function. If you manage the keys in the vSphere Client after deployment, make sure that they also appear on the licensing screen of SDDC Manager.
-
Your VCF subscription and your environment ID are available to Amazon EVS across all AWS Regions for license compliance.
Create the environment
Environment creation can take several hours.
The hosts that Amazon EVS deploys in your account incur charges.
For prices, see Amazon EVS pricing
You can create the environment by using the Amazon EVS console or the AWS CLI.
Example
You have started the creation of an Amazon EVS environment.
What happens during creation
The following happens when you create the environment.
-
Amazon EVS creates the Amazon EVS VLAN subnets and implicitly associates them with the main route table of the VPC. After deployment completes, you must explicitly associate the VLAN subnets with a route table for NSX connectivity. For more information, see Associate VLAN subnets with a route table.
-
Hosts that are created with the environment receive the tag
DoNotDelete-EVS-[<environmentId>]-[<hostname>]. -
Tags that you add to the environment don’t propagate to the underlying AWS resources, such as EC2 instances. You can tag those resources with the console of the respective service or the AWS CLI.
Don’t use the Amazon EC2 console to stop, start, or terminate Amazon EVS hosts. On hosts with local storage, these actions cause the loss of the vSAN data on the instance store volumes. To create, replace, or delete a host, use the Amazon EVS console, the AWS CLI, or the Amazon EVS API.
Amazon EVS deploys a recent bundled version of VCF that might not include individual product updates (async patches).
After deployment completes, we recommend that you review and update the individual products so that they include the latest fixes. You can use the Broadcom Async Patch Tool (AP Tool) or the SDDC Manager in-product lifecycle management (LCM) automation. For more information, see Update and upgrade.
You must upgrade NSX outside of SDDC Manager.