AWS evs documentation change
Summary
Updated terminology from 'custom vendor add-on' to branded 'Amazon EVS Custom Addon' for consistency. No functional changes.
Security assessment
The change is purely terminological/branding update without any security implications. No security vulnerabilities, configurations, or features are mentioned or modified in the documentation update.
Diff
diff --git a/evs/latest/userguide/evs-env-create-host.md b/evs/latest/userguide/evs-env-create-host.md index a01599ca2..e2ccdf4bf 100644 --- a//evs/latest/userguide/evs-env-create-host.md +++ b//evs/latest/userguide/evs-env-create-host.md @@ -21 +21 @@ Follow these steps to create an Amazon EVS host. -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). +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).