# Data Object - VsanPrepareVsanForVcsaSpec(vim.vsan.VsanPrepareVsanForVcsaSpec)

Parameter to
  VsanPrepareVsanForVcsa
Extends
  DynamicData
See also
  VimVsanHostDiskMappingCreationSpec, VsanDataEfficiencyConfig, VsanHostEncryptionInfo
Since
  vSphere API 6.5

## Data Object Description

All configuration parameters for preparing vSAN on a host where VCSA will be deployed

Properties

Name | Type | Description
--- | --- | ---
taskId* | xsd:string | Unique identifier of the task this progress report is for.
vsanDataEfficiencyConfig* | VsanDataEfficiencyConfig | The data efficiency config for vSAN.
vsanDataEncryptionConfig* | VsanHostEncryptionInfo | The data encryption config that will be used to bootstrap single node vSAN cluster. Right now only vSAN encryption with AWS KMS running in VMware Cloud on AWS is supported. This is for VMware internal use. Caller needs to specify the KMS server address "arn:aws:kms" to indicate AWS KMS is used for vSAN encryption and credentials will be automatically configured by vSAN when running in VMC. Since vSAN API VMC M5
vsanDiskMappingCreationSpec* | VimVsanHostDiskMappingCreationSpec | If set, this is used to call InitializeDiskMappings() to create vSAN disk groups. If not set, Vcsa Deployer will skip claiming disks.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanPrepareVsanForVcsaSpec"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="vsanDiskMappingCreationSpec" type="vsan:VimVsanHostDiskMappingCreationSpec" minOccurs="0"/> <element name="vsanDataEfficiencyConfig" type="vsan:VsanDataEfficiencyConfig" minOccurs="0"/> <element name="taskId" type="xsd:string" minOccurs="0"/> <element name="vsanDataEncryptionConfig" type="vsan:VsanHostEncryptionInfo" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>