Interface CreateFileSystemLustreMetadataConfiguration.Builder

All Superinterfaces:
Buildable, CopyableBuilder<CreateFileSystemLustreMetadataConfiguration.Builder,CreateFileSystemLustreMetadataConfiguration>, SdkBuilder<CreateFileSystemLustreMetadataConfiguration.Builder,CreateFileSystemLustreMetadataConfiguration>, SdkPojo
Enclosing class:
CreateFileSystemLustreMetadataConfiguration
public static interface CreateFileSystemLustreMetadataConfiguration.Builder extends SdkPojo, CopyableBuilder<CreateFileSystemLustreMetadataConfiguration.Builder,CreateFileSystemLustreMetadataConfiguration>

  • Method Details

    • iops

      CreateFileSystemLustreMetadataConfiguration.Builder iops(Integer iops)

      (USER_PROVISIONED mode only) Specifies the number of Metadata IOPS to provision for the file system. This parameter sets the maximum rate of metadata disk IOPS supported by the file system. Valid values are 1500, 3000, 6000, 12000, and multiples of 12000 up to a maximum of 192000.

      Iops doesn’t have a default value. If you're using USER_PROVISIONED mode, you can choose to specify a valid value. If you're using AUTOMATIC mode, you cannot specify a value because FSx for Lustre automatically sets the value based on your file system storage capacity.

      Parameters:
      iops - (USER_PROVISIONED mode only) Specifies the number of Metadata IOPS to provision for the file system. This parameter sets the maximum rate of metadata disk IOPS supported by the file system. Valid values are 1500, 3000, 6000, 12000, and multiples of 12000 up to a maximum of 192000.

      Iops doesn’t have a default value. If you're using USER_PROVISIONED mode, you can choose to specify a valid value. If you're using AUTOMATIC mode, you cannot specify a value because FSx for Lustre automatically sets the value based on your file system storage capacity.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • mode

      CreateFileSystemLustreMetadataConfiguration.Builder mode(String mode)

      The metadata configuration mode for provisioning Metadata IOPS for an FSx for Lustre file system using a PERSISTENT_2 deployment type.

      • In AUTOMATIC mode, FSx for Lustre automatically provisions and scales the number of Metadata IOPS for your file system based on your file system storage capacity.

      • In USER_PROVISIONED mode, you specify the number of Metadata IOPS to provision for your file system.

      Parameters:
      mode - The metadata configuration mode for provisioning Metadata IOPS for an FSx for Lustre file system using a PERSISTENT_2 deployment type.

      • In AUTOMATIC mode, FSx for Lustre automatically provisions and scales the number of Metadata IOPS for your file system based on your file system storage capacity.

      • In USER_PROVISIONED mode, you specify the number of Metadata IOPS to provision for your file system.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • mode

      CreateFileSystemLustreMetadataConfiguration.Builder mode(MetadataConfigurationMode mode)

      The metadata configuration mode for provisioning Metadata IOPS for an FSx for Lustre file system using a PERSISTENT_2 deployment type.

      • In AUTOMATIC mode, FSx for Lustre automatically provisions and scales the number of Metadata IOPS for your file system based on your file system storage capacity.

      • In USER_PROVISIONED mode, you specify the number of Metadata IOPS to provision for your file system.

      Parameters:
      mode - The metadata configuration mode for provisioning Metadata IOPS for an FSx for Lustre file system using a PERSISTENT_2 deployment type.

      • In AUTOMATIC mode, FSx for Lustre automatically provisions and scales the number of Metadata IOPS for your file system based on your file system storage capacity.

      • In USER_PROVISIONED mode, you specify the number of Metadata IOPS to provision for your file system.

      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also: