@@ -31,9 +31,15 @@ namespace Amazon.Evs.Model
31
31
{
32
32
/// <summary>
33
33
/// Container for the parameters to the CreateEnvironment operation.
34
+ /// <note>
35
+ /// <para>
36
+ /// Amazon EVS is in public preview release and is subject to change.
37
+ ///
38
+ /// </note>
39
+ /// <para>
34
40
/// Creates an Amazon EVS environment that runs VCF software, such as SDDC Manager, NSX
35
41
/// Manager, and vCenter Server.
36
- ///
42
+ /// </para>
37
43
///
38
44
/// <para>
39
45
/// During environment creation, Amazon EVS performs validations on DNS settings, provisions
@@ -42,20 +48,16 @@ namespace Amazon.Evs.Model
42
48
///
43
49
/// <para>
44
50
/// It can take several hours to create an environment. After the deployment completes,
45
- /// you can configure VCF according to your unique requirements .
51
+ /// you can configure VCF in the vSphere user interface according to your needs .
46
52
/// </para>
47
53
/// <note>
48
54
/// <para>
49
55
/// You cannot use the <c>dedicatedHostId</c> and <c>placementGroupId</c> parameters together
50
56
/// in the same <c>CreateEnvironment</c> action. This results in a <c>ValidationException</c>
51
57
/// response.
52
58
/// </para>
53
- /// </note> <note>
54
- /// <para>
55
- /// EC2 instances created through Amazon EVS do not support associating an IAM instance
56
- /// profile.
57
- /// </para>
58
59
/// </note>
60
+ /// </para>
59
61
/// </summary>
60
62
public partial class CreateEnvironmentRequest : AmazonEvsRequest
61
63
{
@@ -110,7 +112,8 @@ internal bool IsSetClientToken()
110
112
/// <para>
111
113
/// The connectivity configuration for the environment. Amazon EVS requires that you
112
114
/// specify two route server peer IDs. During environment creation, the route server endpoints
113
- /// peer with the NSX edges over the NSX, providing BGP dynamic routing for overlay networks.
115
+ /// peer with the NSX edges over the NSX uplink subnet, providing BGP-based dynamic routing
116
+ /// for overlay networks.
114
117
/// </para>
115
118
/// </summary>
116
119
[ AWSProperty ( Required = true ) ]
@@ -157,9 +160,9 @@ internal bool IsSetEnvironmentName()
157
160
/// </para>
158
161
///
159
162
/// <para>
160
- /// For each host, you must provide the desired hostname, EC2 SSH key , and EC2 instance
161
- /// type. Optionally, you can also provide a partition or cluster placement group to use,
162
- /// or use Amazon EC2 Dedicated Hosts.
163
+ /// For each host, you must provide the desired hostname, EC2 SSH keypair name , and EC2
164
+ /// instance type. Optionally, you can also provide a partition or cluster placement group
165
+ /// to use, or use Amazon EC2 Dedicated Hosts.
163
166
/// </para>
164
167
/// </summary>
165
168
[ AWSProperty ( Required = true , Min = 4 , Max = 4 ) ]
@@ -178,9 +181,14 @@ internal bool IsSetHosts()
178
181
/// <summary>
179
182
/// Gets and sets the property InitialVlans.
180
183
/// <para>
181
- /// The initial VLAN subnets for the environment. You must specify a non-overlapping CIDR
182
- /// block for each VLAN subnet.
184
+ /// The initial VLAN subnets for the Amazon EVS environment.
183
185
/// </para>
186
+ /// <note>
187
+ /// <para>
188
+ /// For each Amazon EVS VLAN subnet, you must specify a non-overlapping CIDR block. Amazon
189
+ /// EVS VLAN subnets have a minimum CIDR block size of /28 and a maximum size of /24.
190
+ /// </para>
191
+ /// </note>
184
192
/// </summary>
185
193
[ AWSProperty ( Required = true ) ]
186
194
public InitialVlans InitialVlans
@@ -219,9 +227,9 @@ internal bool IsSetKmsKeyId()
219
227
/// Gets and sets the property LicenseInfo.
220
228
/// <para>
221
229
/// The license information that Amazon EVS requires to create an environment. Amazon
222
- /// EVS requires two license keys: a VCF solution key and a vSAN license key. VCF licenses
223
- /// must have sufficient core entitlements to cover vCPU core and vSAN storage capacity
224
- /// needs .
230
+ /// EVS requires two license keys: a VCF solution key and a vSAN license key. The VCF
231
+ /// solution key must cover a minimum of 256 cores. The vSAN license key must provide
232
+ /// at least 110 TiB of vSAN capacity .
225
233
/// </para>
226
234
///
227
235
/// <para>
@@ -355,9 +363,11 @@ internal bool IsSetTags()
355
363
/// <summary>
356
364
/// Gets and sets the property TermsAccepted.
357
365
/// <para>
358
- /// Customer confirmation that the customer has purchased and maintains sufficient VCF
359
- /// software licenses to cover all physical processor cores in the environment, in compliance
360
- /// with VMware's licensing requirements and terms of use.
366
+ /// Customer confirmation that the customer has purchased and will continue to maintain
367
+ /// the required number of VCF software licenses to cover all physical processor cores
368
+ /// in the Amazon EVS environment. Information about your VCF software in Amazon EVS will
369
+ /// be shared with Broadcom to verify license compliance. Amazon EVS does not validate
370
+ /// license keys. To validate license keys, visit the Broadcom support portal.
361
371
/// </para>
362
372
/// </summary>
363
373
[ AWSProperty ( Required = true ) ]
@@ -417,8 +427,7 @@ internal bool IsSetVcfVersion()
417
427
/// <summary>
418
428
/// Gets and sets the property VpcId.
419
429
/// <para>
420
- /// A unique ID for the VPC that connects to the environment control plane for service
421
- /// access.
430
+ /// A unique ID for the VPC that the environment is deployed inside.
422
431
/// </para>
423
432
///
424
433
/// <para>
@@ -427,22 +436,22 @@ internal bool IsSetVcfVersion()
427
436
/// </para>
428
437
///
429
438
/// <para>
430
- /// The VPC that you select must have a valid DHCP option set with domain name, at least
439
+ /// The VPC that you specify must have a valid DHCP option set with domain name, at least
431
440
/// two DNS servers, and an NTP server. These settings are used to configure your VCF
432
- /// appliances and hosts.
433
- /// </para>
434
- ///
435
- /// <para>
436
- /// If you plan to use HCX over the internet, choose a VPC that has a primary CIDR block
437
- /// and a /28 secondary CIDR block from an IPAM pool. Make sure that your VPC also has
438
- /// an attached internet gateway.
441
+ /// appliances and hosts. The VPC cannot be used with any other deployed Amazon EVS environment.
442
+ /// Amazon EVS does not provide multi-VPC support for environments at this time.
439
443
/// </para>
440
444
///
441
445
/// <para>
442
446
/// Amazon EVS does not support the following Amazon Web Services networking options for
443
447
/// NSX overlay connectivity: cross-Region VPC peering, Amazon S3 gateway endpoints, or
444
448
/// Amazon Web Services Direct Connect virtual private gateway associations.
445
449
/// </para>
450
+ /// <note>
451
+ /// <para>
452
+ /// Ensure that you specify a VPC that is adequately sized to accommodate the {evws} subnets.
453
+ /// </para>
454
+ /// </note>
446
455
/// </summary>
447
456
[ AWSProperty ( Required = true , Min = 12 , Max = 21 ) ]
448
457
public string VpcId
0 commit comments