AWS evs documentation change
Summary
Added VMware documentation reference for host requirements, updated terminology from 'Amazon EVS Custom Addon' to 'custom add-on', and modified CLI/JSON examples (added ESXi version in CLI, removed from JSON).
Security assessment
Changes involve terminology updates and example adjustments without security implications. No references to vulnerabilities, access controls, or security configurations.
Diff
diff --git a/evs/latest/userguide/evs-env-create-host.md b/evs/latest/userguide/evs-env-create-host.md index e2ccdf4bf..7a1037941 100644 --- a//evs/latest/userguide/evs-env-create-host.md +++ b//evs/latest/userguide/evs-env-create-host.md @@ -9 +9 @@ -After an Amazon EVS environment deploys, you can add hosts to increase capacity and workload resiliency. Amazon EVS supports 4-32 hosts and a default throughput bandwidth of up to 600 Gbps per environment. This action can only be used after the Amazon EVS environment is deployed. +After an Amazon EVS environment deploys, you can add hosts to increase capacity and workload resiliency. This action can only be used after the Amazon EVS environment is deployed. For host count requirements based on your VCF deployment topology, see the [VMware Cloud Foundation documentation](https://techdocs.broadcom.com/us/en/vmware-cis/vcf.html). @@ -21 +21 @@ Follow these steps to create an Amazon EVS host. -Amazon EVS hosts use the Amazon EVS Custom Addon to provide important host functionality. When you add a host to your environment, it will have the latest available version of the Amazon EVS Custom Addon. If your environment uses hosts with an older Custom Addon version, adding host to your vSphere cluster will cause cluster image remediation to fail. For steps to troubleshoot this issue, see [Troubleshoot add host failure due to incompatible cluster image](./evs-env-ami-maintenance.html#troubleshoot-add-host-failure-cluster-image). +Amazon EVS hosts use a custom vendor add-on to provide important host functionality. When you add a host to your environment, it will have the latest available version of the Amazon EVS custom add-on. If your environment uses hosts with an older add-on version, adding host to your vSphere cluster will cause cluster image remediation to fail. For steps to troubleshoot this issue, see [Troubleshoot add host failure due to incompatible cluster image](./evs-env-ami-maintenance.html#troubleshoot-add-host-failure-cluster-image). @@ -77,0 +78 @@ AWS CLI and SDDC Manager UI + --esx-version "ESXi-8.0U3g-24859861" \ @@ -81,2 +82 @@ AWS CLI and SDDC Manager UI - "instanceType": "i4i.metal",\ - "esxVersion": "ESXi-8.0U3g-24859861"\ + "instanceType": "i4i.metal" \