AWS evs documentation change
Summary
Added notes about EC2 Capacity Reservations and VCF license requirements; updated example IP addresses for DNS records and route server configurations; added clarification notes for Self-deployed mode operations.
Security assessment
The changes consist of operational clarifications (license management notes), example IP address updates, and deployment timing instructions. No security vulnerabilities, exploits, or security-specific configurations are mentioned or addressed. The IP changes appear to be example value updates without security implications.
Diff
diff --git a/evs/latest/userguide/evs-deployment-prereq-checklist.md b/evs/latest/userguide/evs-deployment-prereq-checklist.md index f7ab491ef..8cfe89f09 100644 --- a//evs/latest/userguide/evs-deployment-prereq-checklist.md +++ b//evs/latest/userguide/evs-deployment-prereq-checklist.md @@ -10,0 +11,6 @@ This section contains a list of prerequisites that must be completed to enable s +###### Note + +We recommend that you create an Amazon EC2 Capacity Reservation to ensure that capacity is available when you add hosts. For more information, see [Create an Amazon EC2 Capacity Reservation](./setting-up.html#ec2-future-capacity-reservation). + +You need to bring your own VCF licenses to run VCF on Amazon EVS, regardless of how you deploy it. Whether you provide license keys at environment creation depends on your deployment mode — see [VCF subscriptions](./vcf-license-mgmt.html) for details. + @@ -16,0 +23,4 @@ vSAN license key | A vSAN license key allows you to activate and use the vSAN s +###### Note + +When you create an environment in Self-deployed mode, you need VCF license keys when you deploy and configure VCF, not when you create the Amazon EVS environment. Add them in your VCF management appliance after you install VCF. + @@ -82,13 +92,17 @@ DNS records for VCF components Component | Description | Minimum requirements | -ESX host 1 | IP address and hostname defined in the A record and PTR record for ESX host 1. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.0.10 | esxi01 -ESX host 2 | IP address and hostname defined in the A record and PTR record for ESX host 2. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.0.11 | esxi02 -ESX host 3 | IP address and hostname defined in the A record and PTR record for ESX host 3. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.0.12 | esxi03 -ESX host 4 | IP address and hostname defined in the A record and PTR record for ESX host 4. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.0.13 | esxi04 -vCenter Server appliance | IP address and hostname defined in the A record and PTR record for the vCenter Server appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.10 | vc01 -NSX Manager cluster | IP address and hostname defined in the A record and PTR record for the NSX Manager cluster. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.11 | nsx -SDDC Manager appliance | IP address and hostname defined in the A record and PTR record for the SDDC Manager appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.12 | sddcm01 -Cloud Builder appliance | IP address and hostname defined in the A record and PTR record for the Cloud Builder appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.13 | cb01 -NSX Edge 1 appliance | IP address and hostname defined in the A record and PTR record for the NSX Edge 1 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.14 | edge01 -NSX Edge 2 appliance | IP address and hostname defined in the A record and PTR record for the NSX Edge 2 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.15 | edge02 -NSX Manager 1 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 1 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.16 | nsx01 -NSX Manager 2 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 2 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.17 | nsx02 -NSX Manager 3 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 3 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.5.18 | nsx03 +ESX host 1 | IP address and hostname defined in the A record and PTR record for ESX host 1. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.1.11 | esxi01 +ESX host 2 | IP address and hostname defined in the A record and PTR record for ESX host 2. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.1.12 | esxi02 +ESX host 3 | IP address and hostname defined in the A record and PTR record for ESX host 3. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.1.13 | esxi03 +ESX host 4 | IP address and hostname defined in the A record and PTR record for ESX host 4. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each ESX host in each EVS deployment. | 10.1.1.14 | esxi04 +vCenter Server appliance | IP address and hostname defined in the A record and PTR record for the vCenter Server appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.10 | vc01 +NSX Manager cluster | IP address and hostname defined in the A record and PTR record for the NSX Manager cluster. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.11 | nsx +SDDC Manager appliance | IP address and hostname defined in the A record and PTR record for the SDDC Manager appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.12 | sddcm01 +Cloud Builder appliance | IP address and hostname defined in the A record and PTR record for the Cloud Builder appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.13 | cb01 +NSX Edge 1 appliance | IP address and hostname defined in the A record and PTR record for the NSX Edge 1 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.14 | edge01 +NSX Edge 2 appliance | IP address and hostname defined in the A record and PTR record for the NSX Edge 2 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.15 | edge02 +NSX Manager 1 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 1 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.16 | nsx01 +NSX Manager 2 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 2 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.17 | nsx02 +NSX Manager 3 appliance | IP address and hostname defined in the A record and PTR record for the NSX Manager 3 appliance. | Amazon EVS requires a DNS forward lookup zone with A records and a reverse lookup zone with PTR records created for each VCF management appliance in each EVS deployment. | 10.1.6.18 | nsx03 + +###### Note + +When you create an environment in Self-deployed mode, you need these DNS records when you deploy and configure VCF, not when you create the Amazon EVS environment. Create the ESX host records before you add hosts. @@ -110 +124 @@ route server association | The connection between a route server and a VPC. | -BGP ASN of the VPC Route Server side (Amazon-side ASN) | The Amazon-side ASN represents the AWS side of the BGP session between the VPC route server and the NSX Edge peer. You specify this BGP ASN when creating the route server. For more information, see [Create a route server](https://docs.aws.amazon.com/vpc/latest/userguide/route-server-tutorial-create.html) in the _Amazon VPC User Guide_. | This value must be unique, and in the range of 1-4294967295. AWS recommends using a private ASN in the 64512–65534 (16-bit ASN) or 4200000000–4294967294 (32-bit ASN) range. | 65001 +BGP ASN of the VPC Route Server side (Amazon-side ASN) | The Amazon-side ASN represents the AWS side of the BGP session between the VPC route server and the NSX Edge peer. You specify this BGP ASN when creating the route server. For more information, see [Create a route server](https://docs.aws.amazon.com/vpc/latest/userguide/route-server-tutorial-create.html) in the _Amazon VPC User Guide_. | This value must be unique, and in the range of 1-4294967295. AWS recommends using a private ASN in the 64512–65534 (16-bit ASN) or 4200000000–4294967294 (32-bit ASN) range. | 65022 @@ -113,2 +127,2 @@ route server peer 1 ID | The route server peer is a BGP peering session between -route server peer 1 IP address (EVS NSX Edge 1 side) | The IP address of the route server peer (`PeerAddress`). | Must use a unique unused IP address from the NSX uplink VLAN. Amazon EVS will apply this IP address to NSX Edge 1 as part of the deployment and peer with the route server endpoint peer. | 10.1.7.10 -route server peer 1 endpoint ENI address | The endpoint ENI IP address of the route server peer (`EndpointEniAddress`). | Automatically generated by route server on peer creation. | 10.1.7.11 +route server peer 1 IP address (EVS NSX Edge 1 side) | The IP address of the route server peer (`PeerAddress`). | Must use a unique unused IP address from the NSX uplink VLAN. Amazon EVS will apply this IP address to NSX Edge 1 as part of the deployment and peer with the route server endpoint peer. | 10.1.8.10 +route server peer 1 endpoint ENI address | The endpoint ENI IP address of the route server peer (`EndpointEniAddress`). | Automatically generated by route server on peer creation. | 10.1.0.11 @@ -117,2 +131,2 @@ route server peer 2 ID (EVS NSX Edge 2 side) | The route server peer is a BGP p -route server peer 2 IP address | The IP address of the route server peer (`PeerAddress`). | Must use a unique IP address from the NSX uplink VLAN. Amazon EVS will apply this IP address to NSX Edge 2 as part of the deployment and peer with the route server endpoint peer. | 10.1.7.200 -route server peer 2 endpoint ENI address | The endpoint ENI IP address of the route server peer (`EndpointEniAddress`). | Automatically generated by route server on peer creation. | 10.1.7.201 +route server peer 2 IP address | The IP address of the route server peer (`PeerAddress`). | Must use a unique IP address from the NSX uplink VLAN. Amazon EVS will apply this IP address to NSX Edge 2 as part of the deployment and peer with the route server endpoint peer. | 10.1.8.200 +route server peer 2 endpoint ENI address | The endpoint ENI IP address of the route server peer (`EndpointEniAddress`). | Automatically generated by route server on peer creation. | 10.1.0.201 @@ -133,0 +148,4 @@ BGP ASN of the NSX peer side | BGP ASN for the NSX side of the connection. | S +###### Note + +When you create an environment in Self-deployed mode, you configure the Route Server and BGP peering when you deploy and configure VCF, not when you create the Amazon EVS environment. You configure BGP peering on the NSX Edge Tier-0 gateway to the VPC Route Server yourself after you install VCF. For more information, see [Step 5: Configure NSX networking](./getting-started.html#self-deployed-nsx-edge). +