AWS evs documentation change
Summary
Updated VCF version references from 5.2.1 to 5.2.2, added links to version documentation, fixed typos, added ESX host version selection step, adjusted step numbering, and standardized terminology from ESXi to ESX.
Security assessment
The changes primarily involve version updates, documentation links, and terminology corrections. No evidence of security vulnerability fixes, incident response, or security weaknesses is present. The terminology change from ESXi to ESX appears cosmetic and doesn't alter security implications. The SSH access documentation remains unchanged in substance.
Diff
diff --git a/evs/latest/userguide/getting-started.md b/evs/latest/userguide/getting-started.md index 7c77f73f6..bfaf47446 100644 --- a//evs/latest/userguide/getting-started.md +++ b//evs/latest/userguide/getting-started.md @@ -15 +15 @@ After you’re finished, you’ll have an Amazon EVS environment that you can us -To get started as simply and quickly as possible, this topic includes steps to create a VPC, and specifies minimum requirements for DNS server configuration and Amazon EVS environment creation. Before creating these resources, we recommend that you plan out your IP address space and DNS record setup that meets your requirements. You should also familiarize yourself with VCF 5.2.1 requirements. For more information, see the [VCF 5.2.1 release notes](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-2/vcf-release-notes/vmware-cloud-foundation-521-release-notes.html). +To get started as simply and quickly as possible, this topic includes steps to create a VPC, and specifies minimum requirements for DNS server configuration and Amazon EVS environment creation. Before creating these resources, we recommend that you plan out your IP address space and DNS record setup that meets your requirements. You should also familiarize yourself with VCF 5.2.x requirements. See the [VCF 5.2.x release notes](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-2/vcf-release-notes.html) for relevant release information. @@ -19 +19 @@ To get started as simply and quickly as possible, this topic includes steps to c -Amazon EVS only supports VCF version 5.2.1.x at this time. +For information about VCF versions provided by Amazon EVS, see [VCF versions and EC2 instance types provided by Amazon EVS](./versions-provided.html). @@ -593 +593 @@ For more information about configuring DNS servers in a DHCP option set, see [Cr -#### Configure DNS for on-premesis connectivity +#### Configure DNS for on-premisis connectivity @@ -758 +758 @@ Ensure that the AWS Region shown in the upper right of your console is the AWS R - 2. For **Environment version** , choose your VCF version. Amazon EVS currently only supports version 5.2.1.x. + 2. For **Environment version** , choose your VCF version. For information about VCF versions provided by Amazon EVS, see [VCF versions and EC2 instance types provided by Amazon EVS](./versions-provided.html). @@ -788 +788 @@ Your VCF license will be available to Amazon EVS across all AWS Regions for lice -Amazon EVS requires that you maintain a valid vSAN license key in SDDC Manager for the service to function properly. If you manage the vSAN license key using the vSphere Client post-deployment, you must ensure that the keys also appears in the licensing screen of the SDDC Manager user interface. +Amazon EVS requires that you maintain a valid vSAN license key in SDDC Manager forchooose chose the service to function properly. If you manage the vSAN license key using the vSphere Client post-deployment, you must ensure that the keys also appears in the licensing screen of the SDDC Manager user interface. @@ -801,0 +802,2 @@ Amazon EVS requires that you maintain a valid vSAN license key in SDDC Manager f + 4. For **ESX host version** , during environment creation a default ESX version for the chosen VCF version will be used. See [VCF versions and EC2 instance types provided by Amazon EVS](./versions-provided.html) for more information. + @@ -810 +812 @@ Amazon EVS only supports i4i.metal EC2 instances at this time. - 4. For **SSH key pair** , choose an SSH key pair for SSH access into the host. + 5. For **SSH key pair** , choose an SSH key pair for SSH access into the host. @@ -812 +814 @@ Amazon EVS only supports i4i.metal EC2 instances at this time. - 5. Choose **Add host**. + 6. Choose **Add host**. @@ -916 +918 @@ Environment deployment can take several hours. - * For `--vcf-version`, Amazon EVS currently only supports VCF 5.2.1.x. + * For `--vcf-version`, See [VCF versions and EC2 instance types provided by Amazon EVS](./versions-provided.html) for VCF versions provided by Amazon EVS, @@ -972 +974 @@ Amazon EVS requires a VPC Route Server instance that is associated with two Rout - --vcf-version VCF-5.2.1 \ + --vcf-version VCF-5.2.2 \ @@ -1068 +1070 @@ The following is a sample response. - "vcfVersion": "VCF-5.2.1", + "vcfVersion": "VCF-5.2.2", @@ -1147 +1149 @@ The following is a sample response. - "vcfVersion": "VCF-5.2.1", + "vcfVersion": "VCF-5.2.2", @@ -1319 +1321 @@ If you are using AWS Direct Connect, you may need to also update your Direct Con -Amazon EVS uses AWS Secrets Manager to create, encrypt, and store managed secrets in your account. These secrets contain the VCF credentials needed to install and access VCF management appliances such as vCenter Server, NSX, and SDDC Manager, as well as the ESXi root password. For more information about retrieving secrets, see [Get secrets from AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets.html) in the _AWS Secrets Manager User Guide_. +Amazon EVS uses AWS Secrets Manager to create, encrypt, and store managed secrets in your account. These secrets contain the VCF credentials needed to install and access VCF management appliances such as vCenter Server, NSX, and SDDC Manager, as well as the ESX root password. For more information about retrieving secrets, see [Get secrets from AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets.html) in the _AWS Secrets Manager User Guide_. @@ -1327 +1329 @@ After you have retrieved your VCF credentials from AWS Secrets Manager, you can -By default, Amazon EVS enables the ESXi Shell on newly deployed Amazon EVS hosts. This configuration allows access to the Amazon EC2 instance’s serial port through the EC2 serial console, which you can use to troubleshoot boot, network configuration, and other issues. The serial console does not require your instance to have any networking capabilities. With the serial console, you can enter commands to a running EC2 instance as if your keyboard and monitor are directly attached to the instance’s serial port. +By default, Amazon EVS enables the ESX Shell on newly deployed Amazon EVS hosts. This configuration allows access to the Amazon EC2 instance’s serial port through the EC2 serial console, which you can use to troubleshoot boot, network configuration, and other issues. The serial console does not require your instance to have any networking capabilities. With the serial console, you can enter commands to a running EC2 instance as if your keyboard and monitor are directly attached to the instance’s serial port. @@ -1333 +1335 @@ The EC2 serial console can be accessed using the EC2 console or the AWS CLI. For -The EC2 serial console is the only Amazon EVS supported mechanism to access the Direct Console User Interface (DCUI) to interact with an ESXi host locally. +The EC2 serial console is the only Amazon EVS supported mechanism to access the Direct Console User Interface (DCUI) to interact with an ESX host locally. @@ -1337 +1339 @@ The EC2 serial console is the only Amazon EVS supported mechanism to access the -Amazon EVS disables remote SSH by default. For more information about enabling SSH to access the remote ESXi Shell, see [Remote ESXi Shell Access with SSH](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere-sdks-tools/8-0/getting-started-with-esxcli-8-0/running-host-management-commands-in-the-esxi-shell/remote-esxi-shell-access-with-ssh.html) in the VMware vSphere product documentation. +Amazon EVS disables remote SSH by default. For more information about enabling SSH to access the remote ESX Shell, see [Remote ESX Shell Access with SSH](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere-sdks-tools/8-0/getting-started-with-esxcli-8-0/running-host-management-commands-in-the-esxi-shell/remote-esxi-shell-access-with-ssh.html) in the VMware vSphere product documentation. @@ -1403 +1405 @@ The following is a sample response. - "vcfVersion": "VCF-5.2.1", + "vcfVersion": "VCF-5.2.2", @@ -1412 +1414 @@ The following is a sample response. - "vcfVersion": "VCF-5.2.1", + "vcfVersion": "VCF-5.2.2",