AWS cli documentation change
Summary
Added support for self-deployed VCF mode where customers install VCF themselves. Updated parameters to be optional in self-deployed mode, expanded health checks, and improved documentation clarity.
Security assessment
The changes introduce a new deployment mode (self-deployed) and update parameter requirements but contain no evidence of addressing specific vulnerabilities. The expanded health checks improve operational monitoring but don't directly mitigate security risks.
Diff
diff --git a/cli/latest/reference/evs/create-environment.md b/cli/latest/reference/evs/create-environment.md index b7b9e16a9..4ad6d804a 100644 --- a//cli/latest/reference/evs/create-environment.md +++ b//cli/latest/reference/evs/create-environment.md @@ -15 +15 @@ - * [AWS CLI 2.35.11 Command Reference](../../index.html) » + * [AWS CLI 2.35.13 Command Reference](../../index.html) » @@ -61 +61,3 @@ Creates an Amazon EVS environment that runs VCF software, such as SDDC Manager, -During environment creation, Amazon EVS performs validations on DNS settings, provisions VLAN subnets and hosts, and deploys the supplied version of VCF. +### Note + +When you specify `SELF_DEPLOYED` for `vcfVersion` , Amazon EVS provisions only the VLAN subnets; no hosts are added and no VCF installation is performed. After the environment is created, you can add hosts with `CreateEnvironmentHost` and install VCF yourself. The `licenseInfo` , `hosts` , `vcfHostnames` , `siteId` , and `connectivityInfo` parameters are not supported in this mode. @@ -63 +65 @@ During environment creation, Amazon EVS performs validations on DNS settings, pr -It can take several hours to create an environment. After the deployment completes, you can configure VCF in the vSphere user interface according to your needs. +When you specify any other VCF version, Amazon EVS installs and configures VCF for you. For more information, see [Self-deployed mode](https://docs.aws.amazon.com/evs/latest/userguide/getting-started-self-deployed.html) in the _Amazon EVS User Guide_ . @@ -67 +69 @@ It can take several hours to create an environment. After the deployment complet -When creating a new environment, the default ESX version for the selected VCF version will be used, you cannot choose a specific ESX version in `CreateEnvironment` action. When a host has been added with a specific ESX version, it can only be upgraded using vCenter Lifecycle Manager. +When Amazon EVS installs VCF, the default ESX version for the selected VCF version will be used. After a host is added with a specific ESX version, it can only be upgraded using vCenter Lifecycle Manager. @@ -88 +89,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/evs-20 - --license-info <value> @@ -90,4 +91,5 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/evs-20 - --hosts <value> - --connectivity-info <value> - --vcf-hostnames <value> - --site-id <value> + [--connectivity-info <value>] + [--license-info <value>] + [--hosts <value>] + [--vcf-hostnames <value>] + [--site-id <value>] @@ -268 +270 @@ JSON Syntax: -> The subnet that is used to establish connectivity between the Amazon EVS control plane and VPC. Amazon EVS uses this subnet to validate mandatory DNS records for your VCF appliances and hosts and create the environment. +> The subnet that is used to establish connectivity between the Amazon EVS control plane and VPC. The Amazon EVS control plane uses this subnet to interface with your environment. This includes validating DNS records and enabling Amazon EVS Connectors. @@ -280,0 +283,5 @@ JSON Syntax: +> +> * `SELF_DEPLOYED` : You install VCF yourself. The `licenseInfo` , `hosts` , `vcfHostnames` , `siteId` , and `connectivityInfo` parameters are not supported. +> * Any other valid value: Amazon EVS installs and configures VCF for you in the version you specify. +> + @@ -285,0 +293 @@ JSON Syntax: +> * `SELF_DEPLOYED` @@ -291,60 +299 @@ JSON Syntax: -> Customer confirmation that the customer has purchased and will continue to maintain the required number of VCF software licenses to cover all physical processor cores in the Amazon EVS environment. Information about your VCF software in Amazon EVS will be shared with Broadcom to verify license compliance. Amazon EVS does not validate license keys. To validate license keys, visit the Broadcom support portal. - -`--license-info` (list) [required] - -> The license information that Amazon EVS requires to create an environment. Amazon EVS requires two license keys: a VCF solution key and a vSAN license key. The VCF solution key must meet minimum core requirements, and the vSAN license key must meet minimum capacity requirements for your selected instance type. -> -> For information about minimum license requirements, see [the VCF subscriptions section](https://docs.aws.amazon.com/evs/latest/userguide/vcf-license-mgmt.html) in the _Amazon EVS User Guide_ . -> -> VCF licenses can be used for only one Amazon EVS environment. Amazon EVS does not support reuse of VCF licenses for multiple environments. -> -> VCF license information can be retrieved from the Broadcom portal. -> -> Constraints: -> -> * min: `1` -> * max: `1` -> - -> -> (structure) -> ->> The license information that Amazon EVS requires to create an environment. Amazon EVS requires two license keys: a VCF solution key and a vSAN license key. ->> ->> solutionKey -> (string) [required] ->> ->>> The VCF solution key. This license unlocks VMware VCF product features, including vSphere, NSX, SDDC Manager, and vCenter Server. The VCF solution key must meet the instance-type-specific minimum core requirements. ->>> ->>> Constraints: ->>> ->>> * pattern: `[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}` ->>> - ->> ->> vsanKey -> (string) [required] ->> ->>> The VSAN license key. This license unlocks vSAN features. The vSAN license key must meet the instance-type-specific minimum capacity requirements. ->>> ->>> Constraints: ->>> ->>> * pattern: `[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}` ->>> - - -Shorthand Syntax: - - - solutionKey=string,vsanKey=string ... - - -JSON Syntax: - - - [ - { - "solutionKey": "string", - "vsanKey": "string" - } - ... - ] - +> Confirmation that the customer has purchased and will continue to maintain the required number of VCF software licenses to cover all physical processor cores in the Amazon EVS environment. Information about your VCF software in Amazon EVS will be shared with Broadcom to verify license compliance. Amazon EVS does not validate license keys. To validate license keys, visit the Broadcom support portal. @@ -569 +518 @@ JSON Syntax: -`--hosts` (list) [required] +`--connectivity-info` (structure) @@ -571 +520,7 @@ JSON Syntax: -> The ESX hosts to add to the environment. Amazon EVS requires that you provide details for a minimum of 4 hosts during environment creation. +> The connectivity configuration for the environment. Amazon EVS requires that you specify two route server peer IDs. During environment creation, the route server endpoints peer with the NSX edges over the NSX uplink subnet, providing BGP-based dynamic routing for overlay networks. +> +> ### Note +> +> Not supported when `vcfVersion` is `SELF_DEPLOYED` . +> +> privateRouteServerPeerings -> (list) [required] @@ -573 +528,102 @@ JSON Syntax: -> For each host, you must provide the desired hostname, EC2 SSH keypair name, and EC2 instance type. Optionally, you can also provide a partition or cluster placement group to use, or use Amazon EC2 Dedicated Hosts. +>> The unique IDs for private route server peers. +>> +>> Constraints: +>> +>> * min: `2` +>> * max: `2` +>> + +>> +>> (string) +>> +>>> Constraints: +>>> +>>> * min: `3` +>>> * max: `21` +>>> + + +Shorthand Syntax: + + + privateRouteServerPeerings=string,string + + +JSON Syntax: + + + { + "privateRouteServerPeerings": ["string", ...] + } + + +`--license-info` (list) + +> The license information that Amazon EVS requires to create an environment. Amazon EVS requires two license keys: a VCF solution key and a vSAN license key. The VCF solution key must meet minimum core requirements, and the vSAN license key must meet minimum capacity requirements for your selected instance type. +> +> For information about minimum license requirements, see [the VCF subscriptions section](https://docs.aws.amazon.com/evs/latest/userguide/vcf-license-mgmt.html) in the _Amazon EVS User Guide_ . +> +> VCF licenses can be used for only one Amazon EVS environment. Amazon EVS does not support reuse of VCF licenses for multiple environments. +> +> VCF license information can be retrieved from the Broadcom portal. +> +> ### Note +> +> Not supported when `vcfVersion` is `SELF_DEPLOYED` . +> +> Constraints: +> +> * min: `1` +> * max: `1` +> + +> +> (structure) +> +>> The license information that Amazon EVS requires to create an environment. Amazon EVS requires two license keys: a VCF solution key and a vSAN license key. +>> +>> solutionKey -> (string) [required] +>> +>>> The VCF solution key. This license unlocks VMware VCF product features, including vSphere, NSX, SDDC Manager, and vCenter Server. The VCF solution key must meet the instance-type-specific minimum core requirements. +>>> +>>> Constraints: +>>> +>>> * pattern: `[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}` +>>> + +>> +>> vsanKey -> (string) [required] +>> +>>> The VSAN license key. This license unlocks vSAN features. The vSAN license key must meet the instance-type-specific minimum capacity requirements. +>>> +>>> Constraints: +>>> +>>> * pattern: `[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}-[a-zA-Z0-9]{5}` +>>> + + +Shorthand Syntax: + + + solutionKey=string,vsanKey=string ... + +