AWS evs documentation change
Summary
Updated terminology from 'ESXi' to 'ESX' throughout the document. Added information about VCF version support and compatibility resources, including links to Broadcom's Interoperability Matrix and Compatibility Guide. Removed specific VCF version restrictions and added a reference to a new versions-provided page.
Security assessment
The changes primarily involve terminology updates (ESXi→ESX) and general documentation improvements. There is no evidence of security vulnerabilities being addressed, no mention of security patches, and no references to CVEs or security incidents. The updates to maintenance guidance are routine operational recommendations without specific security context.
Diff
diff --git a/evs/latest/userguide/evs-lifecycle-mgmt.md b/evs/latest/userguide/evs-lifecycle-mgmt.md index 42db40b8f..3501c6d50 100644 --- a//evs/latest/userguide/evs-lifecycle-mgmt.md +++ b//evs/latest/userguide/evs-lifecycle-mgmt.md @@ -5 +5 @@ -VMware software updatesESXi host lifecyle and maintenance +VMware software updatesESX host lifecyle and maintenance @@ -11 +11 @@ This page describes your lifecycle management responsibilities within an Amazon -A key benefit of Amazon EVS is that you have complete control over your VMware architecture in the cloud. You can optimize the VMware Cloud Foundation (VCF) software stack to meet the unique demands of your applications. Because Amazon EVS is a self-managed service, you are responsible for the lifecycle management and maintenance of the VMware software used in the Amazon EVS environment, such as ESXi, vSphere, vSAN, NSX, and SDDC Manager. You are also responsible for maintaining any third-party integrations, such as data protection solutions that you integrate into your Amazon EVS hosts. +A key benefit of Amazon EVS is that you have complete control over your VMware architecture in the cloud. You can optimize the VMware Cloud Foundation (VCF) software stack to meet the unique demands of your applications. Because Amazon EVS is a self-managed service, you are responsible for the lifecycle management and maintenance of the VMware software used in the Amazon EVS environment, such as ESX, vSphere, vSAN, NSX, and SDDC Manager. You are also responsible for maintaining any third-party integrations, such as data protection solutions that you integrate into your Amazon EVS hosts. @@ -21 +21 @@ AWS is responsible for deploying the Amazon EVS environment with networking conf - * Deploying the required EVS VLAN subnets, elastic network interfaces, and four initial ESXi hosts. + * Deploying the required EVS VLAN subnets, elastic network interfaces, and four initial ESX hosts. @@ -44 +44 @@ A Tier-0 gateway and a Tier-1 gateway is created and configured as part of Amazo -If you have updated your ESXi version after the Amazon EVS environment deployment, SDDC manager may fail during VCF host validation in the commission hosts step. For steps to troubleshoot this issue, see [SDDC Manager fails VCF host validation during host commissioning](./troubleshooting.html#troubleshoot-sddc-failure-host-commission). +If you have updated your ESX version after the Amazon EVS environment deployment, SDDC manager may fail during VCF host validation in the commission hosts step. For steps to troubleshoot this issue, see [SDDC Manager fails VCF host validation during host commissioning](./troubleshooting.html#troubleshoot-sddc-failure-host-commission). @@ -46 +46 @@ If you have updated your ESXi version after the Amazon EVS environment deploymen -Amazon EVS only supports VMware Cloud Foundation (VCF) 5.2.1.x at this time. Per the [AWS shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/), you are responsible for applying any patches, updates, or upgrades to VCF software, including ESXi, vCenter Server, vSAN, NSX, SDDC Manager, and other integrated solutions, in your EVS environment. Post-deployment, we recommend that you review the VCF software version deployed by Amazon EVS and update as needed. You can obtain VCF updates through the [Broadcom support portal](https://support.broadcom.com/web/ecx). We also recommend that you establish and adhere to a regular maintenance schedule for updates and patches. +For information about VCF versions provided by Amazon EVS, see [VCF versions and EC2 instance types provided by Amazon EVS](./versions-provided.html). Per the [AWS shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/), you are responsible for applying any patches, updates, or upgrades to VCF software, including ESX, vCenter Server, vSAN, NSX, SDDC Manager, and other integrated solutions, in your EVS environment. Post-deployment, we recommend that you review the VCF software version deployed by Amazon EVS and update as needed. You can obtain VCF updates through the [Broadcom support portal](https://support.broadcom.com/web/ecx). We also recommend that you establish and adhere to a regular maintenance schedule for updates and patches. @@ -52 +52,5 @@ Amazon EVS does not support VMware Cloud Foundation 9 at this time. -Certain patches, updates, or upgrade may have impact on workloads running in your environment. Before patching, updating, or upgrading your VCF software, we recommend that you review the [VCF Lifecycle Management Guide](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-2/vmware-cloud-foundation-lifecycle-management.html) to understand how these changes will impact your environment. We also recommend that you test changes in a staging environment before deploying to production. You can review 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 understand the latest VCF 5.2.1 updates. +###### Note + +Amazon EVS does not provide all versions of VCF and ESX released by Broadcom. For software interoperability information, refer to the [Broadcom Interoperability Matrix](https://interopmatrix.broadcom.com/Interoperability?col=1). For full hardware compatibility with AWS EC2 instances, refer to the [Broadcom Compatibility Guide](https://compatibilityguide.broadcom.com/). + +Certain patches, updates, or upgrade may have impact on workloads running in your environment. Before patching, updating, or upgrading your VCF software, we recommend that you review the [VCF Lifecycle Management Guide](https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-2/vmware-cloud-foundation-lifecycle-management.html) to understand how these changes will impact your environment. We also recommend that you test changes in a staging environment before deploying to production. You can review 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) to understand the latest VCF 5.2.x updates. @@ -54 +58 @@ Certain patches, updates, or upgrade may have impact on workloads running in you -## ESXi host lifecyle and maintenance +## ESX host lifecyle and maintenance @@ -56 +60 @@ Certain patches, updates, or upgrade may have impact on workloads running in you -You are responsible for ESXi host lifecycle management and maintenance within the Amazon EVS environment, including monitoring host health and remediating host issues. For more information, see [Performing maintenance on your environment](./evs-env-maintenance.html). +You are responsible for ESX host lifecycle management and maintenance within the Amazon EVS environment, including monitoring host health and remediating host issues. For more information, see [Performing maintenance on your environment](./evs-env-maintenance.html). @@ -66 +70 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -VCF subscriptions +VCF versions and EC2 instances