Values.EnvironmentSourceAn object that represents an Amazon EVS environment.
type nonrec t = {environmentId : EnvironmentId.t option;The unique ID for the environment.
*)environmentState : EnvironmentState.t option;The state of an environment.
*)stateDetails : StateDetails.t option;A detailed description of the environmentState of an environment.
*)createdAt : Timestamp.t option;The date and time that the environment was created.
*)modifiedAt : Timestamp.t option;The date and time that the environment was modified.
*)environmentArn : Arn.t option;The Amazon Resource Name (ARN) that is associated with the environment.
*)environmentName : EnvironmentName.t option;The name of the environment.
*)vpcId : VpcId.t option;The VPC associated with the environment.
*)serviceAccessSubnetId : SubnetId.t option;The subnet that is used to establish connectivity between the Amazon EVS control plane and VPC. Amazon EVS uses this subnet to perform validations and create the environment.
*)vcfVersion : VcfVersion.t option;The VCF version of the environment.
*)termsAccepted : Boolean.t option;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.
*)licenseInfo : LicenseInfoList.t option;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 in the Amazon EVS User Guide.
*)siteId : String_.t option;The Broadcom Site ID that is associated with your Amazon EVS environment. Amazon EVS uses the Broadcom Site ID that you provide to meet Broadcom VCF license usage reporting requirements for Amazon EVS.
*)environmentStatus : CheckResult.t option;Reports impaired functionality that stems from issues internal to the environment, such as impaired reachability.
*)checks : ChecksList.t option;A check on the environment to identify instance health and VMware VCF licensing issues.
*)connectivityInfo : ConnectivityInfo.t option;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 uplink VLAN for connectivity to the NSX overlay network.
*)vcfHostnames : VcfHostnames.t option;The DNS hostnames to be used by the VCF management appliances in your environment. For environment creation to be successful, each hostname entry must resolve to a domain name that you've registered in your DNS service of choice and configured in the DHCP option set of your VPC. DNS hostnames cannot be changed after environment creation has started.
*)kmsKeyId : String_.t option;The Amazon Web Services KMS key ID that Amazon Web Services Secrets Manager uses to encrypt secrets that are associated with the environment. These secrets contain the VCF credentials that are needed to install vCenter Server, NSX, and SDDC Manager. By default, Amazon EVS use the Amazon Web Services Secrets Manager managed key aws/secretsmanager. You can also specify a customer managed key.
*)serviceAccessSecurityGroups : ServiceAccessSecurityGroups.t option;The security groups that allow traffic between the Amazon EVS control plane and your VPC for service access. If a security group is not specified, Amazon EVS uses the default security group in your account for service access.
*)credentials : SecretList.t option;The VCF credentials that are stored as Amazon EVS managed secrets in Amazon Web Services Secrets Manager. Amazon EVS stores credentials that are needed to install vCenter Server, NSX, and SDDC Manager.
*)}val make :
?environmentId:??? ->
?environmentState:??? ->
?stateDetails:??? ->
?createdAt:??? ->
?modifiedAt:??? ->
?environmentArn:??? ->
?environmentName:??? ->
?vpcId:??? ->
?serviceAccessSubnetId:??? ->
?vcfVersion:??? ->
?termsAccepted:??? ->
?licenseInfo:??? ->
?siteId:??? ->
?environmentStatus:??? ->
?checks:??? ->
?connectivityInfo:??? ->
?vcfHostnames:??? ->
?kmsKeyId:??? ->
?serviceAccessSecurityGroups:??? ->
?credentials:??? ->
unit ->
tval to_value :
t ->
[> `Structure of
(string
* [> `Boolean of Boolean.t
| `Enum of string
| `List of
[> `Structure of
(string
* [> `Enum of string
| `String of SolutionKey.t
| `Timestamp of Timestamp.t ])
list ]
list
| `String of EnvironmentId.t
| `Structure of
(string
* [> `List of [> `String of RouteServerPeering.t ] list
| `String of HostName.t ])
list
| `Timestamp of Timestamp.t ])
list ]