Module Smaws_Client_FSx.Types

type nonrec flag = bool
type nonrec general_ar_n = string
type nonrec windows_fsrm_configuration = {
  1. event_log_destination : general_ar_n option;
    (*

    The Amazon Resource Name (ARN) for the destination of the FSRM event logs. The destination can be any Amazon CloudWatch Logs log group ARN or Amazon Kinesis Data Firehose delivery stream ARN.

    The name of the Amazon CloudWatch Logs log group must begin with the /aws/fsx prefix. The name of the Amazon Kinesis Data Firehose delivery stream must begin with the aws-fsx prefix.

    The destination ARN (either CloudWatch Logs log group or Kinesis Data Firehose delivery stream) must be in the same Amazon Web Services partition, Amazon Web Services Region, and Amazon Web Services account as your Amazon FSx file system.

    *)
  2. fsrm_service_enabled : flag;
    (*

    Specifies whether FSRM is enabled or disabled on the file system. When TRUE, the FSRM service is enabled and monitor file operations according to configured policies. When FALSE or omitted, FSRM is disabled. The default value is FALSE.

    *)
}

The File Server Resource Manager (FSRM) configuration that Amazon FSx for Windows File Server uses for the file system. When FSRM is enabled, you can manage and monitor storage quotas, file screening, storage reports, and file classification.

type nonrec directory_id = string
type nonrec active_directory_fully_qualified_name = string
type nonrec organizational_unit_distinguished_name = string
type nonrec file_system_administrators_group_name = string
type nonrec directory_user_name = string
type nonrec ip_address = string
type nonrec dns_ips = ip_address list
type nonrec customer_secrets_manager_ar_n = string
type nonrec self_managed_active_directory_attributes = {
  1. domain_join_service_account_secret : customer_secrets_manager_ar_n option;
    (*

    The Amazon Resource Name (ARN) of the Amazon Web Services Secrets Manager secret containing the service account credentials used to join the file system to your self-managed Active Directory domain.

    *)
  2. dns_ips : dns_ips option;
    (*

    A list of up to three IP addresses of DNS servers or domain controllers in the self-managed AD directory.

    *)
  3. user_name : directory_user_name option;
    (*

    The user name for the service account on your self-managed AD domain that FSx uses to join to your AD domain.

    *)
  4. file_system_administrators_group : file_system_administrators_group_name option;
    (*

    The name of the domain group whose members have administrative privileges for the FSx file system.

    *)
  5. organizational_unit_distinguished_name : organizational_unit_distinguished_name option;
    (*

    The fully qualified distinguished name of the organizational unit within the self-managed AD directory to which the Windows File Server or ONTAP storage virtual machine (SVM) instance is joined.

    *)
  6. domain_name : active_directory_fully_qualified_name option;
    (*

    The fully qualified domain name of the self-managed AD directory.

    *)
}

The configuration of the self-managed Microsoft Active Directory (AD) directory to which the Windows File Server or ONTAP storage virtual machine (SVM) instance is joined.

type nonrec windows_deployment_type =
  1. | SINGLE_AZ_2
  2. | SINGLE_AZ_1
  3. | MULTI_AZ_1
type nonrec dns_name = string
type nonrec subnet_id = string
type nonrec megabytes_per_second = int
type nonrec file_system_maintenance_operation =
  1. | BACKING_UP
  2. | PATCHING

An enumeration specifying the currently ongoing maintenance operation.

type nonrec file_system_maintenance_operations = file_system_maintenance_operation list
type nonrec weekly_time = string
type nonrec daily_time = string
type nonrec automatic_backup_retention_days = int
type nonrec alternate_dns_name = string
type nonrec alias_lifecycle =
  1. | DELETE_FAILED
  2. | CREATE_FAILED
  3. | DELETING
  4. | CREATING
  5. | AVAILABLE
type nonrec alias = {
  1. lifecycle : alias_lifecycle option;
    (*

    Describes the state of the DNS alias.

    • AVAILABLE - The DNS alias is associated with an Amazon FSx file system.
    • CREATING - Amazon FSx is creating the DNS alias and associating it with the file system.
    • CREATE_FAILED - Amazon FSx was unable to associate the DNS alias with the file system.
    • DELETING - Amazon FSx is disassociating the DNS alias from the file system and deleting it.
    • DELETE_FAILED - Amazon FSx was unable to disassociate the DNS alias from the file system.
    *)
  2. name : alternate_dns_name option;
    (*

    The name of the DNS alias. The alias name has to meet the following requirements:

    • Formatted as a fully-qualified domain name (FQDN), hostname.domain, for example, accounting.example.com.
    • Can contain alphanumeric characters, the underscore (_), and the hyphen (-).
    • Cannot start or end with a hyphen.
    • Can start with a numeric.

    For DNS names, Amazon FSx stores alphabetic characters as lowercase letters (a-z), regardless of how you specify them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes.

    *)
}

A DNS alias that is associated with the file system. You can use a DNS alias to access a file system using user-defined DNS names, in addition to the default DNS name that Amazon FSx assigns to the file system. For more information, see DNS aliases in the FSx for Windows File Server User Guide.

type nonrec aliases = alias list
type nonrec windows_access_audit_log_level =
  1. | SUCCESS_AND_FAILURE
  2. | FAILURE_ONLY
  3. | SUCCESS_ONLY
  4. | DISABLED
type nonrec windows_audit_log_configuration = {
  1. audit_log_destination : general_ar_n option;
    (*

    The Amazon Resource Name (ARN) for the destination of the audit logs. The destination can be any Amazon CloudWatch Logs log group ARN or Amazon Kinesis Data Firehose delivery stream ARN.

    The name of the Amazon CloudWatch Logs log group must begin with the /aws/fsx prefix. The name of the Amazon Kinesis Data Firehose delivery stream must begin with the aws-fsx prefix.

    The destination ARN (either CloudWatch Logs log group or Kinesis Data Firehose delivery stream) must be in the same Amazon Web Services partition, Amazon Web Services Region, and Amazon Web Services account as your Amazon FSx file system.

    *)
  2. file_share_access_audit_log_level : windows_access_audit_log_level;
    (*

    Sets which attempt type is logged by Amazon FSx for file share accesses.

    • SUCCESS_ONLY - only successful attempts to access file shares are logged.
    • FAILURE_ONLY - only failed attempts to access file shares are logged.
    • SUCCESS_AND_FAILURE - both successful attempts and failed attempts to access file shares are logged.
    • DISABLED - access auditing of file shares is turned off.
    *)
  3. file_access_audit_log_level : windows_access_audit_log_level;
    (*

    Sets which attempt type is logged by Amazon FSx for file and folder accesses.

    • SUCCESS_ONLY - only successful attempts to access files or folders are logged.
    • FAILURE_ONLY - only failed attempts to access files or folders are logged.
    • SUCCESS_AND_FAILURE - both successful attempts and failed attempts to access files or folders are logged.
    • DISABLED - access auditing of files and folders is turned off.
    *)
}

The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system. For more information, see File access auditing.

type nonrec disk_iops_configuration_mode =
  1. | USER_PROVISIONED
  2. | AUTOMATIC
type nonrec iops = Smaws_Lib.CoreTypes.Int64.t
type nonrec disk_iops_configuration = {
  1. iops : iops option;
    (*

    The total number of SSD IOPS provisioned for the file system.

    The minimum and maximum values for this property depend on the value of HAPairs and StorageCapacity. The minimum value is calculated as StorageCapacity * 3 * HAPairs (3 IOPS per GB of StorageCapacity). The maximum value is calculated as 200,000 * HAPairs.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) if the value of Iops is outside of the minimum or maximum values.

    *)
  2. mode : disk_iops_configuration_mode option;
    (*

    Specifies whether the file system is using the AUTOMATIC setting of SSD IOPS of 3 IOPS per GB of storage capacity, or if it using a USER_PROVISIONED value.

    *)
}

The SSD IOPS (input/output operations per second) configuration for an Amazon FSx for NetApp ONTAP, Amazon FSx for Windows File Server, or FSx for OpenZFS file system. By default, Amazon FSx automatically provisions 3 IOPS per GB of storage capacity. You can provision additional IOPS per GB of storage. The configuration consists of the total number of provisioned SSD IOPS and how it is was provisioned, or the mode (by the customer or by Amazon FSx).

type nonrec windows_file_system_configuration = {
  1. fsrm_configuration : windows_fsrm_configuration option;
    (*

    The File Server Resource Manager (FSRM) configuration that Amazon FSx for Windows File Server uses for the file system. FSRM is disabled by default.

    *)
  2. preferred_file_server_ipv6 : ip_address option;
    (*

    For MULTI_AZ_1 deployment types, the IPv6 address of the primary, or preferred, file server. Use this IP address when mounting the file system on Linux SMB clients or Windows SMB clients that are not joined to a Microsoft Active Directory. Applicable for all Windows file system deployment types. This IPv6 address is temporarily unavailable when the file system is undergoing maintenance. For Linux and Windows SMB clients that are joined to an Active Directory, use the file system's DNSName instead.

    *)
  3. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS (input/output operations per second) configuration for an Amazon FSx for Windows file system. By default, Amazon FSx automatically provisions 3 IOPS per GiB of storage capacity. You can provision additional IOPS per GiB of storage, up to the maximum limit associated with your chosen throughput capacity.

    *)
  4. audit_log_configuration : windows_audit_log_configuration option;
    (*

    The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system.

    *)
  5. aliases : aliases option;
  6. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags on the file system should be copied to backups. This value defaults to false. If it's set to true, all tags on the file system are copied to all automatic backups and any user-initiated backups where the user doesn't specify any tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    *)
  7. automatic_backup_retention_days : automatic_backup_retention_days option;
    (*

    The number of days to retain automatic backups. Setting this to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days.

    *)
  8. daily_automatic_backup_start_time : daily_time option;
    (*

    The preferred time to take daily automatic backups, in the UTC time zone.

    *)
  9. weekly_maintenance_start_time : weekly_time option;
    (*

    The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.

    *)
  10. maintenance_operations_in_progress : file_system_maintenance_operations option;
    (*

    The list of maintenance operations in progress for this file system.

    *)
  11. throughput_capacity : megabytes_per_second option;
    (*

    The throughput of the Amazon FSx file system, measured in megabytes per second.

    *)
  12. preferred_file_server_ip : ip_address option;
    (*

    For MULTI_AZ_1 deployment types, the IPv4 address of the primary, or preferred, file server.

    Use this IP address when mounting the file system on Linux SMB clients or Windows SMB clients that are not joined to a Microsoft Active Directory. Applicable for all Windows file system deployment types. This IPv4 address is temporarily unavailable when the file system is undergoing maintenance. For Linux and Windows SMB clients that are joined to an Active Directory, use the file system's DNSName instead. For more information on mapping and mounting file shares, see Accessing data using file shares.

    *)
  13. preferred_subnet_id : subnet_id option;
    (*

    For MULTI_AZ_1 deployment types, it specifies the ID of the subnet where the preferred file server is located. Must be one of the two subnet IDs specified in SubnetIds property. Amazon FSx serves traffic from this subnet except in the event of a failover to the secondary file server.

    For SINGLE_AZ_1 and SINGLE_AZ_2 deployment types, this value is the same as that for SubnetIDs. For more information, see Availability and durability: Single-AZ and Multi-AZ file systems.

    *)
  14. remote_administration_endpoint : dns_name option;
    (*

    For MULTI_AZ_1 deployment types, use this endpoint when performing administrative tasks on the file system using Amazon FSx Remote PowerShell.

    For SINGLE_AZ_1 and SINGLE_AZ_2 deployment types, this is the DNS name of the file system.

    This endpoint is temporarily unavailable when the file system is undergoing maintenance.

    *)
  15. deployment_type : windows_deployment_type option;
    (*

    Specifies the file system deployment type, valid values are the following:

    • MULTI_AZ_1 - Specifies a high availability file system that is configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability, and supports SSD and HDD storage.
    • SINGLE_AZ_1 - (Default) Specifies a file system that is configured for single AZ redundancy, only supports SSD storage.
    • SINGLE_AZ_2 - Latest generation Single AZ file system. Specifies a file system that is configured for single AZ redundancy and supports SSD and HDD storage.

    For more information, see Single-AZ and Multi-AZ File Systems.

    *)
  16. self_managed_active_directory_configuration : self_managed_active_directory_attributes option;
  17. active_directory_id : directory_id option;
    (*

    The ID for an existing Amazon Web Services Managed Microsoft Active Directory instance that the file system is joined to.

    *)
}

The configuration for this Microsoft Windows file system.

type nonrec windows_audit_log_create_configuration = {
  1. audit_log_destination : general_ar_n option;
    (*

    The Amazon Resource Name (ARN) that specifies the destination of the audit logs.

    The destination can be any Amazon CloudWatch Logs log group ARN or Amazon Kinesis Data Firehose delivery stream ARN, with the following requirements:

    • The destination ARN that you provide (either CloudWatch Logs log group or Kinesis Data Firehose delivery stream) must be in the same Amazon Web Services partition, Amazon Web Services Region, and Amazon Web Services account as your Amazon FSx file system.
    • The name of the Amazon CloudWatch Logs log group must begin with the /aws/fsx prefix. The name of the Amazon Kinesis Data Firehose delivery stream must begin with the aws-fsx prefix.
    • If you do not provide a destination in AuditLogDestination, Amazon FSx will create and use a log stream in the CloudWatch Logs /aws/fsx/windows log group.
    • If AuditLogDestination is provided and the resource does not exist, the request will fail with a BadRequest error.
    • If FileAccessAuditLogLevel and FileShareAccessAuditLogLevel are both set to DISABLED, you cannot specify a destination in AuditLogDestination.
    *)
  2. file_share_access_audit_log_level : windows_access_audit_log_level;
    (*

    Sets which attempt type is logged by Amazon FSx for file share accesses.

    • SUCCESS_ONLY - only successful attempts to access file shares are logged.
    • FAILURE_ONLY - only failed attempts to access file shares are logged.
    • SUCCESS_AND_FAILURE - both successful attempts and failed attempts to access file shares are logged.
    • DISABLED - access auditing of file shares is turned off.
    *)
  3. file_access_audit_log_level : windows_access_audit_log_level;
    (*

    Sets which attempt type is logged by Amazon FSx for file and folder accesses.

    • SUCCESS_ONLY - only successful attempts to access files or folders are logged.
    • FAILURE_ONLY - only failed attempts to access files or folders are logged.
    • SUCCESS_AND_FAILURE - both successful attempts and failed attempts to access files or folders are logged.
    • DISABLED - access auditing of files and folders is turned off.
    *)
}

The Windows file access auditing configuration used when creating or updating an Amazon FSx for Windows File Server file system.

type nonrec vpc_id = string
type nonrec creation_time = Smaws_Lib.CoreTypes.Timestamp.t
type nonrec file_system_id = string
type nonrec volume_lifecycle =
  1. | AVAILABLE
  2. | PENDING
  3. | MISCONFIGURED
  4. | FAILED
  5. | DELETING
  6. | CREATED
  7. | CREATING
type nonrec volume_name = string
type nonrec flex_cache_endpoint_type =
  1. | CACHE
  2. | ORIGIN
  3. | NONE
type nonrec junction_path = string
type nonrec security_style =
  1. | MIXED
  2. | NTFS
  3. | UNIX
type nonrec volume_capacity = int
type nonrec storage_virtual_machine_id = string
type nonrec cooling_period = int
type nonrec tiering_policy_name =
  1. | NONE
  2. | ALL
  3. | AUTO
  4. | SNAPSHOT_ONLY
type nonrec tiering_policy = {
  1. name : tiering_policy_name option;
    (*

    Specifies the tiering policy used to transition data. Default value is SNAPSHOT_ONLY.

    • SNAPSHOT_ONLY - moves cold snapshots to the capacity pool storage tier.
    • AUTO - moves cold user data and snapshots to the capacity pool storage tier based on your access patterns.
    • ALL - moves all user data blocks in both the active file system and Snapshot copies to the storage pool tier.
    • NONE - keeps a volume's data in the primary storage tier, preventing it from being moved to the capacity pool tier.
    *)
  2. cooling_period : cooling_period option;
    (*

    Specifies the number of days that user data in a volume must remain inactive before it is considered "cold" and moved to the capacity pool. Used with the AUTO and SNAPSHOT_ONLY tiering policies. Enter a whole number between 2 and 183. Default values are 31 days for AUTO and 2 days for SNAPSHOT_ONLY.

    *)
}

Describes the data tiering policy for an ONTAP volume. When enabled, Amazon FSx for ONTAP's intelligent tiering automatically transitions a volume's data between the file system's primary storage and capacity pool storage based on your access patterns.

Valid tiering policies are the following:

  • SNAPSHOT_ONLY - (Default value) moves cold snapshots to the capacity pool storage tier.
  • AUTO - moves cold user data and snapshots to the capacity pool storage tier based on your access patterns.
  • ALL - moves all user data blocks in both the active file system and Snapshot copies to the storage pool tier.
  • NONE - keeps a volume's data in the primary storage tier, preventing it from being moved to the capacity pool tier.
type nonrec uui_d = string
type nonrec ontap_volume_type =
  1. | LS
  2. | DP
  3. | RW
type nonrec snapshot_policy = string
type nonrec autocommit_period_type =
  1. | NONE
  2. | YEARS
  3. | MONTHS
  4. | DAYS
  5. | HOURS
  6. | MINUTES
type nonrec autocommit_period_value = int
type nonrec autocommit_period = {
  1. value : autocommit_period_value option;
    (*

    Defines the amount of time for the autocommit period of a file in an FSx for ONTAP SnapLock volume. The following ranges are valid:

    • Minutes: 5 - 65,535
    • Hours: 1 - 65,535
    • Days: 1 - 3,650
    • Months: 1 - 120
    • Years: 1 - 10
    *)
  2. type_ : autocommit_period_type;
    (*

    Defines the type of time for the autocommit period of a file in an FSx for ONTAP SnapLock volume. Setting this value to NONE disables autocommit. The default value is NONE.

    *)
}

Sets the autocommit period of files in an FSx for ONTAP SnapLock volume, which determines how long the files must remain unmodified before they're automatically transitioned to the write once, read many (WORM) state.

For more information, see Autocommit.

type nonrec privileged_delete =
  1. | PERMANENTLY_DISABLED
  2. | ENABLED
  3. | DISABLED
type nonrec retention_period_type =
  1. | UNSPECIFIED
  2. | INFINITE
  3. | YEARS
  4. | MONTHS
  5. | DAYS
  6. | HOURS
  7. | MINUTES
  8. | SECONDS
type nonrec retention_period_value = int
type nonrec retention_period = {
  1. value : retention_period_value option;
    (*

    Defines the amount of time for the retention period of an FSx for ONTAP SnapLock volume. You can't set a value for INFINITE or UNSPECIFIED. For all other options, the following ranges are valid:

    • Seconds: 0 - 65,535
    • Minutes: 0 - 65,535
    • Hours: 0 - 24
    • Days: 0 - 365
    • Months: 0 - 12
    • Years: 0 - 100
    *)
  2. type_ : retention_period_type;
    (*

    Defines the type of time for the retention period of an FSx for ONTAP SnapLock volume. Set it to one of the valid types. If you set it to INFINITE, the files are retained forever. If you set it to UNSPECIFIED, the files are retained until you set an explicit retention period.

    *)
}

Specifies the retention period of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. Files can't be deleted or modified during the retention period.

For more information, see Working with the retention period in SnapLock.

type nonrec snaplock_retention_period = {
  1. maximum_retention : retention_period;
    (*

    The longest retention period that can be assigned to a WORM file on an FSx for ONTAP SnapLock volume.

    *)
  2. minimum_retention : retention_period;
    (*

    The shortest retention period that can be assigned to a WORM file on an FSx for ONTAP SnapLock volume.

    *)
  3. default_retention : retention_period;
    (*

    The retention period assigned to a write once, read many (WORM) file by default if an explicit retention period is not set for an FSx for ONTAP SnapLock volume. The default retention period must be greater than or equal to the minimum retention period and less than or equal to the maximum retention period.

    *)
}

The configuration to set the retention period of an FSx for ONTAP SnapLock volume. The retention period includes default, maximum, and minimum settings. For more information, see Working with the retention period in SnapLock.

type nonrec snaplock_type =
  1. | ENTERPRISE
  2. | COMPLIANCE
type nonrec snaplock_configuration = {
  1. volume_append_mode_enabled : flag option;
    (*

    Enables or disables volume-append mode on an FSx for ONTAP SnapLock volume. Volume-append mode allows you to create WORM-appendable files and write data to them incrementally. The default value is false.

    For more information, see Volume-append mode.

    *)
  2. snaplock_type : snaplock_type option;
    (*

    Specifies the retention mode of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. You can choose one of the following retention modes:

    • COMPLIANCE: Files transitioned to write once, read many (WORM) on a Compliance volume can't be deleted until their retention periods expire. This retention mode is used to address government or industry-specific mandates or to protect against ransomware attacks. For more information, see SnapLock Compliance.
    • ENTERPRISE: Files transitioned to WORM on an Enterprise volume can be deleted by authorized users before their retention periods expire using privileged delete. This retention mode is used to advance an organization's data integrity and internal compliance or to test retention settings before using SnapLock Compliance. For more information, see SnapLock Enterprise.
    *)
  3. retention_period : snaplock_retention_period option;
    (*

    Specifies the retention period of an FSx for ONTAP SnapLock volume.

    *)
  4. privileged_delete : privileged_delete option;
    (*

    Enables, disables, or permanently disables privileged delete on an FSx for ONTAP SnapLock Enterprise volume. Enabling privileged delete allows SnapLock administrators to delete write once, read many (WORM) files even if they have active retention periods. PERMANENTLY_DISABLED is a terminal state. If privileged delete is permanently disabled on a SnapLock volume, you can't re-enable it. The default value is DISABLED.

    For more information, see Privileged delete.

    *)
  5. autocommit_period : autocommit_period option;
    (*

    The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.

    *)
  6. audit_log_volume : flag option;
    (*

    Enables or disables the audit log volume for an FSx for ONTAP SnapLock volume. The default value is false. If you set AuditLogVolume to true, the SnapLock volume is created as an audit log volume. The minimum retention period for an audit log volume is six months.

    For more information, see SnapLock audit log volumes.

    *)
}

Specifies the SnapLock configuration for an FSx for ONTAP SnapLock volume.

type nonrec volume_style =
  1. | FLEXGROUP
  2. | FLEXVOL
type nonrec aggregate = string
type nonrec aggregates = aggregate list
type nonrec total_constituents = int
type nonrec aggregate_configuration = {
  1. total_constituents : total_constituents option;
    (*

    The total number of constituents this FlexGroup volume has. Not applicable for FlexVols.

    *)
  2. aggregates : aggregates option;
    (*

    The list of aggregates that this volume resides on. Aggregates are storage pools which make up your primary storage tier. Each high-availability (HA) pair has one aggregate. The names of the aggregates map to the names of the aggregates in the ONTAP CLI and REST API. For FlexVols, there will always be a single entry.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The strings in the value of Aggregates are not are not formatted as aggrX, where X is a number between 1 and 12.
    • The value of Aggregates contains aggregates that are not present.
    • One or more of the aggregates supplied are too close to the volume limit to support adding more volumes.
    *)
}

Used to specify configuration options for a volume’s storage aggregate or aggregates.

type nonrec volume_capacity_bytes = Smaws_Lib.CoreTypes.Int64.t
type nonrec ontap_volume_configuration = {
  1. size_in_bytes : volume_capacity_bytes option;
    (*

    The configured size of the volume, in bytes.

    *)
  2. aggregate_configuration : aggregate_configuration option;
    (*

    This structure specifies configuration options for a volume’s storage aggregate or aggregates.

    *)
  3. volume_style : volume_style option;
    (*

    Use to specify the style of an ONTAP volume. For more information about FlexVols and FlexGroups, see Volume types in Amazon FSx for NetApp ONTAP User Guide.

    *)
  4. snaplock_configuration : snaplock_configuration option;
    (*

    The SnapLock configuration object for an FSx for ONTAP SnapLock volume.

    *)
  5. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags for the volume should be copied to backups. This value defaults to false. If it's set to true, all tags for the volume are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the volume, regardless of this value.

    *)
  6. snapshot_policy : snapshot_policy option;
    (*

    Specifies the snapshot policy for the volume. There are three built-in snapshot policies:

    • default: This is the default policy. A maximum of six hourly snapshots taken five minutes past the hour. A maximum of two daily snapshots taken Monday through Saturday at 10 minutes after midnight. A maximum of two weekly snapshots taken every Sunday at 15 minutes after midnight.
    • default-1weekly: This policy is the same as the default policy except that it only retains one snapshot from the weekly schedule.
    • none: This policy does not take any snapshots. This policy can be assigned to volumes to prevent automatic snapshots from being taken.

    You can also provide the name of a custom policy that you created with the ONTAP CLI or REST API.

    For more information, see Snapshot policies in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  7. ontap_volume_type : ontap_volume_type option;
    (*

    Specifies the type of volume. Valid values are the following:

    • RW specifies a read/write volume. RW is the default.
    • DP specifies a data-protection volume. You can protect data by replicating it to data-protection mirror copies. If a disaster occurs, you can use these data-protection mirror copies to recover data.
    • LS specifies a load-sharing mirror volume. A load-sharing mirror reduces the network traffic to a FlexVol volume by providing additional read-only access to clients.
    *)
  8. uui_d : uui_d option;
    (*

    The volume's universally unique identifier (UUID).

    *)
  9. tiering_policy : tiering_policy option;
    (*

    The volume's TieringPolicy setting.

    *)
  10. storage_virtual_machine_root : flag option;
    (*

    A Boolean flag indicating whether this volume is the root volume for its storage virtual machine (SVM). Only one volume on an SVM can be the root volume. This value defaults to false. If this value is true, then this is the SVM root volume.

    This flag is useful when you're deleting an SVM, because you must first delete all non-root volumes. This flag, when set to false, helps you identify which volumes to delete before you can delete the SVM.

    *)
  11. storage_virtual_machine_id : storage_virtual_machine_id option;
    (*

    The ID of the volume's storage virtual machine.

    *)
  12. storage_efficiency_enabled : flag option;
    (*

    The volume's storage efficiency setting.

    *)
  13. size_in_megabytes : volume_capacity option;
    (*

    The configured size of the volume, in megabytes (MBs).

    *)
  14. security_style : security_style option;
    (*

    The security style for the volume, which can be UNIX, NTFS, or MIXED.

    *)
  15. junction_path : junction_path option;
    (*

    Specifies the directory that network-attached storage (NAS) clients use to mount the volume, along with the storage virtual machine (SVM) Domain Name System (DNS) name or IP address. You can create a JunctionPath directly below a parent volume junction or on a directory within a volume. A JunctionPath for a volume named vol3 might be /vol1/vol2/vol3, or /vol1/dir2/vol3, or even /dir1/dir2/vol3.

    *)
  16. flex_cache_endpoint_type : flex_cache_endpoint_type option;
    (*

    Specifies the FlexCache endpoint type of the volume. Valid values are the following:

    • NONE specifies that the volume doesn't have a FlexCache configuration. NONE is the default.
    • ORIGIN specifies that the volume is the origin volume for a FlexCache volume.
    • CACHE specifies that the volume is a FlexCache volume.
    *)
}

The configuration of an Amazon FSx for NetApp ONTAP volume.

type nonrec resource_ar_n = string
type nonrec tag_key = string
type nonrec tag_value = string
type nonrec tag = {
  1. value : tag_value;
    (*

    A value that specifies the TagValue, the value assigned to the corresponding tag key. Tag values can be null and don't have to be unique in a tag set. For example, you can have a key-value pair in a tag set of finances : April and also of payroll : April.

    *)
  2. key : tag_key;
    (*

    A value that specifies the TagKey, the name of the tag. Tag keys must be unique for the resource to which they are attached.

    *)
}

Specifies a key-value pair for a resource tag.

type nonrec tags = tag list
type nonrec volume_id = string
type nonrec volume_type =
  1. | OPENZFS
  2. | ONTAP
type nonrec error_message = string
type nonrec lifecycle_transition_reason = {
  1. message : error_message option;
}

Describes why a resource lifecycle state changed.

type nonrec administrative_action_type =
  1. | DOWNLOAD_DATA_FROM_BACKUP
  2. | VOLUME_INITIALIZE_WITH_SNAPSHOT
  3. | VOLUME_UPDATE_WITH_SNAPSHOT
  4. | MISCONFIGURED_STATE_RECOVERY
  5. | STORAGE_TYPE_OPTIMIZATION
  6. | IOPS_OPTIMIZATION
  7. | THROUGHPUT_OPTIMIZATION
  8. | VOLUME_RESTORE
  9. | RELEASE_NFS_V3_LOCKS
  10. | SNAPSHOT_UPDATE
  11. | VOLUME_UPDATE
  12. | FILE_SYSTEM_ALIAS_DISASSOCIATION
  13. | FILE_SYSTEM_ALIAS_ASSOCIATION
  14. | STORAGE_OPTIMIZATION
  15. | FILE_SYSTEM_UPDATE

Describes the type of administrative action, as follows:

  • FILE_SYSTEM_UPDATE - A file system update administrative action initiated from the Amazon FSx console, API (UpdateFileSystem), or CLI (update-file-system).
  • THROUGHPUT_OPTIMIZATION - After the FILE_SYSTEM_UPDATE task to increase a file system's throughput capacity has been completed successfully, a THROUGHPUT_OPTIMIZATION task starts.

    You can track the storage-optimization progress using the ProgressPercent property. When THROUGHPUT_OPTIMIZATION has been completed successfully, the parent FILE_SYSTEM_UPDATE action status changes to COMPLETED. For more information, see Managing throughput capacity in the Amazon FSx for Windows File Server User Guide.

  • STORAGE_OPTIMIZATION - After the FILE_SYSTEM_UPDATE task to increase a file system's storage capacity has completed successfully, a STORAGE_OPTIMIZATION task starts.

    • For Windows and ONTAP, storage optimization is the process of migrating the file system data to newer larger disks.
    • For Lustre, storage optimization consists of rebalancing the data across the existing and newly added file servers.

    You can track the storage-optimization progress using the ProgressPercent property. When STORAGE_OPTIMIZATION has been completed successfully, the parent FILE_SYSTEM_UPDATE action status changes to COMPLETED. For more information, see Managing storage capacity in the Amazon FSx for Windows File Server User Guide, Managing storage capacity in the Amazon FSx for Lustre User Guide, and Managing storage capacity and provisioned IOPS in the Amazon FSx for NetApp ONTAP User Guide.

  • FILE_SYSTEM_ALIAS_ASSOCIATION - A file system update to associate a new Domain Name System (DNS) alias with the file system. For more information, see AssociateFileSystemAliases.
  • FILE_SYSTEM_ALIAS_DISASSOCIATION - A file system update to disassociate a DNS alias from the file system. For more information, see DisassociateFileSystemAliases.
  • IOPS_OPTIMIZATION - After the FILE_SYSTEM_UPDATE task to increase a file system's throughput capacity has been completed successfully, a IOPS_OPTIMIZATION task starts.

    You can track the storage-optimization progress using the ProgressPercent property. When IOPS_OPTIMIZATION has been completed successfully, the parent FILE_SYSTEM_UPDATE action status changes to COMPLETED. For more information, see Managing provisioned SSD IOPS in the Amazon FSx for Windows File Server User Guide.

  • STORAGE_TYPE_OPTIMIZATION - After the FILE_SYSTEM_UPDATE task to increase a file system's throughput capacity has been completed successfully, a STORAGE_TYPE_OPTIMIZATION task starts.

    You can track the storage-optimization progress using the ProgressPercent property. When STORAGE_TYPE_OPTIMIZATION has been completed successfully, the parent FILE_SYSTEM_UPDATE action status changes to COMPLETED.

  • VOLUME_UPDATE - A volume update to an Amazon FSx for OpenZFS volume initiated from the Amazon FSx console, API (UpdateVolume), or CLI (update-volume).
  • VOLUME_RESTORE - An Amazon FSx for OpenZFS volume is returned to the state saved by the specified snapshot, initiated from an API (RestoreVolumeFromSnapshot) or CLI (restore-volume-from-snapshot).
  • SNAPSHOT_UPDATE - A snapshot update to an Amazon FSx for OpenZFS volume initiated from the Amazon FSx console, API (UpdateSnapshot), or CLI (update-snapshot).
  • RELEASE_NFS_V3_LOCKS - Tracks the release of Network File System (NFS) V3 locks on an Amazon FSx for OpenZFS file system.
  • DOWNLOAD_DATA_FROM_BACKUP - An FSx for ONTAP backup is being restored to a new volume on a second-generation file system. Once the all the file metadata is loaded onto the volume, you can mount the volume with read-only access. during this process.
  • VOLUME_INITIALIZE_WITH_SNAPSHOT - A volume is being created from a snapshot on a different FSx for OpenZFS file system. You can initiate this from the Amazon FSx console, API (CreateVolume), or CLI (create-volume) when using the using the FULL_COPY strategy.
  • VOLUME_UPDATE_WITH_SNAPSHOT - A volume is being updated from a snapshot on a different FSx for OpenZFS file system. You can initiate this from the Amazon FSx console, API (CopySnapshotAndUpdateVolume), or CLI (copy-snapshot-and-update-volume).
type nonrec progress_percent = int
type nonrec request_time = Smaws_Lib.CoreTypes.Timestamp.t
type nonrec status =
  1. | CANCELLED
  2. | PAUSED
  3. | OPTIMIZING
  4. | UPDATED_OPTIMIZING
  5. | COMPLETED
  6. | PENDING
  7. | IN_PROGRESS
  8. | FAILED
type nonrec aws_account_id = string
type nonrec file_system_type =
  1. | OPENZFS
  2. | ONTAP
  3. | LUSTRE
  4. | WINDOWS

The type of Amazon FSx file system.

type nonrec file_system_lifecycle =
  1. | MISCONFIGURED_UNAVAILABLE
  2. | UPDATING
  3. | MISCONFIGURED
  4. | DELETING
  5. | FAILED
  6. | CREATING
  7. | AVAILABLE

The lifecycle status of the file system.

type nonrec file_system_failure_details = {
  1. message : error_message option;
    (*

    A message describing any failures that occurred.

    *)
}

A structure providing details of any failures that occurred.

type nonrec storage_capacity = int
type nonrec storage_type =
  1. | INTELLIGENT_TIERING
  2. | HDD
  3. | SSD

Specifies the file system's storage type.

type nonrec subnet_ids = subnet_id list
type nonrec network_interface_id = string
type nonrec network_interface_ids = network_interface_id list
type nonrec kms_key_id = string
type nonrec data_repository_lifecycle =
  1. | FAILED
  2. | DELETING
  3. | UPDATING
  4. | MISCONFIGURED
  5. | AVAILABLE
  6. | CREATING
type nonrec archive_path = string
type nonrec megabytes = int
type nonrec auto_import_policy_type =
  1. | NEW_CHANGED_DELETED
  2. | NEW_CHANGED
  3. | NEW
  4. | NONE
type nonrec data_repository_failure_details = {
  1. message : error_message option;
}

Provides detailed information about the data repository if its Lifecycle is set to MISCONFIGURED or FAILED.

type nonrec data_repository_configuration = {
  1. failure_details : data_repository_failure_details option;
  2. auto_import_policy : auto_import_policy_type option;
    (*

    Describes the file system's linked S3 data repository's AutoImportPolicy. The AutoImportPolicy configures how Amazon FSx keeps your file and directory listings up to date as you add or modify objects in your linked S3 bucket. AutoImportPolicy can have the following values:

    • NONE - (Default) AutoImport is off. Amazon FSx only updates file and directory listings from the linked S3 bucket when the file system is created. FSx does not update file and directory listings for any new or changed objects after choosing this option.
    • NEW - AutoImport is on. Amazon FSx automatically imports directory listings of any new objects added to the linked S3 bucket that do not currently exist in the FSx file system.
    • NEW_CHANGED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket and any existing objects that are changed in the S3 bucket after you choose this option.
    • NEW_CHANGED_DELETED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket, any existing objects that are changed in the S3 bucket, and any objects that were deleted in the S3 bucket.
    *)
  3. imported_file_chunk_size : megabytes option;
    (*

    For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

    The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

    *)
  4. export_path : archive_path option;
    (*

    The export path to the Amazon S3 bucket (and prefix) that you are using to store new and changed Lustre file system files in S3.

    *)
  5. import_path : archive_path option;
    (*

    The import path to the Amazon S3 bucket (and optional prefix) that you're using as the data repository for your FSx for Lustre file system, for example s3://import-bucket/optional-prefix. If a prefix is specified after the Amazon S3 bucket name, only object keys with that prefix are loaded into the file system.

    *)
  6. lifecycle : data_repository_lifecycle option;
    (*

    Describes the state of the file system's S3 durable data repository, if it is configured with an S3 repository. The lifecycle can have the following values:

    • CREATING - The data repository configuration between the FSx file system and the linked S3 data repository is being created. The data repository is unavailable.
    • AVAILABLE - The data repository is available for use.
    • MISCONFIGURED - Amazon FSx cannot automatically import updates from the S3 bucket until the data repository configuration is corrected. For more information, see Troubleshooting a Misconfigured linked S3 bucket.
    • UPDATING - The data repository is undergoing a customer initiated update and availability may be impacted.
    • FAILED - The data repository is in a terminal state that cannot be recovered.
    *)
}

The data repository configuration object for Lustre file systems returned in the response of the CreateFileSystem operation.

This data type is not supported on file systems with a data repository association. For file systems with a data repository association, see .

type nonrec lustre_deployment_type =
  1. | PERSISTENT_2
  2. | PERSISTENT_1
  3. | SCRATCH_2
  4. | SCRATCH_1
type nonrec per_unit_storage_throughput = int
type nonrec lustre_file_system_mount_name = string
type nonrec drive_cache_type =
  1. | READ
  2. | NONE
type nonrec data_compression_type =
  1. | LZ4
  2. | NONE
type nonrec lustre_access_audit_log_level =
  1. | WARN_ERROR
  2. | ERROR_ONLY
  3. | WARN_ONLY
  4. | DISABLED
type nonrec lustre_log_configuration = {
  1. destination : general_ar_n option;
    (*

    The Amazon Resource Name (ARN) that specifies the destination of the logs. The destination can be any Amazon CloudWatch Logs log group ARN. The destination ARN must be in the same Amazon Web Services partition, Amazon Web Services Region, and Amazon Web Services account as your Amazon FSx file system.

    *)
  2. level : lustre_access_audit_log_level;
    (*

    The data repository events that are logged by Amazon FSx.

    • WARN_ONLY - only warning events are logged.
    • ERROR_ONLY - only error events are logged.
    • WARN_ERROR - both warning events and error events are logged.
    • DISABLED - logging of data repository events is turned off.

    Note that Amazon File Cache uses a default setting of WARN_ERROR, which can't be changed.

    *)
}

The configuration for Lustre logging used to write the enabled logging events for your Amazon FSx for Lustre file system or Amazon File Cache resource to Amazon CloudWatch Logs.

type nonrec lustre_root_squash = string
type nonrec lustre_no_squash_nid = string
type nonrec lustre_no_squash_nids = lustre_no_squash_nid list
type nonrec lustre_root_squash_configuration = {
  1. no_squash_nids : lustre_no_squash_nids option;
    (*

    When root squash is enabled, you can optionally specify an array of NIDs of clients for which root squash does not apply. A client NID is a Lustre Network Identifier used to uniquely identify a client. You can specify the NID as either a single address or a range of addresses:

    • A single address is described in standard Lustre NID format by specifying the client’s IP address followed by the Lustre network ID (for example, 10.0.1.6@tcp).
    • An address range is described using a dash to separate the range (for example, 10.0.[2-10].[1-255]@tcp).
    *)
  2. root_squash : lustre_root_squash option;
    (*

    You enable root squash by setting a user ID (UID) and group ID (GID) for the file system in the format UID:GID (for example, 365534:65534). The UID and GID values can range from 0 to 4294967294:

    • A non-zero value for UID and GID enables root squash. The UID and GID values can be different, but each must be a non-zero value.
    • A value of 0 (zero) for UID and GID indicates root, and therefore disables root squash.

    When root squash is enabled, the user ID and group ID of a root user accessing the file system are re-mapped to the UID and GID you provide.

    *)
}

The configuration for Lustre root squash used to restrict root-level access from clients that try to access your FSx for Lustre file system as root. Use the RootSquash parameter to enable root squash. To learn more about Lustre root squash, see Lustre root squash.

You can also use the NoSquashNids parameter to provide an array of clients who are not affected by the root squash setting. These clients will access the file system as root, with unrestricted privileges.

type nonrec metadata_iops = int
type nonrec metadata_configuration_mode =
  1. | USER_PROVISIONED
  2. | AUTOMATIC
type nonrec file_system_lustre_metadata_configuration = {
  1. mode : metadata_configuration_mode;
    (*

    The metadata configuration mode for provisioning Metadata IOPS for the file system.

    • In AUTOMATIC mode (supported only on SSD file systems), FSx for Lustre automatically provisions and scales the number of Metadata IOPS on your file system based on your file system storage capacity.
    • In USER_PROVISIONED mode, you can choose to specify the number of Metadata IOPS to provision for your file system.
    *)
  2. iops : metadata_iops option;
    (*

    The number of Metadata IOPS provisioned for the file system.

    • For SSD file systems, valid values are 1500, 3000, 6000, 12000, and multiples of 12000 up to a maximum of 192000.
    • For Intelligent-Tiering file systems, valid values are 6000 and 12000.
    *)
}

The Lustre metadata performance configuration of an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. The configuration enables the file system to support increasing metadata performance.

type nonrec throughput_capacity_mbps = int
type nonrec lustre_read_cache_sizing_mode =
  1. | PROPORTIONAL_TO_THROUGHPUT_CAPACITY
  2. | USER_PROVISIONED
  3. | NO_CACHE
type nonrec lustre_read_cache_configuration = {
  1. size_gi_b : storage_capacity option;
    (*

    Required if SizingMode is set to USER_PROVISIONED. Specifies the size of the file system's SSD read cache, in gibibytes (GiB).

    The SSD read cache size is distributed across provisioned file servers in your file system. Intelligent-Tiering file systems support a minimum of 32 GiB and maximum of 131072 GiB for SSD read cache size for every 4,000 MB/s of throughput capacity provisioned.

    *)
  2. sizing_mode : lustre_read_cache_sizing_mode option;
    (*

    Specifies how the provisioned SSD read cache is sized, as follows:

    • Set to NO_CACHE if you do not want to use an SSD read cache with your Intelligent-Tiering file system.
    • Set to USER_PROVISIONED to specify the exact size of your SSD read cache.
    • Set to PROPORTIONAL_TO_THROUGHPUT_CAPACITY to have your SSD read cache automatically sized based on your throughput capacity.
    *)
}

The configuration for the optional provisioned SSD read cache on Amazon FSx for Lustre file systems that use the Intelligent-Tiering storage class.

type nonrec lustre_file_system_configuration = {
  1. data_read_cache_configuration : lustre_read_cache_configuration option;
    (*

    Required when StorageType is set to INTELLIGENT_TIERING. Specifies the optional provisioned SSD read cache.

    *)
  2. throughput_capacity : throughput_capacity_mbps option;
    (*

    The throughput of an Amazon FSx for Lustre file system using the Intelligent-Tiering storage class, measured in megabytes per second (MBps).

    *)
  3. efa_enabled : flag option;
    (*

    Specifies whether Elastic Fabric Adapter (EFA) and GPUDirect Storage (GDS) support is enabled for the Amazon FSx for Lustre file system.

    *)
  4. metadata_configuration : file_system_lustre_metadata_configuration option;
    (*

    The Lustre metadata performance configuration for an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type.

    *)
  5. root_squash_configuration : lustre_root_squash_configuration option;
    (*

    The Lustre root squash configuration for an Amazon FSx for Lustre file system. When enabled, root squash restricts root-level access from clients that try to access your file system as a root user.

    *)
  6. log_configuration : lustre_log_configuration option;
    (*

    The Lustre logging configuration. Lustre logging writes the enabled log events for your file system to Amazon CloudWatch Logs.

    *)
  7. data_compression_type : data_compression_type option;
    (*

    The data compression configuration for the file system. DataCompressionType can have the following values:

    • NONE - Data compression is turned off for the file system.
    • LZ4 - Data compression is turned on with the LZ4 algorithm.

    For more information, see Lustre data compression.

    *)
  8. drive_cache_type : drive_cache_type option;
    (*

    The type of drive cache used by PERSISTENT_1 file systems that are provisioned with HDD storage devices. This parameter is required when StorageType is HDD. When set to READ the file system has an SSD storage cache that is sized to 20% of the file system's storage capacity. This improves the performance for frequently accessed files by caching up to 20% of the total storage capacity.

    This parameter is required when StorageType is set to HDD.

    *)
  9. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags on the file system are copied to backups. If it's set to true, all tags on the file system are copied to all automatic backups and any user-initiated backups where the user doesn't specify any tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value. (Default = false)

    *)
  10. automatic_backup_retention_days : automatic_backup_retention_days option;
  11. daily_automatic_backup_start_time : daily_time option;
  12. mount_name : lustre_file_system_mount_name option;
    (*

    You use the MountName value when mounting the file system.

    For the SCRATCH_1 deployment type, this value is always "fsx". For SCRATCH_2, PERSISTENT_1, and PERSISTENT_2 deployment types, this value is a string that is unique within an Amazon Web Services Region.

    *)
  13. per_unit_storage_throughput : per_unit_storage_throughput option;
    (*

    Per unit storage throughput represents the megabytes per second of read or write throughput per 1 tebibyte of storage provisioned. File system throughput capacity is equal to Storage capacity (TiB) * PerUnitStorageThroughput (MB/s/TiB). This option is only valid for PERSISTENT_1 and PERSISTENT_2 deployment types.

    Valid values:

    • For PERSISTENT_1 SSD storage: 50, 100, 200.
    • For PERSISTENT_1 HDD storage: 12, 40.
    • For PERSISTENT_2 SSD storage: 125, 250, 500, 1000.
    *)
  14. deployment_type : lustre_deployment_type option;
    (*

    The deployment type of the FSx for Lustre file system. Scratch deployment type is designed for temporary storage and shorter-term processing of data.

    SCRATCH_1 and SCRATCH_2 deployment types are best suited for when you need temporary storage and shorter-term processing of data. The SCRATCH_2 deployment type provides in-transit encryption of data and higher burst throughput capacity than SCRATCH_1.

    The PERSISTENT_1 and PERSISTENT_2 deployment type is used for longer-term storage and workloads and encryption of data in transit. PERSISTENT_2 offers higher PerUnitStorageThroughput (up to 1000 MB/s/TiB) along with a lower minimum storage capacity requirement (600 GiB). To learn more about FSx for Lustre deployment types, see Deployment and storage class options for FSx for Lustre file systems.

    The default is SCRATCH_1.

    *)
  15. data_repository_configuration : data_repository_configuration option;
  16. weekly_maintenance_start_time : weekly_time option;
    (*

    The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. Here, d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.

    *)
}

The configuration for the Amazon FSx for Lustre file system.

type nonrec ontap_deployment_type =
  1. | MULTI_AZ_2
  2. | SINGLE_AZ_2
  3. | SINGLE_AZ_1
  4. | MULTI_AZ_1
type nonrec ip_address_range = string
type nonrec ontap_endpoint_ip_addresses = ip_address list
type nonrec file_system_endpoint = {
  1. ipv6_addresses : ontap_endpoint_ip_addresses option;
    (*

    The IPv6 addresses of the file system endpoint.

    *)
  2. ip_addresses : ontap_endpoint_ip_addresses option;
    (*

    The IPv4 addresses of the file system endpoint.

    *)
  3. dns_name : dns_name option;
}

An Amazon FSx for NetApp ONTAP file system has two endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror. They are the Management and Intercluster endpoints.

type nonrec file_system_endpoints = {
  1. management : file_system_endpoint option;
    (*

    An endpoint for managing your file system using the NetApp ONTAP CLI and NetApp ONTAP API.

    *)
  2. intercluster : file_system_endpoint option;
    (*

    An endpoint for managing your file system by setting up NetApp SnapMirror with other ONTAP systems.

    *)
}

An Amazon FSx for NetApp ONTAP file system has the following endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror.

type nonrec route_table_id = string
type nonrec route_table_ids = route_table_id list
type nonrec admin_password = string
type nonrec ha_pairs = int
type nonrec throughput_capacity_per_ha_pair = int
type nonrec ipv6_address_range = string
type nonrec ontap_file_system_configuration = {
  1. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  2. throughput_capacity_per_ha_pair : throughput_capacity_per_ha_pair option;
    (*

    Use to choose the throughput capacity per HA pair. When the value of HAPairs is equal to 1, the value of ThroughputCapacityPerHAPair is the total throughput for the file system.

    This field and ThroughputCapacity cannot be defined in the same API call, but one is required.

    This field and ThroughputCapacity are the same for file systems with one HA pair.

    • For SINGLE_AZ_1 and MULTI_AZ_1 file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps.
    • For SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps.
    • For MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value.
    • The value of deployment type is SINGLE_AZ_2 and ThroughputCapacity / ThroughputCapacityPerHAPair is not a valid HA pair (a value between 1 and 12).
    • The value of ThroughputCapacityPerHAPair is not a valid value.
    *)
  3. ha_pairs : ha_pairs option;
    (*

    Specifies how many high-availability (HA) file server pairs the file system will have. The default value is 1. The value of this property affects the values of StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of HAPairs is less than 1 or greater than 12.
    • The value of HAPairs is greater than 1 and the value of DeploymentType is SINGLE_AZ_1, MULTI_AZ_1, or MULTI_AZ_2.
    *)
  4. fsx_admin_password : admin_password option;
    (*

    You can use the fsxadmin user account to access the NetApp ONTAP CLI and REST API. The password value is always redacted in the response.

    *)
  5. weekly_maintenance_start_time : weekly_time option;
  6. throughput_capacity : megabytes_per_second option;
  7. route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) The VPC route tables in which your file system's endpoints are created.

    *)
  8. preferred_subnet_id : subnet_id option;
  9. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS configuration for the ONTAP file system, specifying the number of provisioned IOPS and the provision mode.

    *)
  10. endpoints : file_system_endpoints option;
    (*

    The Management and Intercluster endpoints that are used to access data or to manage the file system using the NetApp ONTAP CLI, REST API, or NetApp SnapMirror.

    *)
  11. endpoint_ip_address_range : ip_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API, Amazon FSx selects an unused IP address range for you from the 198.19.* range. By default in the Amazon FSx console, Amazon FSx chooses the last 64 IP addresses from the VPC’s primary CIDR range to use as the endpoint IP address range for the file system. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables.

    *)
  12. deployment_type : ontap_deployment_type option;
    (*

    Specifies the FSx for ONTAP file system deployment type in use in the file system.

    • MULTI_AZ_1 - A high availability file system configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability. This is a first-generation FSx for ONTAP file system.
    • MULTI_AZ_2 - A high availability file system configured for Multi-AZ redundancy to tolerate temporary AZ unavailability. This is a second-generation FSx for ONTAP file system.
    • SINGLE_AZ_1 - A file system configured for Single-AZ redundancy. This is a first-generation FSx for ONTAP file system.
    • SINGLE_AZ_2 - A file system configured with multiple high-availability (HA) pairs for Single-AZ redundancy. This is a second-generation FSx for ONTAP file system.

    For information about the use cases for Multi-AZ and Single-AZ deployments, refer to Choosing Multi-AZ or Single-AZ file system deployment.

    *)
  13. daily_automatic_backup_start_time : daily_time option;
  14. automatic_backup_retention_days : automatic_backup_retention_days option;
}

Configuration for the FSx for NetApp ONTAP file system.

type nonrec file_system_type_version = string
type nonrec open_zfs_deployment_type =
  1. | MULTI_AZ_1
  2. | SINGLE_AZ_HA_2
  3. | SINGLE_AZ_HA_1
  4. | SINGLE_AZ_2
  5. | SINGLE_AZ_1
type nonrec open_zfs_read_cache_sizing_mode =
  1. | PROPORTIONAL_TO_THROUGHPUT_CAPACITY
  2. | USER_PROVISIONED
  3. | NO_CACHE
type nonrec open_zfs_read_cache_configuration = {
  1. size_gi_b : storage_capacity option;
    (*

    Required if SizingMode is set to USER_PROVISIONED. Specifies the size of the file system's SSD read cache, in gibibytes (GiB).

    *)
  2. sizing_mode : open_zfs_read_cache_sizing_mode option;
    (*

    Specifies how the provisioned SSD read cache is sized, as follows:

    • Set to NO_CACHE if you do not want to use an SSD read cache with your Intelligent-Tiering file system.
    • Set to USER_PROVISIONED to specify the exact size of your SSD read cache.
    • Set to PROPORTIONAL_TO_THROUGHPUT_CAPACITY to have your SSD read cache automatically sized based on your throughput capacity.
    *)
}

The configuration for the optional provisioned SSD read cache on Amazon FSx for OpenZFS file systems that use the Intelligent-Tiering storage class.

type nonrec open_zfs_file_system_configuration = {
  1. read_cache_configuration : open_zfs_read_cache_configuration option;
    (*

    Required when StorageType is set to INTELLIGENT_TIERING. Specifies the optional provisioned SSD read cache.

    *)
  2. endpoint_ipv6_address : ip_address option;
    (*

    The IPv6 address of the endpoint that is used to access data or to manage the file system.

    *)
  3. endpoint_ip_address : ip_address option;
    (*

    The IPv4 address of the endpoint that is used to access data or to manage the file system.

    *)
  4. route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) The VPC route tables in which your file system's endpoints are created.

    *)
  5. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  6. endpoint_ip_address_range : ip_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /28 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables.

    *)
  7. preferred_subnet_id : subnet_id option;
    (*

    Required when DeploymentType is set to MULTI_AZ_1. This specifies the subnet in which you want the preferred file server to be located.

    *)
  8. root_volume_id : volume_id option;
    (*

    The ID of the root volume of the OpenZFS file system.

    *)
  9. disk_iops_configuration : disk_iops_configuration option;
  10. weekly_maintenance_start_time : weekly_time option;
  11. throughput_capacity : megabytes_per_second option;
    (*

    The throughput of an Amazon FSx file system, measured in megabytes per second (MBps).

    *)
  12. deployment_type : open_zfs_deployment_type option;
    (*

    Specifies the file-system deployment type. Amazon FSx for OpenZFS supports
 MULTI_AZ_1, SINGLE_AZ_HA_2, SINGLE_AZ_HA_1, SINGLE_AZ_2, and SINGLE_AZ_1.

    *)
  13. daily_automatic_backup_start_time : daily_time option;
  14. copy_tags_to_volumes : flag option;
    (*

    A Boolean value indicating whether tags for the volume should be copied to snapshots. This value defaults to false. If it's set to true, all tags for the volume are copied to snapshots where the user doesn't specify tags. If this value is true and you specify one or more tags, only the specified tags are copied to snapshots. If you specify one or more tags when creating the snapshot, no tags are copied from the volume, regardless of this value.

    *)
  15. copy_tags_to_backups : flag option;
    (*

    A Boolean value indicating whether tags on the file system should be copied to backups. If it's set to true, all tags on the file system are copied to all automatic backups and any user-initiated backups where the user doesn't specify any tags. If this value is true and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    *)
  16. automatic_backup_retention_days : automatic_backup_retention_days option;
}

The configuration for the Amazon FSx for OpenZFS file system.

type nonrec network_type =
  1. | DUAL
  2. | IPV4
type nonrec administrative_action_failure_details = {
  1. message : error_message option;
    (*

    Error message providing details about the failed administrative action.

    *)
}

Provides information about a failed administrative action.

type nonrec snapshot_id = string
type nonrec snapshot_name = string
type nonrec snapshot_lifecycle =
  1. | AVAILABLE
  2. | DELETING
  3. | CREATING
  4. | PENDING
type nonrec total_transfer_bytes = Smaws_Lib.CoreTypes.Int64.t
type nonrec remaining_transfer_bytes = Smaws_Lib.CoreTypes.Int64.t
type nonrec volume_path = string
type nonrec integer_no_max = int
type nonrec integer_record_size_ki_b = int
type nonrec open_zfs_data_compression_type =
  1. | LZ4
  2. | ZSTD
  3. | NONE
type nonrec open_zfs_copy_strategy =
  1. | INCREMENTAL_COPY
  2. | FULL_COPY
  3. | CLONE
type nonrec open_zfs_origin_snapshot_configuration = {
  1. copy_strategy : open_zfs_copy_strategy option;
    (*

    The strategy used when copying data from the snapshot to the new volume.

    • CLONE - The new volume references the data in the origin snapshot. Cloning a snapshot is faster than copying the data from a snapshot to a new volume and doesn't consume disk throughput. However, the origin snapshot can't be deleted if there is a volume using its copied data.
    • FULL_COPY - Copies all data from the snapshot to the new volume.

    The INCREMENTAL_COPY option is only for updating an existing volume by using a snapshot from another FSx for OpenZFS file system. For more information, see CopySnapshotAndUpdateVolume.

    *)
  2. snapshot_ar_n : resource_ar_n option;
}

The snapshot configuration used when creating an Amazon FSx for OpenZFS volume from a snapshot.

type nonrec read_only = bool
type nonrec open_zfs_clients = string
type nonrec open_zfs_nfs_export_option = string
type nonrec open_zfs_nfs_export_options = open_zfs_nfs_export_option list
type nonrec open_zfs_client_configuration = {
  1. options : open_zfs_nfs_export_options;
    (*

    The options to use when mounting the file system. For a list of options that you can use with Network File System (NFS), see the exports(5) - Linux man page. When choosing your options, consider the following:

    • crossmnt is used by default. If you don't specify crossmnt when changing the client configuration, you won't be able to see or access snapshots in your file system's snapshot directory.
    • sync is used by default. If you instead specify async, the system acknowledges writes before writing to disk. If the system crashes before the writes are finished, you lose the unwritten data.
    *)
  2. clients : open_zfs_clients;
    (*

    A value that specifies who can mount the file system. You can provide a wildcard character (*), an IP address (0.0.0.0), or a CIDR address (192.0.2.0/24). By default, Amazon FSx uses the wildcard character when specifying the client.

    *)
}

Specifies who can mount an OpenZFS file system and the options available while mounting the file system.

type nonrec open_zfs_client_configurations = open_zfs_client_configuration list
type nonrec open_zfs_nfs_export = {
  1. client_configurations : open_zfs_client_configurations;
    (*

    A list of configuration objects that contain the client and options for mounting the OpenZFS file system.

    *)
}

The Network File System (NFS) configurations for mounting an Amazon FSx for OpenZFS file system.

type nonrec open_zfs_nfs_exports = open_zfs_nfs_export list
type nonrec open_zfs_quota_type =
  1. | GROUP
  2. | USER
type nonrec open_zfs_user_or_group_quota = {
  1. storage_capacity_quota_gi_b : integer_no_max;
    (*

    The user or group's storage quota, in gibibytes (GiB).

    *)
  2. id : integer_no_max;
    (*

    The ID of the user or group that the quota applies to.

    *)
  3. type_ : open_zfs_quota_type;
    (*

    Specifies whether the quota applies to a user or group.

    *)
}

Used to configure quotas that define how much storage a user or group can use on an FSx for OpenZFS volume. For more information, see Volume properties in the FSx for OpenZFS User Guide.

type nonrec open_zfs_user_and_group_quotas = open_zfs_user_or_group_quota list
type nonrec open_zfs_volume_configuration = {
  1. copy_strategy : open_zfs_copy_strategy option;
    (*

    Specifies the strategy used when copying data from the snapshot to the new volume.

    • CLONE - The new volume references the data in the origin snapshot. Cloning a snapshot is faster than copying data from the snapshot to a new volume and doesn't consume disk throughput. However, the origin snapshot can't be deleted if there is a volume using its copied data.
    • FULL_COPY - Copies all data from the snapshot to the new volume.

      Specify this option to create the volume from a snapshot on another FSx for OpenZFS file system.

    The INCREMENTAL_COPY option is only for updating an existing volume by using a snapshot from another FSx for OpenZFS file system. For more information, see CopySnapshotAndUpdateVolume.

    *)
  2. destination_snapshot : snapshot_id option;
    (*

    The ID of the snapshot that's being copied or was most recently copied to the destination volume.

    *)
  3. source_snapshot_ar_n : resource_ar_n option;
  4. delete_intermediate_data : flag option;
    (*

    A Boolean value indicating whether snapshot data that differs between the current state and the specified snapshot should be overwritten when a volume is restored from a snapshot.

    *)
  5. delete_cloned_volumes : flag option;
    (*

    A Boolean value indicating whether dependent clone volumes created from intermediate snapshots should be deleted when a volume is restored from snapshot.

    *)
  6. delete_intermediate_snaphots : flag option;
    (*

    A Boolean value indicating whether snapshots between the current state and the specified snapshot should be deleted when a volume is restored from snapshot.

    *)
  7. restore_to_snapshot : snapshot_id option;
    (*

    Specifies the ID of the snapshot to which the volume was restored.

    *)
  8. user_and_group_quotas : open_zfs_user_and_group_quotas option;
    (*

    An object specifying how much storage users or groups can use on the volume.

    *)
  9. nfs_exports : open_zfs_nfs_exports option;
    (*

    The configuration object for mounting a Network File System (NFS) file system.

    *)
  10. read_only : read_only option;
    (*

    A Boolean value indicating whether the volume is read-only.

    *)
  11. origin_snapshot : open_zfs_origin_snapshot_configuration option;
    (*

    The configuration object that specifies the snapshot to use as the origin of the data for the volume.

    *)
  12. copy_tags_to_snapshots : flag option;
    (*

    A Boolean value indicating whether tags for the volume should be copied to snapshots. This value defaults to false. If it's set to true, all tags for the volume are copied to snapshots where the user doesn't specify tags. If this value is true and you specify one or more tags, only the specified tags are copied to snapshots. If you specify one or more tags when creating the snapshot, no tags are copied from the volume, regardless of this value.

    *)
  13. data_compression_type : open_zfs_data_compression_type option;
    (*

    Specifies the method used to compress the data on the volume. The compression type is NONE by default.

    • NONE - Doesn't compress the data on the volume. NONE is the default.
    • ZSTD - Compresses the data in the volume using the Zstandard (ZSTD) compression algorithm. Compared to LZ4, Z-Standard provides a better compression ratio to minimize on-disk storage utilization.
    • LZ4 - Compresses the data in the volume using the LZ4 compression algorithm. Compared to Z-Standard, LZ4 is less compute-intensive and delivers higher write throughput speeds.
    *)
  14. record_size_ki_b : integer_record_size_ki_b option;
    (*

    The record size of an OpenZFS volume, in kibibytes (KiB). Valid values are 4, 8, 16, 32, 64, 128, 256, 512, or 1024 KiB. The default is 128 KiB. Most workloads should use the default record size. For guidance on when to set a custom record size, see the Amazon FSx for OpenZFS User Guide.

    *)
  15. storage_capacity_quota_gi_b : integer_no_max option;
    (*

    The maximum amount of storage in gibibytes (GiB) that the volume can use from its parent. You can specify a quota larger than the storage on the parent volume.

    *)
  16. storage_capacity_reservation_gi_b : integer_no_max option;
    (*

    The amount of storage in gibibytes (GiB) to reserve from the parent volume. You can't reserve more storage than the parent volume has reserved.

    *)
  17. volume_path : volume_path option;
    (*

    The path to the volume from the root volume. For example, fsx/parentVolume/volume1.

    *)
  18. parent_volume_id : volume_id option;
    (*

    The ID of the parent volume.

    *)
}

The configuration of an Amazon FSx for OpenZFS volume.

type administrative_action = {
  1. message : error_message option;
  2. remaining_transfer_bytes : remaining_transfer_bytes option;
    (*

    The remaining bytes to transfer for the FSx for OpenZFS snapshot that you're copying.

    *)
  3. total_transfer_bytes : total_transfer_bytes option;
    (*

    The number of bytes that have transferred for the FSx for OpenZFS snapshot that you're copying.

    *)
  4. target_snapshot_values : snapshot option;
  5. target_volume_values : volume option;
  6. failure_details : administrative_action_failure_details option;
  7. target_file_system_values : file_system option;
    (*

    The target value for the administration action, provided in the UpdateFileSystem operation. Returned for FILE_SYSTEM_UPDATE administrative actions.

    *)
  8. status : status option;
    (*

    The status of the administrative action, as follows:

    • FAILED - Amazon FSx failed to process the administrative action successfully.
    • IN_PROGRESS - Amazon FSx is processing the administrative action.
    • PENDING - Amazon FSx is waiting to process the administrative action.
    • COMPLETED - Amazon FSx has finished processing the administrative task.

      For a backup restore to a second-generation FSx for ONTAP file system, indicates that all data has been downloaded to the volume, and clients now have read-write access to volume.

    • UPDATED_OPTIMIZING - For a storage-capacity increase update, Amazon FSx has updated the file system with the new storage capacity, and is now performing the storage-optimization process.
    • PENDING - For a backup restore to a second-generation FSx for ONTAP file system, indicates that the file metadata is being downloaded onto the volume. The volume's Lifecycle state is CREATING.
    • IN_PROGRESS - For a backup restore to a second-generation FSx for ONTAP file system, indicates that all metadata has been downloaded to the new volume and client can access data with read-only access while Amazon FSx downloads the file data to the volume. Track the progress of this process with the ProgressPercent element.
    *)
  9. request_time : request_time option;
    (*

    The time that the administrative action request was received.

    *)
  10. progress_percent : progress_percent option;
    (*

    The percentage-complete status of a STORAGE_OPTIMIZATION or DOWNLOAD_DATA_FROM_BACKUP administrative action. Does not apply to any other administrative action type.

    *)
  11. administrative_action_type : administrative_action_type option;
}

Describes a specific Amazon FSx administrative action for the current Windows, Lustre, OpenZFS, or ONTAP file system or volume.

and administrative_actions = administrative_action list
and file_system = {
  1. network_type : network_type option;
    (*

    The network type of the file system.

    *)
  2. open_zfs_configuration : open_zfs_file_system_configuration option;
    (*

    The configuration for this Amazon FSx for OpenZFS file system.

    *)
  3. file_system_type_version : file_system_type_version option;
    (*

    The Lustre version of the Amazon FSx for Lustre file system, which can be 2.10, 2.12, or 2.15.

    *)
  4. ontap_configuration : ontap_file_system_configuration option;
    (*

    The configuration for this Amazon FSx for NetApp ONTAP file system.

    *)
  5. administrative_actions : administrative_actions option;
    (*

    A list of administrative actions for the file system that are in process or waiting to be processed. Administrative actions describe changes to the Amazon FSx system that you have initiated using the UpdateFileSystem operation.

    *)
  6. lustre_configuration : lustre_file_system_configuration option;
  7. windows_configuration : windows_file_system_configuration option;
    (*

    The configuration for this Amazon FSx for Windows File Server file system.

    *)
  8. tags : tags option;
    (*

    The tags to associate with the file system. For more information, see Tagging your Amazon FSx resources in the Amazon FSx for Lustre User Guide.

    *)
  9. resource_ar_n : resource_ar_n option;
    (*

    The Amazon Resource Name (ARN) of the file system resource.

    *)
  10. kms_key_id : kms_key_id option;
    (*

    The ID of the Key Management Service (KMS) key used to encrypt Amazon FSx file system data. Used as follows with Amazon FSx file system types:

    • Amazon FSx for Lustre PERSISTENT_1 and PERSISTENT_2 deployment types only.

      SCRATCH_1 and SCRATCH_2 types are encrypted using the Amazon FSx service KMS key for your account.

    • Amazon FSx for NetApp ONTAP
    • Amazon FSx for OpenZFS
    • Amazon FSx for Windows File Server
    *)
  11. dns_name : dns_name option;
    (*

    The Domain Name System (DNS) name for the file system.

    *)
  12. network_interface_ids : network_interface_ids option;
    (*

    The IDs of the elastic network interfaces from which a specific file system is accessible. The elastic network interface is automatically created in the same virtual private cloud (VPC) that the Amazon FSx file system was created in. For more information, see Elastic Network Interfaces in the Amazon EC2 User Guide.

    For an Amazon FSx for Windows File Server file system, you can have one network interface ID. For an Amazon FSx for Lustre file system, you can have more than one.

    *)
  13. subnet_ids : subnet_ids option;
    (*

    Specifies the IDs of the subnets that the file system is accessible from. For the Amazon FSx Windows and ONTAP MULTI_AZ_1 file system deployment type, there are two subnet IDs, one for the preferred file server and one for the standby file server. The preferred file server subnet identified in the PreferredSubnetID property. All other file systems have only one subnet ID.

    For FSx for Lustre file systems, and Single-AZ Windows file systems, this is the ID of the subnet that contains the file system's endpoint. For MULTI_AZ_1 Windows and ONTAP file systems, the file system endpoint is available in the PreferredSubnetID.

    *)
  14. vpc_id : vpc_id option;
    (*

    The ID of the primary virtual private cloud (VPC) for the file system.

    *)
  15. storage_type : storage_type option;
    (*

    The type of storage the file system is using.

    • If set to SSD, the file system uses solid state drive storage.
    • If set to HDD, the file system uses hard disk drive storage.
    • If set to INTELLIGENT_TIERING, the file system uses fully elastic, intelligently-tiered storage.
    *)
  16. storage_capacity : storage_capacity option;
    (*

    The storage capacity of the file system in gibibytes (GiB).

    Amazon FSx responds with an HTTP status code 400 (Bad Request) if the value of StorageCapacity is outside of the minimum or maximum values.

    *)
  17. failure_details : file_system_failure_details option;
  18. lifecycle : file_system_lifecycle option;
    (*

    The lifecycle status of the file system. The following are the possible values and what they mean:

    • AVAILABLE - The file system is in a healthy state, and is reachable and available for use.
    • CREATING - Amazon FSx is creating the new file system.
    • DELETING - Amazon FSx is deleting an existing file system.
    • FAILED - An existing file system has experienced an unrecoverable failure. When creating a new file system, Amazon FSx was unable to create the file system.
    • MISCONFIGURED - The file system is in a failed but recoverable state.
    • MISCONFIGURED_UNAVAILABLE - (Amazon FSx for Windows File Server only) The file system is currently unavailable due to a change in your Active Directory configuration.
    • UPDATING - The file system is undergoing a customer-initiated update.
    *)
  19. file_system_type : file_system_type option;
    (*

    The type of Amazon FSx file system, which can be LUSTRE, WINDOWS, ONTAP, or OPENZFS.

    *)
  20. file_system_id : file_system_id option;
    (*

    The system-generated, unique 17-digit ID of the file system.

    *)
  21. creation_time : creation_time option;
    (*

    The time that the file system was created, in seconds (since 1970-01-01T00:00:00Z), also known as Unix time.

    *)
  22. owner_id : aws_account_id option;
    (*

    The Amazon Web Services account that created the file system. If the file system was created by a user in IAM Identity Center, the Amazon Web Services account to which the IAM user belongs is the owner.

    *)
}

A description of a specific Amazon FSx file system.

and snapshot = {
  1. administrative_actions : administrative_actions option;
    (*

    A list of administrative actions for the file system that are in process or waiting to be processed. Administrative actions describe changes to the Amazon FSx system.

    *)
  2. tags : tags option;
  3. lifecycle_transition_reason : lifecycle_transition_reason option;
  4. lifecycle : snapshot_lifecycle option;
    (*

    The lifecycle status of the snapshot.

    • PENDING - Amazon FSx hasn't started creating the snapshot.
    • CREATING - Amazon FSx is creating the snapshot.
    • DELETING - Amazon FSx is deleting the snapshot.
    • AVAILABLE - The snapshot is fully available.
    *)
  5. creation_time : creation_time option;
  6. volume_id : volume_id option;
    (*

    The ID of the volume that the snapshot is of.

    *)
  7. name : snapshot_name option;
    (*

    The name of the snapshot.

    *)
  8. snapshot_id : snapshot_id option;
    (*

    The ID of the snapshot.

    *)
  9. resource_ar_n : resource_ar_n option;
}

A snapshot of an Amazon FSx for OpenZFS volume.

and volume = {
  1. open_zfs_configuration : open_zfs_volume_configuration option;
    (*

    The configuration of an Amazon FSx for OpenZFS volume.

    *)
  2. administrative_actions : administrative_actions option;
    (*

    A list of administrative actions for the volume that are in process or waiting to be processed. Administrative actions describe changes to the volume that you have initiated using the UpdateVolume action.

    *)
  3. lifecycle_transition_reason : lifecycle_transition_reason option;
    (*

    The reason why the volume lifecycle status changed.

    *)
  4. volume_type : volume_type option;
    (*

    The type of the volume.

    *)
  5. volume_id : volume_id option;
    (*

    The system-generated, unique ID of the volume.

    *)
  6. tags : tags option;
  7. resource_ar_n : resource_ar_n option;
  8. ontap_configuration : ontap_volume_configuration option;
  9. name : volume_name option;
    (*

    The name of the volume.

    *)
  10. lifecycle : volume_lifecycle option;
    (*

    The lifecycle status of the volume.

    • AVAILABLE - The volume is fully available for use.
    • CREATED - The volume has been created.
    • CREATING - Amazon FSx is creating the new volume.
    • DELETING - Amazon FSx is deleting an existing volume.
    • FAILED - Amazon FSx was unable to create the volume.
    • MISCONFIGURED - The volume is in a failed but recoverable state.
    • PENDING - Amazon FSx hasn't started creating the volume.
    *)
  11. file_system_id : file_system_id option;
  12. creation_time : creation_time option;
}

Describes an Amazon FSx volume.

type nonrec volumes = volume list
type nonrec volume_not_found = {
  1. message : error_message option;
}

No Amazon FSx volumes were found based upon the supplied parameters.

type nonrec volume_ids = volume_id list
type nonrec volume_filter_name =
  1. | STORAGE_VIRTUAL_MACHINE_ID
  2. | FILE_SYSTEM_ID
type nonrec volume_filter_value = string
type nonrec volume_filter_values = volume_filter_value list
type nonrec volume_filter = {
  1. values : volume_filter_values option;
    (*

    The values of the filter. These are all the values for any of the applied filters.

    *)
  2. name : volume_filter_name option;
    (*

    The name for this filter.

    *)
}

A filter used to restrict the results of describe calls for Amazon FSx for NetApp ONTAP or Amazon FSx for OpenZFS volumes. You can use multiple filters to return results that meet all applied filter requirements.

type nonrec volume_filters = volume_filter list
type nonrec verbose_flag = string
type nonrec value = Smaws_Lib.CoreTypes.Int64.t
type nonrec update_volume_response = {
  1. volume : volume option;
    (*

    A description of the volume just updated. Returned after a successful UpdateVolume API operation.

    *)
}
type nonrec client_request_token = string
type nonrec update_snaplock_configuration = {
  1. volume_append_mode_enabled : flag option;
    (*

    Enables or disables volume-append mode on an FSx for ONTAP SnapLock volume. Volume-append mode allows you to create WORM-appendable files and write data to them incrementally. The default value is false.

    For more information, see Volume-append mode.

    *)
  2. retention_period : snaplock_retention_period option;
    (*

    Specifies the retention period of an FSx for ONTAP SnapLock volume.

    *)
  3. privileged_delete : privileged_delete option;
    (*

    Enables, disables, or permanently disables privileged delete on an FSx for ONTAP SnapLock Enterprise volume. Enabling privileged delete allows SnapLock administrators to delete write once, read many (WORM) files even if they have active retention periods. PERMANENTLY_DISABLED is a terminal state. If privileged delete is permanently disabled on a SnapLock volume, you can't re-enable it. The default value is DISABLED.

    For more information, see Privileged delete.

    *)
  4. autocommit_period : autocommit_period option;
    (*

    The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.

    *)
  5. audit_log_volume : flag option;
    (*

    Enables or disables the audit log volume for an FSx for ONTAP SnapLock volume. The default value is false. If you set AuditLogVolume to true, the SnapLock volume is created as an audit log volume. The minimum retention period for an audit log volume is six months.

    For more information, see SnapLock audit log volumes.

    *)
}

Updates the SnapLock configuration for an existing FSx for ONTAP volume.

type nonrec update_ontap_volume_configuration = {
  1. size_in_bytes : volume_capacity_bytes option;
    (*

    The configured size of the volume, in bytes.

    *)
  2. snaplock_configuration : update_snaplock_configuration option;
    (*

    The configuration object for updating the SnapLock configuration of an FSx for ONTAP SnapLock volume.

    *)
  3. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags for the volume should be copied to backups. This value defaults to false. If it's set to true, all tags for the volume are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the volume, regardless of this value.

    *)
  4. snapshot_policy : snapshot_policy option;
    (*

    Specifies the snapshot policy for the volume. There are three built-in snapshot policies:

    • default: This is the default policy. A maximum of six hourly snapshots taken five minutes past the hour. A maximum of two daily snapshots taken Monday through Saturday at 10 minutes after midnight. A maximum of two weekly snapshots taken every Sunday at 15 minutes after midnight.
    • default-1weekly: This policy is the same as the default policy except that it only retains one snapshot from the weekly schedule.
    • none: This policy does not take any snapshots. This policy can be assigned to volumes to prevent automatic snapshots from being taken.

    You can also provide the name of a custom policy that you created with the ONTAP CLI or REST API.

    For more information, see Snapshot policies in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  5. tiering_policy : tiering_policy option;
    (*

    Update the volume's data tiering policy.

    *)
  6. storage_efficiency_enabled : flag option;
    (*

    Default is false. Set to true to enable the deduplication, compression, and compaction storage efficiency features on the volume.

    *)
  7. size_in_megabytes : volume_capacity option;
    (*

    Specifies the size of the volume in megabytes.

    *)
  8. security_style : security_style option;
    (*

    The security style for the volume, which can be UNIX, NTFS, or MIXED.

    *)
  9. junction_path : junction_path option;
    (*

    Specifies the location in the SVM's namespace where the volume is mounted. The JunctionPath must have a leading forward slash, such as /vol3.

    *)
}

Used to specify changes to the ONTAP configuration for the volume you are updating.

type nonrec integer_no_max_from_negative_one = int
type nonrec update_open_zfs_volume_configuration = {
  1. read_only : read_only option;
    (*

    A Boolean value indicating whether the volume is read-only.

    *)
  2. user_and_group_quotas : open_zfs_user_and_group_quotas option;
    (*

    An object specifying how much storage users or groups can use on the volume.

    *)
  3. nfs_exports : open_zfs_nfs_exports option;
    (*

    The configuration object for mounting a Network File System (NFS) file system.

    *)
  4. data_compression_type : open_zfs_data_compression_type option;
    (*

    Specifies the method used to compress the data on the volume. The compression type is NONE by default.

    • NONE - Doesn't compress the data on the volume. NONE is the default.
    • ZSTD - Compresses the data in the volume using the Zstandard (ZSTD) compression algorithm. Compared to LZ4, Z-Standard provides a better compression ratio to minimize on-disk storage utilization.
    • LZ4 - Compresses the data in the volume using the LZ4 compression algorithm. Compared to Z-Standard, LZ4 is less compute-intensive and delivers higher write throughput speeds.
    *)
  5. record_size_ki_b : integer_record_size_ki_b option;
    (*

    Specifies the record size of an OpenZFS volume, in kibibytes (KiB). Valid values are 4, 8, 16, 32, 64, 128, 256, 512, or 1024 KiB. The default is 128 KiB. Most workloads should use the default record size. Database workflows can benefit from a smaller record size, while streaming workflows can benefit from a larger record size. For additional guidance on when to set a custom record size, see Tips for maximizing performance in the Amazon FSx for OpenZFS User Guide.

    *)
  6. storage_capacity_quota_gi_b : integer_no_max_from_negative_one option;
    (*

    The maximum amount of storage in gibibytes (GiB) that the volume can use from its parent. You can specify a quota larger than the storage on the parent volume. You can specify a value of -1 to unset a volume's storage capacity quota.

    *)
  7. storage_capacity_reservation_gi_b : integer_no_max_from_negative_one option;
    (*

    The amount of storage in gibibytes (GiB) to reserve from the parent volume. You can't reserve more storage than the parent volume has reserved. You can specify a value of -1 to unset a volume's storage capacity reservation.

    *)
}

Used to specify changes to the OpenZFS configuration for the volume that you are updating.

type nonrec update_volume_request = {
  1. open_zfs_configuration : update_open_zfs_volume_configuration option;
    (*

    The configuration of the OpenZFS volume that you are updating.

    *)
  2. name : volume_name option;
    (*

    The name of the OpenZFS volume. OpenZFS root volumes are automatically named FSX. Child volume names must be unique among their parent volume's children. The name of the volume is part of the mount string for the OpenZFS volume.

    *)
  3. ontap_configuration : update_ontap_volume_configuration option;
    (*

    The configuration of the ONTAP volume that you are updating.

    *)
  4. volume_id : volume_id;
    (*

    The ID of the volume that you want to update, in the format fsvol-0123456789abcdef0.

    *)
  5. client_request_token : client_request_token option;
}
type nonrec missing_volume_configuration = {
  1. message : error_message option;
}

A volume configuration is required for this operation.

type nonrec internal_server_error = {
  1. message : error_message option;
}

A generic error indicating a server-side failure.

type nonrec parameter = string
type nonrec incompatible_parameter_error = {
  1. message : error_message option;
  2. parameter : parameter;
    (*

    A parameter that is incompatible with the earlier request.

    *)
}

The error returned when a second request is received with the same client request token but different parameters settings. A client request token should always uniquely identify a single request.

type nonrec bad_request = {
  1. message : error_message option;
}

A generic error indicating a failure with a client request.

type nonrec directory_password = string
type nonrec self_managed_active_directory_configuration_updates = {
  1. domain_join_service_account_secret : customer_secrets_manager_ar_n option;
    (*

    Specifies the updated Amazon Resource Name (ARN) of the Amazon Web Services Secrets Manager secret containing the self-managed Active Directory domain join service account credentials. Amazon FSx uses this account to join to your self-managed Active Directory domain.

    *)
  2. file_system_administrators_group : file_system_administrators_group_name option;
    (*

    For FSx for ONTAP file systems only - Specifies the updated name of the self-managed Active Directory domain group whose members are granted administrative privileges for the Amazon FSx resource.

    *)
  3. organizational_unit_distinguished_name : organizational_unit_distinguished_name option;
    (*

    Specifies an updated fully qualified distinguished name of the organization unit within your self-managed Active Directory.

    *)
  4. domain_name : active_directory_fully_qualified_name option;
    (*

    Specifies an updated fully qualified domain name of your self-managed Active Directory configuration.

    *)
  5. dns_ips : dns_ips option;
    (*

    A list of up to three DNS server or domain controller IP addresses in your self-managed Active Directory domain.

    *)
  6. password : directory_password option;
    (*

    Specifies the updated password for the service account on your self-managed Active Directory domain. Amazon FSx uses this account to join to your self-managed Active Directory domain.

    *)
  7. user_name : directory_user_name option;
    (*

    Specifies the updated user name for the service account on your self-managed Active Directory domain. Amazon FSx uses this account to join to your self-managed Active Directory domain.

    This account must have the permissions required to join computers to the domain in the organizational unit provided in OrganizationalUnitDistinguishedName.

    *)
}

Specifies changes you are making to the self-managed Microsoft Active Directory configuration to which an FSx for Windows File Server file system or an FSx for ONTAP SVM is joined.

type nonrec net_bios_alias = string
type nonrec update_svm_active_directory_configuration = {
  1. net_bios_name : net_bios_alias option;
    (*

    Specifies an updated NetBIOS name of the AD computer object NetBiosName to which an SVM is joined.

    *)
  2. self_managed_active_directory_configuration : self_managed_active_directory_configuration_updates option;
}

Specifies updates to an FSx for ONTAP storage virtual machine's (SVM) Microsoft Active Directory (AD) configuration. Note that account credentials are not returned in the response payload.

type nonrec svm_active_directory_configuration = {
  1. self_managed_active_directory_configuration : self_managed_active_directory_attributes option;
  2. net_bios_name : net_bios_alias option;
    (*

    The NetBIOS name of the AD computer object to which the SVM is joined.

    *)
}

Describes the Microsoft Active Directory (AD) directory configuration to which the FSx for ONTAP storage virtual machine (SVM) is joined. Note that account credentials are not returned in the response payload.

type nonrec svm_endpoint = {
  1. ipv6_addresses : ontap_endpoint_ip_addresses option;
    (*

    The SVM endpoint's IPv6 addresses.

    *)
  2. ip_addresses : ontap_endpoint_ip_addresses option;
    (*

    The SVM endpoint's IPv4 addresses.

    *)
  3. dns_name : dns_name option;
}

An Amazon FSx for NetApp ONTAP storage virtual machine (SVM) has four endpoints that are used to access data or to manage the SVM using the NetApp ONTAP CLI, REST API, or NetApp CloudManager. They are the Iscsi, Management, Nfs, and Smb endpoints.

type nonrec svm_endpoints = {
  1. smb : svm_endpoint option;
    (*

    An endpoint for connecting using the Server Message Block (SMB) protocol.

    *)
  2. nfs : svm_endpoint option;
    (*

    An endpoint for connecting using the Network File System (NFS) protocol.

    *)
  3. management : svm_endpoint option;
    (*

    An endpoint for managing SVMs using the NetApp ONTAP CLI, NetApp ONTAP API, or NetApp CloudManager.

    *)
  4. iscsi : svm_endpoint option;
    (*

    An endpoint for connecting using the Internet Small Computer Systems Interface (iSCSI) protocol.

    *)
}

An Amazon FSx for NetApp ONTAP storage virtual machine (SVM) has the following endpoints that are used to access data or to manage the SVM using the NetApp ONTAP CLI, REST API, or NetApp CloudManager.

type nonrec storage_virtual_machine_lifecycle =
  1. | PENDING
  2. | MISCONFIGURED
  3. | FAILED
  4. | DELETING
  5. | CREATING
  6. | CREATED
type nonrec storage_virtual_machine_name = string
type nonrec storage_virtual_machine_subtype =
  1. | SYNC_SOURCE
  2. | SYNC_DESTINATION
  3. | DP_DESTINATION
  4. | DEFAULT
type nonrec storage_virtual_machine_root_volume_security_style =
  1. | MIXED
  2. | NTFS
  3. | UNIX
type nonrec storage_virtual_machine = {
  1. root_volume_security_style : storage_virtual_machine_root_volume_security_style option;
    (*

    The security style of the root volume of the SVM.

    *)
  2. lifecycle_transition_reason : lifecycle_transition_reason option;
    (*

    Describes why the SVM lifecycle state changed.

    *)
  3. tags : tags option;
  4. uui_d : uui_d option;
    (*

    The SVM's UUID (universally unique identifier).

    *)
  5. subtype : storage_virtual_machine_subtype option;
    (*

    Describes the SVM's subtype.

    *)
  6. storage_virtual_machine_id : storage_virtual_machine_id option;
    (*

    The SVM's system generated unique ID.

    *)
  7. resource_ar_n : resource_ar_n option;
  8. name : storage_virtual_machine_name option;
    (*

    The name of the SVM, if provisioned.

    *)
  9. lifecycle : storage_virtual_machine_lifecycle option;
    (*

    Describes the SVM's lifecycle status.

    • CREATED - The SVM is fully available for use.
    • CREATING - Amazon FSx is creating the new SVM.
    • DELETING - Amazon FSx is deleting an existing SVM.
    • FAILED - Amazon FSx was unable to create the SVM.
    • MISCONFIGURED - The SVM is in a failed but recoverable state.
    • PENDING - Amazon FSx has not started creating the SVM.
    *)
  10. file_system_id : file_system_id option;
  11. endpoints : svm_endpoints option;
    (*

    The endpoints that are used to access data or to manage the SVM using the NetApp ONTAP CLI, REST API, or NetApp CloudManager. They are the Iscsi, Management, Nfs, and Smb endpoints.

    *)
  12. creation_time : creation_time option;
  13. active_directory_configuration : svm_active_directory_configuration option;
    (*

    Describes the Microsoft Active Directory configuration to which the SVM is joined, if applicable.

    *)
}

Describes the Amazon FSx for NetApp ONTAP storage virtual machine (SVM) configuration.

type nonrec update_storage_virtual_machine_response = {
  1. storage_virtual_machine : storage_virtual_machine option;
}
type nonrec update_storage_virtual_machine_request = {
  1. svm_admin_password : admin_password option;
    (*

    Specifies a new SvmAdminPassword.

    *)
  2. storage_virtual_machine_id : storage_virtual_machine_id;
    (*

    The ID of the SVM that you want to update, in the format svm-0123456789abcdef0.

    *)
  3. client_request_token : client_request_token option;
  4. active_directory_configuration : update_svm_active_directory_configuration option;
    (*

    Specifies updates to an SVM's Microsoft Active Directory (AD) configuration.

    *)
}
type nonrec unsupported_operation = {
  1. message : error_message option;
}

The requested operation is not supported for this resource or API.

type nonrec storage_virtual_machine_not_found = {
  1. message : error_message option;
}

No FSx for ONTAP SVMs were found based upon the supplied parameters.

type nonrec update_snapshot_response = {
  1. snapshot : snapshot option;
    (*

    Returned after a successful UpdateSnapshot operation, describing the snapshot that you updated.

    *)
}
type nonrec update_snapshot_request = {
  1. snapshot_id : snapshot_id;
    (*

    The ID of the snapshot that you want to update, in the format fsvolsnap-0123456789abcdef0.

    *)
  2. name : snapshot_name;
    (*

    The name of the snapshot to update.

    *)
  3. client_request_token : client_request_token option;
}
type nonrec snapshot_not_found = {
  1. message : error_message option;
}

No Amazon FSx snapshots were found based on the supplied parameters.

type nonrec update_shared_vpc_configuration_response = {
  1. enable_fsx_route_table_updates_from_participant_accounts : verbose_flag option;
    (*

    Indicates whether participant accounts can create FSx for ONTAP Multi-AZ file systems in shared subnets.

    *)
}
type nonrec update_shared_vpc_configuration_request = {
  1. client_request_token : client_request_token option;
  2. enable_fsx_route_table_updates_from_participant_accounts : verbose_flag option;
    (*

    Specifies whether participant accounts can create FSx for ONTAP Multi-AZ file systems in shared subnets. Set to true to enable or false to disable.

    *)
}
type nonrec update_open_zfs_volume_option =
  1. | DELETE_INTERMEDIATE_DATA
  2. | DELETE_CLONED_VOLUMES
  3. | DELETE_INTERMEDIATE_SNAPSHOTS
type nonrec update_open_zfs_volume_options = update_open_zfs_volume_option list
type nonrec update_file_system_windows_configuration = {
  1. fsrm_configuration : windows_fsrm_configuration option;
    (*

    The File Server Resource Manager (FSRM) configuration that Amazon FSx for Windows File Server uses for the file system. FSRM is disabled by default.

    *)
  2. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS (input/output operations per second) configuration for an Amazon FSx for Windows file system. By default, Amazon FSx automatically provisions 3 IOPS per GiB of storage capacity. You can provision additional IOPS per GiB of storage, up to the maximum limit associated with your chosen throughput capacity.

    *)
  3. audit_log_configuration : windows_audit_log_create_configuration option;
    (*

    The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system..

    *)
  4. self_managed_active_directory_configuration : self_managed_active_directory_configuration_updates option;
    (*

    The configuration Amazon FSx uses to join the Windows File Server instance to the self-managed Microsoft AD directory. You cannot make a self-managed Microsoft AD update request if there is an existing self-managed Microsoft AD update request in progress.

    *)
  5. throughput_capacity : megabytes_per_second option;
    (*

    Sets the target value for a file system's throughput capacity, in MB/s, that you are updating the file system to. Valid values are 8, 16, 32, 64, 128, 256, 512, 1024, 2048. You cannot make a throughput capacity update request if there is an existing throughput capacity update request in progress. For more information, see Managing Throughput Capacity.

    *)
  6. automatic_backup_retention_days : automatic_backup_retention_days option;
    (*

    The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 30. For more information, see Working with Automatic Daily Backups.

    *)
  7. daily_automatic_backup_start_time : daily_time option;
    (*

    The preferred time to start the daily automatic backup, in the UTC time zone, for example, 02:00

    *)
  8. weekly_maintenance_start_time : weekly_time option;
    (*

    The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. Where d is the weekday number, from 1 through 7, with 1 = Monday and 7 = Sunday.

    *)
}

Updates the configuration for an existing Amazon FSx for Windows File Server file system. Amazon FSx only overwrites existing properties with non-null values provided in the request.

type nonrec update_file_system_response = {
  1. file_system : file_system option;
    (*

    A description of the file system that was updated.

    *)
}

The response object for the UpdateFileSystem operation.

type nonrec lustre_log_create_configuration = {
  1. destination : general_ar_n option;
    (*

    The Amazon Resource Name (ARN) that specifies the destination of the logs.

    The destination can be any Amazon CloudWatch Logs log group ARN, with the following requirements:

    • The destination ARN that you provide must be in the same Amazon Web Services partition, Amazon Web Services Region, and Amazon Web Services account as your Amazon FSx file system.
    • The name of the Amazon CloudWatch Logs log group must begin with the /aws/fsx prefix.
    • If you do not provide a destination, Amazon FSx will create and use a log stream in the CloudWatch Logs /aws/fsx/lustre log group (for Amazon FSx for Lustre) or /aws/fsx/filecache (for Amazon File Cache).
    • If Destination is provided and the resource does not exist, the request will fail with a BadRequest error.
    • If Level is set to DISABLED, you cannot specify a destination in Destination.
    *)
  2. level : lustre_access_audit_log_level;
    (*

    Sets which data repository events are logged by Amazon FSx.

    • WARN_ONLY - only warning events are logged.
    • ERROR_ONLY - only error events are logged.
    • WARN_ERROR - both warning events and error events are logged.
    • DISABLED - logging of data repository events is turned off.
    *)
}

The Lustre logging configuration used when creating or updating an Amazon FSx for Lustre file system. An Amazon File Cache is created with Lustre logging enabled by default, with a setting of WARN_ERROR for the logging events. which can't be changed.

Lustre logging writes the enabled logging events for your file system or cache to Amazon CloudWatch Logs.

type nonrec update_file_system_lustre_metadata_configuration = {
  1. mode : metadata_configuration_mode option;
    (*

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

    • To increase the Metadata IOPS or to switch an SSD file system from AUTOMATIC, specify USER_PROVISIONED as the value for this parameter. Then use the Iops parameter to provide a Metadata IOPS value that is greater than or equal to the current number of Metadata IOPS provisioned for the file system.
    • To switch from USER_PROVISIONED mode on an SSD file system, specify AUTOMATIC as the value for this parameter, but do not input a value for Iops.

      • If you request to switch from USER_PROVISIONED to AUTOMATIC mode and the current Metadata IOPS value is greater than the automated default, FSx for Lustre rejects the request because downscaling Metadata IOPS is not supported.
      • AUTOMATIC mode is not supported on Intelligent-Tiering file systems. For Intelligent-Tiering file systems, use USER_PROVISIONED mode.
    *)
  2. iops : metadata_iops option;
    (*

    (USER_PROVISIONED mode only) Specifies the number of Metadata IOPS to provision for your file system.

    • For SSD file systems, valid values are 1500, 3000, 6000, 12000, and multiples of 12000 up to a maximum of 192000.
    • For Intelligent-Tiering file systems, valid values are 6000 and 12000.

    The value you provide must be greater than or equal to the current number of Metadata IOPS provisioned for the file system.

    *)
}

The Lustre metadata performance configuration update for an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. You can request an increase in your file system's Metadata IOPS and/or switch your file system's metadata configuration mode. For more information, see Managing metadata performance in the Amazon FSx for Lustre User Guide.

type nonrec update_file_system_lustre_configuration = {
  1. data_read_cache_configuration : lustre_read_cache_configuration option;
    (*

    Specifies the optional provisioned SSD read cache on Amazon FSx for Lustre file systems that use the Intelligent-Tiering storage class.

    *)
  2. throughput_capacity : throughput_capacity_mbps option;
    (*

    The throughput of an Amazon FSx for Lustre file system using an Intelligent-Tiering storage class, measured in megabytes per second (MBps). You can only increase your file system's throughput. Valid values are 4000 MBps or multiples of 4000 MBps.

    *)
  3. metadata_configuration : update_file_system_lustre_metadata_configuration option;
    (*

    The Lustre metadata performance configuration for an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. When this configuration is enabled, the file system supports increasing metadata performance.

    *)
  4. per_unit_storage_throughput : per_unit_storage_throughput option;
    (*

    The throughput of an Amazon FSx for Lustre Persistent SSD-based file system, measured in megabytes per second per tebibyte (MB/s/TiB). You can increase or decrease your file system's throughput. Valid values depend on the deployment type of the file system, as follows:

    • For PERSISTENT_1 SSD-based deployment types, valid values are 50, 100, and 200 MB/s/TiB.
    • For PERSISTENT_2 SSD-based deployment types, valid values are 125, 250, 500, and 1000 MB/s/TiB.

    For more information, see Managing throughput capacity.

    *)
  5. root_squash_configuration : lustre_root_squash_configuration option;
    (*

    The Lustre root squash configuration used when updating an Amazon FSx for Lustre file system. When enabled, root squash restricts root-level access from clients that try to access your file system as a root user.

    *)
  6. log_configuration : lustre_log_create_configuration option;
    (*

    The Lustre logging configuration used when updating an Amazon FSx for Lustre file system. When logging is enabled, Lustre logs error and warning events for data repositories associated with your file system to Amazon CloudWatch Logs.

    *)
  7. data_compression_type : data_compression_type option;
    (*

    Sets the data compression configuration for the file system. DataCompressionType can have the following values:

    • NONE - Data compression is turned off for the file system.
    • LZ4 - Data compression is turned on with the LZ4 algorithm.

    If you don't use DataCompressionType, the file system retains its current data compression configuration.

    For more information, see Lustre data compression.

    *)
  8. auto_import_policy : auto_import_policy_type option;
    (*

    (Optional) When you create your file system, your existing S3 objects appear as file and directory listings. Use this property to choose how Amazon FSx keeps your file and directory listing up to date as you add or modify objects in your linked S3 bucket. AutoImportPolicy can have the following values:

    • NONE - (Default) AutoImport is off. Amazon FSx only updates file and directory listings from the linked S3 bucket when the file system is created. FSx does not update the file and directory listing for any new or changed objects after choosing this option.
    • NEW - AutoImport is on. Amazon FSx automatically imports directory listings of any new objects added to the linked S3 bucket that do not currently exist in the FSx file system.
    • NEW_CHANGED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket and any existing objects that are changed in the S3 bucket after you choose this option.
    • NEW_CHANGED_DELETED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket, any existing objects that are changed in the S3 bucket, and any objects that were deleted in the S3 bucket.

    This parameter is not supported for file systems with a data repository association.

    *)
  9. automatic_backup_retention_days : automatic_backup_retention_days option;
    (*

    The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 0.

    *)
  10. daily_automatic_backup_start_time : daily_time option;
  11. weekly_maintenance_start_time : weekly_time option;
    (*

    (Optional) The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone. d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.

    *)
}

The configuration object for Amazon FSx for Lustre file systems used in the UpdateFileSystem operation.

type nonrec update_file_system_ontap_configuration = {
  1. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  2. ha_pairs : ha_pairs option;
    (*

    Use to update the number of high-availability (HA) pairs for a second-generation single-AZ file system. If you increase the number of HA pairs for your file system, you must specify proportional increases for StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide. Block storage protocol support (iSCSI and NVMe over TCP) is disabled on file systems with more than 6 HA pairs. For more information, see Using block storage protocols.

    *)
  3. throughput_capacity_per_ha_pair : throughput_capacity_per_ha_pair option;
    (*

    Use to choose the throughput capacity per HA pair, rather than the total throughput for the file system.

    This field and ThroughputCapacity cannot be defined in the same API call, but one is required.

    This field and ThroughputCapacity are the same for file systems with one HA pair.

    • For SINGLE_AZ_1 and MULTI_AZ_1 file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps.
    • For SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps.
    • For MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value for file systems with one HA pair.
    • The value of deployment type is SINGLE_AZ_2 and ThroughputCapacity / ThroughputCapacityPerHAPair is not a valid HA pair (a value between 1 and 12).
    • The value of ThroughputCapacityPerHAPair is not a valid value.
    *)
  4. remove_route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) A list of IDs of existing virtual private cloud (VPC) route tables to disassociate (remove) from your Amazon FSx for NetApp ONTAP file system. You can use the API operation to retrieve the list of VPC route table IDs for a file system.

    *)
  5. add_route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) A list of IDs of new virtual private cloud (VPC) route tables to associate (add) with your Amazon FSx for NetApp ONTAP file system.

    *)
  6. throughput_capacity : megabytes_per_second option;
    (*

    Enter a new value to change the amount of throughput capacity for the file system in megabytes per second (MBps). For more information, see Managing throughput capacity in the FSx for ONTAP User Guide.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value.
    • The value of ThroughputCapacity when divided by the value of HAPairs is outside of the valid range for ThroughputCapacity.
    *)
  7. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS (input output operations per second) configuration for an Amazon FSx for NetApp ONTAP file system. The default is 3 IOPS per GB of storage capacity, but you can provision additional IOPS per GB of storage. The configuration consists of an IOPS mode (AUTOMATIC or USER_PROVISIONED), and in the case of USER_PROVISIONED IOPS, the total number of SSD IOPS provisioned. For more information, see File system storage capacity and IOPS.

    *)
  8. weekly_maintenance_start_time : weekly_time option;
  9. fsx_admin_password : admin_password option;
    (*

    Update the password for the fsxadmin user by entering a new password. You use the fsxadmin user to access the NetApp ONTAP CLI and REST API to manage your file system resources. For more information, see Managing resources using NetApp Application.

    *)
  10. daily_automatic_backup_start_time : daily_time option;
  11. automatic_backup_retention_days : automatic_backup_retention_days option;
}

The configuration updates for an Amazon FSx for NetApp ONTAP file system.

type nonrec update_file_system_open_zfs_configuration = {
  1. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  2. read_cache_configuration : open_zfs_read_cache_configuration option;
    (*

    The configuration for the optional provisioned SSD read cache on file systems that use the Intelligent-Tiering storage class.

    *)
  3. remove_route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) A list of IDs of existing virtual private cloud (VPC) route tables to disassociate (remove) from your Amazon FSx for OpenZFS file system. You can use the API operation to retrieve the list of VPC route table IDs for a file system.

    *)
  4. add_route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) A list of IDs of new virtual private cloud (VPC) route tables to associate (add) with your Amazon FSx for OpenZFS file system.

    *)
  5. disk_iops_configuration : disk_iops_configuration option;
  6. weekly_maintenance_start_time : weekly_time option;
  7. throughput_capacity : megabytes_per_second option;
    (*

    The throughput of an Amazon FSx for OpenZFS file system, measured in megabytes per second
 (MB/s). Valid values depend on the DeploymentType you choose, as follows:

    • For MULTI_AZ_1 and SINGLE_AZ_2, valid values are 160, 320, 640, 1280, 2560, 3840, 5120, 7680, or 10240 MB/s.
    • For SINGLE_AZ_1, valid values are 64, 128, 256, 512, 1024, 2048, 3072, or 4096 MB/s.
    *)
  8. daily_automatic_backup_start_time : daily_time option;
  9. copy_tags_to_volumes : flag option;
    (*

    A Boolean value indicating whether tags for the volume should be copied to snapshots. This value defaults to false. If it's set to true, all tags for the volume are copied to snapshots where the user doesn't specify tags. If this value is true and you specify one or more tags, only the specified tags are copied to snapshots. If you specify one or more tags when creating the snapshot, no tags are copied from the volume, regardless of this value.

    *)
  10. copy_tags_to_backups : flag option;
    (*

    A Boolean value indicating whether tags for the file system should be copied to backups. This value defaults to false. If it's set to true, all tags for the file system are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    *)
  11. automatic_backup_retention_days : automatic_backup_retention_days option;
}

The configuration updates for an Amazon FSx for OpenZFS file system.

type nonrec update_file_system_request = {
  1. network_type : network_type option;
    (*

    Changes the network type of an FSx for OpenZFS file system.

    *)
  2. file_system_type_version : file_system_type_version option;
    (*

    The Lustre version you are updating an FSx for Lustre file system to. Valid values are 2.12 and 2.15. The value you choose must be newer than the file system's current Lustre version.

    *)
  3. storage_type : storage_type option;
  4. open_zfs_configuration : update_file_system_open_zfs_configuration option;
    (*

    The configuration updates for an FSx for OpenZFS file system.

    *)
  5. ontap_configuration : update_file_system_ontap_configuration option;
  6. lustre_configuration : update_file_system_lustre_configuration option;
  7. windows_configuration : update_file_system_windows_configuration option;
    (*

    The configuration updates for an Amazon FSx for Windows File Server file system.

    *)
  8. storage_capacity : storage_capacity option;
    (*

    Use this parameter to increase the storage capacity of an FSx for Windows File Server, FSx for Lustre, FSx for OpenZFS, or FSx for ONTAP file system. For second-generation FSx for ONTAP file systems, you can also decrease the storage capacity. Specifies the storage capacity target value, in GiB, for the file system that you're updating.

    You can't make a storage capacity increase request if there is an existing storage capacity increase request in progress.

    For Lustre file systems, the storage capacity target value can be the following:

    • For SCRATCH_2, PERSISTENT_1, and PERSISTENT_2 SSD deployment types, valid values are in multiples of 2400 GiB. The value must be greater than the current storage capacity.
    • For PERSISTENT HDD file systems, valid values are multiples of 6000 GiB for 12-MBps throughput per TiB file systems and multiples of 1800 GiB for 40-MBps throughput per TiB file systems. The values must be greater than the current storage capacity.
    • For SCRATCH_1 file systems, you can't increase the storage capacity.

    For more information, see Managing storage and throughput capacity in the FSx for Lustre User Guide.

    For FSx for OpenZFS file systems, the storage capacity target value must be at least 10 percent greater than the current storage capacity value. For more information, see Managing storage capacity in the FSx for OpenZFS User Guide.

    For Windows file systems, the storage capacity target value must be at least 10 percent greater than the current storage capacity value. To increase storage capacity, the file system must have at least 16 MBps of throughput capacity. For more information, see Managing storage capacity in the Amazon FSxfor Windows File Server User Guide.

    For ONTAP file systems, when increasing storage capacity, the storage capacity target value must be at least 10 percent greater than the current storage capacity value. When decreasing storage capacity on second-generation file systems, the target value must be at least 9 percent smaller than the current SSD storage capacity. For more information, see File system storage capacity and IOPS in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  9. client_request_token : client_request_token option;
    (*

    A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent updates. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.

    *)
  10. file_system_id : file_system_id;
    (*

    The ID of the file system that you are updating.

    *)
}

The request object for the UpdateFileSystem operation.

type nonrec service_limit =
  1. | FILE_CACHE_COUNT
  2. | TOTAL_SSD_IOPS
  3. | VOLUMES_PER_FILE_SYSTEM
  4. | STORAGE_VIRTUAL_MACHINES_PER_FILE_SYSTEM
  5. | TOTAL_IN_PROGRESS_COPY_BACKUPS
  6. | TOTAL_USER_TAGS
  7. | TOTAL_USER_INITIATED_BACKUPS
  8. | TOTAL_STORAGE
  9. | TOTAL_THROUGHPUT_CAPACITY
  10. | FILE_SYSTEM_COUNT

The types of limits on your service utilization. Limits include file system count, total throughput capacity, total storage, and total user-initiated backups. These limits apply for a specific account in a specific Amazon Web Services Region. You can increase some of them by contacting Amazon Web Services Support.

type nonrec service_limit_exceeded = {
  1. message : error_message option;
  2. limit : service_limit;
    (*

    Enumeration of the service limit that was exceeded.

    *)
}

An error indicating that a particular service limit was exceeded. You can increase some service limits by contacting Amazon Web Services Support.

type nonrec missing_file_system_configuration = {
  1. message : error_message option;
}

A file system configuration is required for this operation.

type nonrec security_group_id = string
type nonrec invalid_network_settings = {
  1. invalid_route_table_id : route_table_id option;
    (*

    The route table ID is either invalid or not part of the VPC specified.

    *)
  2. invalid_security_group_id : security_group_id option;
    (*

    The security group ID is either invalid or not part of the VPC specified.

    *)
  3. invalid_subnet_id : subnet_id option;
    (*

    The subnet ID that is either invalid or not part of the VPC specified.

    *)
  4. message : error_message option;
    (*

    Error message explaining what's wrong with network settings.

    *)
}

One or more network settings specified in the request are invalid.

type nonrec file_system_not_found = {
  1. message : error_message option;
}

No Amazon FSx file systems were found based upon supplied parameters.

type nonrec file_cache_id = string
type nonrec file_cache_type =
  1. | LUSTRE
type nonrec file_cache_lifecycle =
  1. | FAILED
  2. | UPDATING
  3. | DELETING
  4. | CREATING
  5. | AVAILABLE
type nonrec file_cache_failure_details = {
  1. message : error_message option;
    (*

    A message describing any failures that occurred.

    *)
}

A structure providing details of any failures that occurred.

type nonrec file_cache_lustre_deployment_type =
  1. | CACHE_1
type nonrec metadata_storage_capacity = int
type nonrec file_cache_lustre_metadata_configuration = {
  1. storage_capacity : metadata_storage_capacity;
    (*

    The storage capacity of the Lustre MDT (Metadata Target) storage volume in gibibytes (GiB). The only supported value is 2400 GiB.

    *)
}

The configuration for a Lustre MDT (Metadata Target) storage volume. The metadata on Amazon File Cache is managed by a Lustre Metadata Server (MDS) while the actual metadata is persisted on an MDT.

type nonrec file_cache_lustre_configuration = {
  1. log_configuration : lustre_log_configuration option;
    (*

    The configuration for Lustre logging used to write the enabled logging events for your Amazon File Cache resource to Amazon CloudWatch Logs.

    *)
  2. metadata_configuration : file_cache_lustre_metadata_configuration option;
    (*

    The configuration for a Lustre MDT (Metadata Target) storage volume.

    *)
  3. weekly_maintenance_start_time : weekly_time option;
  4. mount_name : lustre_file_system_mount_name option;
    (*

    You use the MountName value when mounting the cache. If you pass a cache ID to the DescribeFileCaches operation, it returns the the MountName value as part of the cache's description.

    *)
  5. deployment_type : file_cache_lustre_deployment_type option;
    (*

    The deployment type of the Amazon File Cache resource, which must be CACHE_1.

    *)
  6. per_unit_storage_throughput : per_unit_storage_throughput option;
    (*

    Per unit storage throughput represents the megabytes per second of read or write throughput per 1 tebibyte of storage provisioned. Cache throughput capacity is equal to Storage capacity (TiB) * PerUnitStorageThroughput (MB/s/TiB). The only supported value is 1000.

    *)
}

The configuration for the Amazon File Cache resource.

type nonrec data_repository_association_id = string
type nonrec data_repository_association_ids = data_repository_association_id list
type nonrec file_cache = {
  1. data_repository_association_ids : data_repository_association_ids option;
    (*

    A list of IDs of data repository associations that are associated with this cache.

    *)
  2. lustre_configuration : file_cache_lustre_configuration option;
    (*

    The configuration for the Amazon File Cache resource.

    *)
  3. resource_ar_n : resource_ar_n option;
  4. kms_key_id : kms_key_id option;
    (*

    Specifies the ID of the Key Management Service (KMS) key to use for encrypting data on an Amazon File Cache. If a KmsKeyId isn't specified, the Amazon FSx-managed KMS key for your account is used. For more information, see Encrypt in the Key Management Service API Reference.

    *)
  5. dns_name : dns_name option;
    (*

    The Domain Name System (DNS) name for the cache.

    *)
  6. network_interface_ids : network_interface_ids option;
  7. subnet_ids : subnet_ids option;
  8. vpc_id : vpc_id option;
  9. storage_capacity : storage_capacity option;
    (*

    The storage capacity of the cache in gibibytes (GiB).

    *)
  10. failure_details : file_cache_failure_details option;
    (*

    A structure providing details of any failures that occurred.

    *)
  11. lifecycle : file_cache_lifecycle option;
    (*

    The lifecycle status of the cache. The following are the possible values and what they mean:

    • AVAILABLE - The cache is in a healthy state, and is reachable and available for use.
    • CREATING - The new cache is being created.
    • DELETING - An existing cache is being deleted.
    • UPDATING - The cache is undergoing a customer-initiated update.
    • FAILED - An existing cache has experienced an unrecoverable failure. When creating a new cache, the cache was unable to be created.
    *)
  12. file_cache_type_version : file_system_type_version option;
    (*

    The Lustre version of the cache, which must be 2.12.

    *)
  13. file_cache_type : file_cache_type option;
    (*

    The type of cache, which must be LUSTRE.

    *)
  14. file_cache_id : file_cache_id option;
    (*

    The system-generated, unique ID of the cache.

    *)
  15. creation_time : creation_time option;
  16. owner_id : aws_account_id option;
}

A description of a specific Amazon File Cache resource, which is a response object from the DescribeFileCaches operation.

type nonrec update_file_cache_response = {
  1. file_cache : file_cache option;
    (*

    A description of the cache that was updated.

    *)
}
type nonrec update_file_cache_lustre_configuration = {
  1. weekly_maintenance_start_time : weekly_time option;
}

The configuration update for an Amazon File Cache resource.

type nonrec update_file_cache_request = {
  1. lustre_configuration : update_file_cache_lustre_configuration option;
    (*

    The configuration updates for an Amazon File Cache resource.

    *)
  2. client_request_token : client_request_token option;
  3. file_cache_id : file_cache_id;
    (*

    The ID of the cache that you are updating.

    *)
}
type nonrec missing_file_cache_configuration = {
  1. message : error_message option;
}

A cache configuration is required for this operation.

type nonrec file_cache_not_found = {
  1. message : error_message option;
}

No caches were found based upon supplied parameters.

type nonrec namespace = string
type nonrec batch_import_meta_data_on_create = bool
type nonrec event_type =
  1. | DELETED
  2. | CHANGED
  3. | NEW
type nonrec event_types = event_type list
type nonrec auto_import_policy = {
  1. events : event_types option;
    (*

    The AutoImportPolicy can have the following event values:

    • NEW - Amazon FSx automatically imports metadata of files added to the linked S3 bucket that do not currently exist in the FSx file system.
    • CHANGED - Amazon FSx automatically updates file metadata and invalidates existing file content on the file system as files change in the data repository.
    • DELETED - Amazon FSx automatically deletes files on the file system as corresponding files are deleted in the data repository.

    You can define any combination of event types for your AutoImportPolicy.

    *)
}

Describes the data repository association's automatic import policy. The AutoImportPolicy defines how Amazon FSx keeps your file metadata and directory listings up to date by importing changes to your Amazon FSx for Lustre file system as you modify objects in a linked S3 bucket.

The AutoImportPolicy is only supported on Amazon FSx for Lustre file systems with a data repository association.

type nonrec auto_export_policy = {
  1. events : event_types option;
    (*

    The AutoExportPolicy can have the following event values:

    • NEW - New files and directories are automatically exported to the data repository as they are added to the file system.
    • CHANGED - Changes to files and directories on the file system are automatically exported to the data repository.
    • DELETED - Files and directories are automatically deleted on the data repository when they are deleted on the file system.

    You can define any combination of event types for your AutoExportPolicy.

    *)
}

Describes a data repository association's automatic export policy. The AutoExportPolicy defines the types of updated objects on the file system that will be automatically exported to the data repository. As you create, modify, or delete files, Amazon FSx for Lustre automatically exports the defined changes asynchronously once your application finishes modifying the file.

The AutoExportPolicy is only supported on Amazon FSx for Lustre file systems with a data repository association.

type nonrec s3_data_repository_configuration = {
  1. auto_export_policy : auto_export_policy option;
    (*

    Specifies the type of updated objects (new, changed, deleted) that will be automatically exported from your file system to the linked S3 bucket.

    *)
  2. auto_import_policy : auto_import_policy option;
    (*

    Specifies the type of updated objects (new, changed, deleted) that will be automatically imported from the linked S3 bucket to your file system.

    *)
}

The configuration for an Amazon S3 data repository linked to an Amazon FSx for Lustre file system with a data repository association. The configuration consists of an AutoImportPolicy that defines which file events on the data repository are automatically imported to the file system and an AutoExportPolicy that defines which file events on the file system are automatically exported to the data repository. File events are when files or directories are added, changed, or deleted on the file system or the data repository.

Data repository associations on Amazon File Cache don't use S3DataRepositoryConfiguration because they don't support automatic import or automatic export.

type nonrec sub_directories_paths = namespace list
type nonrec nfs_version =
  1. | NFS3
type nonrec repository_dns_ips = ip_address list
type nonrec nfs_data_repository_configuration = {
  1. auto_export_policy : auto_export_policy option;
    (*

    This parameter is not supported for Amazon File Cache.

    *)
  2. dns_ips : repository_dns_ips option;
    (*

    A list of up to 2 IP addresses of DNS servers used to resolve the NFS file system domain name. The provided IP addresses can either be the IP addresses of a DNS forwarder or resolver that the customer manages and runs inside the customer VPC, or the IP addresses of the on-premises DNS servers.

    *)
  3. version : nfs_version;
    (*

    The version of the NFS (Network File System) protocol of the NFS data repository. Currently, the only supported value is NFS3, which indicates that the data repository must support the NFSv3 protocol.

    *)
}

The configuration for a data repository association that links an Amazon File Cache resource to an NFS data repository.

type nonrec data_repository_association = {
  1. nf_s : nfs_data_repository_configuration option;
    (*

    The configuration for an NFS data repository linked to an Amazon File Cache resource with a data repository association.

    *)
  2. data_repository_subdirectories : sub_directories_paths option;
    (*

    For Amazon File Cache, a list of NFS Exports that will be linked with an NFS data repository association. All the subdirectories must be on a single NFS file system. The Export paths are in the format /exportpath1. To use this parameter, you must configure DataRepositoryPath as the domain name of the NFS file system. The NFS file system domain name in effect is the root of the subdirectories. Note that DataRepositorySubdirectories is not supported for S3 data repositories.

    *)
  3. file_cache_path : namespace option;
    (*

    A path on the Amazon File Cache that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the path is required. Two data repository associations cannot have overlapping cache paths. For example, if a data repository is associated with cache path /ns1/, then you cannot link another data repository with cache path /ns1/ns2.

    This path specifies the directory in your cache where files will be exported from. This cache directory can be linked to only one data repository (S3 or NFS) and no other data repository can be linked to the directory.

    The cache path can only be set to root (/) on an NFS DRA when DataRepositorySubdirectories is specified. If you specify root (/) as the cache path, you can create only one DRA on the cache.

    The cache path cannot be set to root (/) for an S3 DRA.

    *)
  4. file_cache_id : file_cache_id option;
    (*

    The globally unique ID of the Amazon File Cache resource.

    *)
  5. creation_time : creation_time option;
  6. tags : tags option;
  7. s3 : s3_data_repository_configuration option;
    (*

    The configuration for an Amazon S3 data repository linked to an Amazon FSx for Lustre file system with a data repository association.

    *)
  8. imported_file_chunk_size : megabytes option;
    (*

    For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system or cache.

    The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

    *)
  9. batch_import_meta_data_on_create : batch_import_meta_data_on_create option;
    (*

    A boolean flag indicating whether an import data repository task to import metadata should run after the data repository association is created. The task runs if this flag is set to true.

    BatchImportMetaDataOnCreate is not supported for data repositories linked to an Amazon File Cache resource.

    *)
  10. data_repository_path : archive_path option;
    (*

    The path to the data repository that will be linked to the cache or file system.

    • For Amazon File Cache, the path can be an NFS data repository that will be linked to the cache. The path can be in one of two formats:

      • If you are not using the DataRepositorySubdirectories parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format nsf://nfs-domain-name/exportpath. You can therefore link a single NFS Export to a single data repository association.
      • If you are using the DataRepositorySubdirectories parameter, the path is the domain name of the NFS file system in the format nfs://filer-domain-name, which indicates the root of the subdirectories specified with the DataRepositorySubdirectories parameter.
    • For Amazon File Cache, the path can be an S3 bucket or prefix in the format s3://bucket-name/prefix/ (where prefix is optional).
    • For Amazon FSx for Lustre, the path can be an S3 bucket or prefix in the format s3://bucket-name/prefix/ (where prefix is optional).
    *)
  11. file_system_path : namespace option;
    (*

    A path on the Amazon FSx for Lustre file system that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the name is required. Two data repository associations cannot have overlapping file system paths. For example, if a data repository is associated with file system path /ns1/, then you cannot link another data repository with file system path /ns1/ns2.

    This path specifies where in your file system files will be exported from or imported to. This file system directory can be linked to only one Amazon S3 bucket, and no other S3 bucket can be linked to the directory.

    If you specify only a forward slash (/) as the file system path, you can link only one data repository to the file system. You can only specify "/" as the file system path for the first data repository associated with a file system.

    *)
  12. failure_details : data_repository_failure_details option;
  13. lifecycle : data_repository_lifecycle option;
    (*

    Describes the state of a data repository association. The lifecycle can have the following values:

    • CREATING - The data repository association between the file system or cache and the data repository is being created. The data repository is unavailable.
    • AVAILABLE - The data repository association is available for use.
    • MISCONFIGURED - The data repository association is misconfigured. Until the configuration is corrected, automatic import and automatic export will not work (only for Amazon FSx for Lustre).
    • UPDATING - The data repository association is undergoing a customer initiated update that might affect its availability.
    • DELETING - The data repository association is undergoing a customer initiated deletion.
    • FAILED - The data repository association is in a terminal state that cannot be recovered.
    *)
  14. file_system_id : file_system_id option;
  15. resource_ar_n : resource_ar_n option;
  16. association_id : data_repository_association_id option;
    (*

    The system-generated, unique ID of the data repository association.

    *)
}

The configuration of a data repository association that links an Amazon FSx for Lustre file system to an Amazon S3 bucket or an Amazon File Cache resource to an Amazon S3 bucket or an NFS file system. The data repository association configuration object is returned in the response of the following operations:

  • CreateDataRepositoryAssociation
  • UpdateDataRepositoryAssociation
  • DescribeDataRepositoryAssociations

Data repository associations are supported on Amazon File Cache resources and all FSx for Lustre 2.12 and 2.15 file systems, excluding Intelligent-Tiering and scratch_1 file systems.

type nonrec update_data_repository_association_response = {
  1. association : data_repository_association option;
    (*

    The response object returned after the data repository association is updated.

    *)
}
type nonrec update_data_repository_association_request = {
  1. s3 : s3_data_repository_configuration option;
    (*

    The configuration for an Amazon S3 data repository linked to an Amazon FSx Lustre file system with a data repository association. The configuration defines which file events (new, changed, or deleted files or directories) are automatically imported from the linked data repository to the file system or automatically exported from the file system to the data repository.

    *)
  2. imported_file_chunk_size : megabytes option;
    (*

    For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

    The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

    *)
  3. client_request_token : client_request_token option;
  4. association_id : data_repository_association_id;
    (*

    The ID of the data repository association that you are updating.

    *)
}
type nonrec data_repository_association_not_found = {
  1. message : error_message option;
}

No data repository associations were found based upon the supplied parameters.

type nonrec untag_resource_response = unit
type nonrec tag_keys = tag_key list
type nonrec untag_resource_request = {
  1. tag_keys : tag_keys;
    (*

    A list of keys of tags on the resource to untag. In case the tag key doesn't exist, the call will still succeed to be idempotent.

    *)
  2. resource_ar_n : resource_ar_n;
    (*

    The ARN of the Amazon FSx resource to untag.

    *)
}

The request object for UntagResource action.

type nonrec resource_not_found = {
  1. message : error_message option;
  2. resource_ar_n : resource_ar_n;
    (*

    The resource ARN of the resource that can't be found.

    *)
}

The resource specified by the Amazon Resource Name (ARN) can't be found.

type nonrec resource_does_not_support_tagging = {
  1. message : error_message option;
  2. resource_ar_n : resource_ar_n;
    (*

    The Amazon Resource Name (ARN) of the resource that doesn't support tagging.

    *)
}

The resource specified does not support tagging.

type nonrec not_service_resource_error = {
  1. message : error_message option;
  2. resource_ar_n : resource_ar_n;
    (*

    The Amazon Resource Name (ARN) of the non-Amazon FSx resource.

    *)
}

The resource specified for the tagging operation is not a resource type owned by Amazon FSx. Use the API of the relevant service to perform the operation.

type nonrec unit_ =
  1. | DAYS
type nonrec total_count = Smaws_Lib.CoreTypes.Int64.t
type nonrec error_code = string
type nonrec too_many_access_points = {
  1. message : error_message option;
  2. error_code : error_code option;
    (*

    An error code indicating that you have reached the maximum number of S3 access points attachments allowed for your account in this Amazon Web Services Region, or for the file system.

    *)
}

You have reached the maximum number of S3 access points attachments allowed for your account in this Amazon Web Services Region, or for the file system. For more information, or to request an increase, see Service quotas on FSx resources in the FSx for OpenZFS User Guide.

type nonrec task_id = string
type nonrec task_ids = task_id list
type nonrec tag_resource_response = unit
type nonrec tag_resource_request = {
  1. tags : tags;
    (*

    A list of tags for the resource. If a tag with a given key already exists, the value is replaced by the one specified in this parameter.

    *)
  2. resource_ar_n : resource_ar_n;
    (*

    The Amazon Resource Name (ARN) of the Amazon FSx resource that you want to tag.

    *)
}

The request object for the TagResource operation.

type nonrec succeeded_count = Smaws_Lib.CoreTypes.Int64.t
type nonrec storage_virtual_machines = storage_virtual_machine list
type nonrec storage_virtual_machine_ids = storage_virtual_machine_id list
type nonrec storage_virtual_machine_filter_name =
  1. | FILE_SYSTEM_ID
type nonrec storage_virtual_machine_filter_value = string
type nonrec storage_virtual_machine_filter_values = storage_virtual_machine_filter_value list
type nonrec storage_virtual_machine_filter = {
  1. values : storage_virtual_machine_filter_values option;
    (*

    The values of the filter. These are all the values for any of the applied filters.

    *)
  2. name : storage_virtual_machine_filter_name option;
    (*

    The name for this filter.

    *)
}

A filter used to restrict the results of describe calls for Amazon FSx for NetApp ONTAP storage virtual machines (SVMs). You can use multiple filters to return results that meet all applied filter requirements.

type nonrec storage_virtual_machine_filters = storage_virtual_machine_filter list
type nonrec start_time = Smaws_Lib.CoreTypes.Timestamp.t
type nonrec start_misconfigured_state_recovery_response = {
  1. file_system : file_system option;
}
type nonrec start_misconfigured_state_recovery_request = {
  1. file_system_id : file_system_id;
  2. client_request_token : client_request_token option;
}
type nonrec backup_id = string
type nonrec source_backup_unavailable = {
  1. backup_id : backup_id option;
  2. message : error_message option;
}

The request was rejected because the lifecycle status of the source backup isn't AVAILABLE.

type nonrec source_backup_id = string
type nonrec snapshots = snapshot list
type nonrec snapshot_ids = snapshot_id list
type nonrec snapshot_filter_name =
  1. | VOLUME_ID
  2. | FILE_SYSTEM_ID
type nonrec snapshot_filter_value = string
type nonrec snapshot_filter_values = snapshot_filter_value list
type nonrec snapshot_filter = {
  1. values : snapshot_filter_values option;
    (*

    The file-system-id or volume-id that you are filtering for.

    *)
  2. name : snapshot_filter_name option;
    (*

    The name of the filter to use. You can filter by the file-system-id or by volume-id.

    *)
}

A filter used to restrict the results of DescribeSnapshots calls. You can use multiple filters to return results that meet all applied filter requirements.

type nonrec snapshot_filters = snapshot_filter list
type nonrec size_in_bytes = Smaws_Lib.CoreTypes.Int64.t
type nonrec self_managed_active_directory_configuration = {
  1. domain_join_service_account_secret : customer_secrets_manager_ar_n option;
    (*

    The Amazon Resource Name (ARN) of the Amazon Web Services Secrets Manager secret containing the self-managed Active Directory domain join service account credentials. When provided, Amazon FSx uses the credentials stored in this secret to join the file system to your self-managed Active Directory domain.

    The secret must contain two key-value pairs:

    • CUSTOMER_MANAGED_ACTIVE_DIRECTORY_USERNAME - The username for the service account
    • CUSTOMER_MANAGED_ACTIVE_DIRECTORY_PASSWORD - The password for the service account

    For more information, see Using Amazon FSx for Windows with your self-managed Microsoft Active Directory or Using Amazon FSx for ONTAP with your self-managed Microsoft Active Directory.

    *)
  2. dns_ips : dns_ips;
    (*

    A list of up to three IP addresses of DNS servers or domain controllers in the self-managed AD directory.

    *)
  3. password : directory_password option;
    (*

    The password for the service account on your self-managed AD domain that Amazon FSx will use to join to your AD domain.

    *)
  4. user_name : directory_user_name option;
    (*

    The user name for the service account on your self-managed AD domain that Amazon FSx will use to join to your AD domain. This account must have the permission to join computers to the domain in the organizational unit provided in OrganizationalUnitDistinguishedName, or in the default location of your AD domain.

    *)
  5. file_system_administrators_group : file_system_administrators_group_name option;
    (*

    (Optional) The name of the domain group whose members are granted administrative privileges for the file system. Administrative privileges include taking ownership of files and folders, setting audit controls (audit ACLs) on files and folders, and administering the file system remotely by using the FSx Remote PowerShell. The group that you specify must already exist in your domain. If you don't provide one, your AD domain's Domain Admins group is used.

    *)
  6. organizational_unit_distinguished_name : organizational_unit_distinguished_name option;
    (*

    (Optional) The fully qualified distinguished name of the organizational unit within your self-managed AD directory. Amazon FSx only accepts OU as the direct parent of the file system. An example is OU=FSx,DC=yourdomain,DC=corp,DC=com. To learn more, see RFC 2253. If none is provided, the FSx file system is created in the default location of your self-managed AD directory.

    Only Organizational Unit (OU) objects can be the direct parent of the file system that you're creating.

    *)
  7. domain_name : active_directory_fully_qualified_name;
    (*

    The fully qualified domain name of the self-managed AD directory, such as corp.example.com.

    *)
}

The configuration that Amazon FSx uses to join a FSx for Windows File Server file system or an FSx for ONTAP storage virtual machine (SVM) to a self-managed (including on-premises) Microsoft Active Directory (AD) directory. For more information, see Using Amazon FSx for Windows with your self-managed Microsoft Active Directory or Managing FSx for ONTAP SVMs.

type nonrec security_group_ids = security_group_id list
type nonrec s3_access_point_vpc_configuration = {
  1. vpc_id : vpc_id option;
    (*

    Specifies the virtual private cloud (VPC) for the S3 access point VPC configuration, if one exists.

    *)
}

If included, Amazon S3 restricts access to this access point to requests from the specified virtual private cloud (VPC).

type nonrec open_zfs_file_system_user_type =
  1. | POSIX
type nonrec file_system_ui_d = Smaws_Lib.CoreTypes.Int64.t
type nonrec file_system_gi_d = Smaws_Lib.CoreTypes.Int64.t
type nonrec file_system_secondary_gi_ds = file_system_gi_d list
type nonrec open_zfs_posix_file_system_user = {
  1. secondary_gids : file_system_secondary_gi_ds option;
    (*

    The list of secondary GIDs for the file system user.

    *)
  2. gid : file_system_gi_d;
    (*

    The GID of the file system user.

    *)
  3. uid : file_system_ui_d;
    (*

    The UID of the file system user.

    *)
}

The FSx for OpenZFS file system user that is used for authorizing all file access requests that are made using the S3 access point.

type nonrec open_zfs_file_system_identity = {
  1. posix_user : open_zfs_posix_file_system_user option;
    (*

    Specifies the UID and GIDs of the file system POSIX user.

    *)
  2. type_ : open_zfs_file_system_user_type;
    (*

    Specifies the FSx for OpenZFS user identity type, accepts only POSIX.

    *)
}

Specifies the file system user identity that will be used for authorizing all file access requests that are made using the S3 access point.

type nonrec s3_access_point_open_zfs_configuration = {
  1. file_system_identity : open_zfs_file_system_identity option;
    (*

    The file system identity used to authorize file access requests made using the S3 access point.

    *)
  2. volume_id : volume_id option;
    (*

    The ID of the FSx for OpenZFS volume that the S3 access point is attached to.

    *)
}

Describes the FSx for OpenZFS attachment configuration of an S3 access point attachment.

type nonrec ontap_file_system_user_type =
  1. | WINDOWS
  2. | UNIX
type nonrec ontap_file_system_user_name = string
type nonrec ontap_unix_file_system_user = {
  1. name : ontap_file_system_user_name;
    (*

    The name of the UNIX user. The name can be up to 256 characters long.

    *)
}

The FSx for ONTAP UNIX file system user that is used for authorizing all file access requests that are made using the S3 access point.

type nonrec ontap_windows_file_system_user = {
  1. name : ontap_file_system_user_name;
    (*

    The name of the Windows user. The name can be up to 256 characters long and supports Active Directory users.

    *)
}

The FSx for ONTAP Windows file system user that is used for authorizing all file access requests that are made using the S3 access point.

type nonrec ontap_file_system_identity = {
  1. windows_user : ontap_windows_file_system_user option;
    (*

    Specifies the Windows user identity for file system operations.

    *)
  2. unix_user : ontap_unix_file_system_user option;
    (*

    Specifies the UNIX user identity for file system operations.

    *)
  3. type_ : ontap_file_system_user_type;
    (*

    Specifies the FSx for ONTAP user identity type. Valid values are UNIX and WINDOWS.

    *)
}

Specifies the file system user identity that will be used for authorizing all file access requests that are made using the S3 access point. The identity can be either a UNIX user or a Windows user.

type nonrec s3_access_point_ontap_configuration = {
  1. file_system_identity : ontap_file_system_identity option;
    (*

    The file system identity used to authorize file access requests made using the S3 access point.

    *)
  2. volume_id : volume_id option;
    (*

    The ID of the FSx for ONTAP volume that the S3 access point is attached to.

    *)
}

Describes the FSx for ONTAP attachment configuration of an S3 access point attachment.

type nonrec s3_access_point_attachments_filter_name =
  1. | TYPE
  2. | VOLUME_ID
  3. | FILE_SYSTEM_ID
type nonrec s3_access_point_attachments_filter_value = string
type nonrec s3_access_point_attachments_filter_values = s3_access_point_attachments_filter_value list
type nonrec s3_access_point_attachments_filter = {
  1. values : s3_access_point_attachments_filter_values option;
    (*

    The values of the filter.

    *)
  2. name : s3_access_point_attachments_filter_name option;
    (*

    The name of the filter.

    *)
}

A set of Name and Values pairs used to view a select set of S3 access point attachments.

type nonrec s3_access_point_attachments_filters = s3_access_point_attachments_filter list
type nonrec s3_access_point_attachment_lifecycle =
  1. | MISCONFIGURED
  2. | FAILED
  3. | UPDATING
  4. | DELETING
  5. | CREATING
  6. | AVAILABLE
type nonrec s3_access_point_attachment_name = string
type nonrec s3_access_point_attachment_type =
  1. | ONTAP
  2. | OPENZFS
type nonrec s3_access_point_alias = string
type nonrec s3_access_point = {
  1. vpc_configuration : s3_access_point_vpc_configuration option;
    (*

    The S3 access point's virtual private cloud (VPC) configuration.

    *)
  2. alias : s3_access_point_alias option;
    (*

    The S3 access point's alias.

    *)
  3. resource_ar_n : general_ar_n option;
    (*

    he S3 access point's ARN.

    *)
}

Describes the S3 access point configuration of the S3 access point attachment.

type nonrec s3_access_point_attachment = {
  1. s3_access_point : s3_access_point option;
    (*

    The S3 access point configuration of the S3 access point attachment.

    *)
  2. ontap_configuration : s3_access_point_ontap_configuration option;
    (*

    The ONTAP configuration of the S3 access point attachment.

    *)
  3. open_zfs_configuration : s3_access_point_open_zfs_configuration option;
    (*

    The OpenZFSConfiguration of the S3 access point attachment.

    *)
  4. type_ : s3_access_point_attachment_type option;
    (*

    The type of Amazon FSx volume that the S3 access point is attached to.

    *)
  5. name : s3_access_point_attachment_name option;
    (*

    The name of the S3 access point attachment; also used for the name of the S3 access point.

    *)
  6. creation_time : creation_time option;
  7. lifecycle_transition_reason : lifecycle_transition_reason option;
  8. lifecycle : s3_access_point_attachment_lifecycle option;
    (*

    The lifecycle status of the S3 access point attachment. The lifecycle can have the following values:

    • AVAILABLE - the S3 access point attachment is available for use
    • CREATING - Amazon FSx is creating the S3 access point and attachment
    • DELETING - Amazon FSx is deleting the S3 access point and attachment
    • FAILED - The S3 access point attachment is in a failed state. Delete and detach the S3 access point attachment, and create a new one.
    • UPDATING - Amazon FSx is updating the S3 access point attachment
    *)
}

An S3 access point attached to an Amazon FSx volume.

type nonrec s3_access_point_attachments = s3_access_point_attachment list
type nonrec s3_access_point_attachment_not_found = {
  1. message : error_message option;
}

The access point specified was not found.

type nonrec s3_access_point_attachment_names = s3_access_point_attachment_name list
type nonrec restore_volume_from_snapshot_response = {
  1. administrative_actions : administrative_actions option;
    (*

    A list of administrative actions for the file system that are in process or waiting to be processed. Administrative actions describe changes to the Amazon FSx system.

    *)
  2. lifecycle : volume_lifecycle option;
    (*

    The lifecycle state of the volume being restored.

    *)
  3. volume_id : volume_id option;
    (*

    The ID of the volume that you restored.

    *)
}
type nonrec restore_open_zfs_volume_option =
  1. | DELETE_CLONED_VOLUMES
  2. | DELETE_INTERMEDIATE_SNAPSHOTS
type nonrec restore_open_zfs_volume_options = restore_open_zfs_volume_option list
type nonrec restore_volume_from_snapshot_request = {
  1. options : restore_open_zfs_volume_options option;
    (*

    The settings used when restoring the specified volume from snapshot.

    • DELETE_INTERMEDIATE_SNAPSHOTS - Deletes snapshots between the current state and the specified snapshot. If there are intermediate snapshots and this option isn't used, RestoreVolumeFromSnapshot fails.
    • DELETE_CLONED_VOLUMES - Deletes any dependent clone volumes created from intermediate snapshots. If there are any dependent clone volumes and this option isn't used, RestoreVolumeFromSnapshot fails.
    *)
  2. snapshot_id : snapshot_id;
    (*

    The ID of the source snapshot. Specifies the snapshot that you are restoring from.

    *)
  3. volume_id : volume_id;
    (*

    The ID of the volume that you are restoring.

    *)
  4. client_request_token : client_request_token option;
}
type nonrec resource_type =
  1. | VOLUME
  2. | FILE_SYSTEM
type nonrec report_scope =
  1. | FAILED_FILES_ONLY
type nonrec report_format =
  1. | REPORT_CSV_20191124
type nonrec released_capacity = Smaws_Lib.CoreTypes.Int64.t
type nonrec release_file_system_nfs_v3_locks_response = {
  1. file_system : file_system option;
}
type nonrec release_file_system_nfs_v3_locks_request = {
  1. client_request_token : client_request_token option;
  2. file_system_id : file_system_id;
}
type nonrec duration_since_last_access = {
  1. value : value option;
    (*

    An integer that represents the minimum amount of time (in days) since a file was last accessed in the file system. Only exported files with a MAX(atime, ctime, mtime) timestamp that is more than this amount of time in the past (relative to the task create time) will be released. The default of Value is 0. This is a required parameter.

    If an exported file meets the last accessed time criteria, its file or directory path must also be specified in the Paths parameter of the operation in order for the file to be released.

    *)
  2. unit_ : unit_ option;
    (*

    The unit of time used by the Value parameter to determine if a file can be released, based on when it was last accessed. DAYS is the only supported value. This is a required parameter.

    *)
}

Defines the minimum amount of time since last access for a file to be eligible for release. Only files that have been exported to S3 and that were last accessed or modified before this point-in-time are eligible to be released from the Amazon FSx for Lustre file system.

type nonrec release_configuration = {
  1. duration_since_last_access : duration_since_last_access option;
    (*

    Defines the point-in-time since an exported file was last accessed, in order for that file to be eligible for release. Only files that were last accessed before this point-in-time are eligible to be released from the file system.

    *)
}

The configuration that specifies a minimum amount of time since last access for an exported file to be eligible for release from an Amazon FSx for Lustre file system. Only files that were last accessed before this point-in-time can be released. For example, if you specify a last accessed time criteria of 9 days, only files that were last accessed 9.00001 or more days ago can be released.

Only file data that has been exported to S3 can be released. Files that have not yet been exported to S3, such as new or changed files that have not been exported, are not eligible for release. When files are released, their metadata stays on the file system, so they can still be accessed later. Users and applications can access a released file by reading the file again, which restores data from Amazon S3 to the FSx for Lustre file system.

If a file meets the last accessed time criteria, its file or directory path must also be specified with the Paths parameter of the operation in order for the file to be released.

type nonrec region = string
type nonrec open_zfs_create_root_volume_configuration = {
  1. read_only : read_only option;
    (*

    A Boolean value indicating whether the volume is read-only. Setting this value to true can be useful after you have completed changes to a volume and no longer want changes to occur.

    *)
  2. copy_tags_to_snapshots : flag option;
    (*

    A Boolean value indicating whether tags for the volume should be copied to snapshots of the volume. This value defaults to false. If it's set to true, all tags for the volume are copied to snapshots where the user doesn't specify tags. If this value is true and you specify one or more tags, only the specified tags are copied to snapshots. If you specify one or more tags when creating the snapshot, no tags are copied from the volume, regardless of this value.

    *)
  3. user_and_group_quotas : open_zfs_user_and_group_quotas option;
    (*

    An object specifying how much storage users or groups can use on the volume.

    *)
  4. nfs_exports : open_zfs_nfs_exports option;
    (*

    The configuration object for mounting a file system.

    *)
  5. data_compression_type : open_zfs_data_compression_type option;
    (*

    Specifies the method used to compress the data on the volume. The compression type is NONE by default.

    • NONE - Doesn't compress the data on the volume. NONE is the default.
    • ZSTD - Compresses the data in the volume using the Zstandard (ZSTD) compression algorithm. Compared to LZ4, Z-Standard provides a better compression ratio to minimize on-disk storage utilization.
    • LZ4 - Compresses the data in the volume using the LZ4 compression algorithm. Compared to Z-Standard, LZ4 is less compute-intensive and delivers higher write throughput speeds.
    *)
  6. record_size_ki_b : integer_record_size_ki_b option;
    (*

    Specifies the record size of an OpenZFS root volume, in kibibytes (KiB). Valid values are 4, 8, 16, 32, 64, 128, 256, 512, or 1024 KiB. The default is 128 KiB. Most workloads should use the default record size. Database workflows can benefit from a smaller record size, while streaming workflows can benefit from a larger record size. For additional guidance on setting a custom record size, see Tips for maximizing performance in the Amazon FSx for OpenZFS User Guide.

    *)
}

The configuration of an Amazon FSx for OpenZFS root volume.

type nonrec next_token = string
type nonrec max_results = int
type nonrec list_tags_for_resource_response = {
  1. next_token : next_token option;
    (*

    This is present if there are more tags than returned in the response (String). You can use the NextToken value in the later request to fetch the tags.

    *)
  2. tags : tags option;
    (*

    A list of tags on the resource.

    *)
}

The response object for ListTagsForResource operation.

type nonrec list_tags_for_resource_request = {
  1. next_token : next_token option;
    (*

    Opaque pagination token returned from a previous ListTagsForResource operation (String). If a token present, the action continues the list from where the returning call left off.

    *)
  2. max_results : max_results option;
    (*

    Maximum number of tags to return in the response (integer). This parameter value must be greater than 0. The number of items that Amazon FSx returns is the minimum of the MaxResults parameter specified in the request and the service's internal maximum number of items per page.

    *)
  3. resource_ar_n : resource_ar_n;
    (*

    The ARN of the Amazon FSx resource that will have its tags listed.

    *)
}

The request object for ListTagsForResource operation.

type nonrec limited_max_results = int
type nonrec last_updated_time = Smaws_Lib.CoreTypes.Timestamp.t
type nonrec invalid_source_kms_key = {
  1. message : error_message option;
}

The Key Management Service (KMS) key of the source backup is not valid.

type nonrec invalid_request = {
  1. message : error_message option;
  2. error_code : error_code option;
    (*

    An error code indicating that the action or operation requested is invalid.

    *)
}

The action or operation requested is invalid. Verify that the action is typed correctly.

type nonrec invalid_region = {
  1. message : error_message option;
}

The Region provided for SourceRegion is not valid or is in a different Amazon Web Services partition.

type nonrec invalid_per_unit_storage_throughput = {
  1. message : error_message option;
}

An invalid value for PerUnitStorageThroughput was provided. Please create your file system again, using a valid value.

type nonrec invalid_import_path = {
  1. message : error_message option;
}

The path provided for data repository import isn't valid.

type nonrec invalid_export_path = {
  1. message : error_message option;
}

The path provided for data repository export isn't valid.

type nonrec invalid_destination_kms_key = {
  1. message : error_message option;
}

The Key Management Service (KMS) key of the destination backup is not valid.

type nonrec invalid_data_repository_type = {
  1. message : error_message option;
}

You have filtered the response to a data repository type that is not supported.

type nonrec invalid_access_point = {
  1. message : error_message option;
  2. error_code : error_code option;
    (*

    An error code indicating that the access point specified doesn't exist.

    *)
}

The access point specified doesn't exist.

type nonrec input_ontap_volume_type =
  1. | DP
  2. | RW
type nonrec incompatible_region_for_multi_a_z = {
  1. message : error_message option;
}

Amazon FSx doesn't support Multi-AZ Windows File Server copy backup in the destination Region, so the copied backup can't be restored.

type nonrec include_shared = bool
type nonrec filter_name =
  1. | FILE_CACHE_TYPE
  2. | FILE_CACHE_ID
  3. | DATA_REPOSITORY_TYPE
  4. | VOLUME_ID
  5. | FILE_SYSTEM_TYPE
  6. | BACKUP_TYPE
  7. | FILE_SYSTEM_ID

The name for a filter.

type nonrec filter_value = string
type nonrec filter_values = filter_value list
type nonrec filter = {
  1. values : filter_values option;
    (*

    The values of the filter. These are all the values for any of the applied filters.

    *)
  2. name : filter_name option;
    (*

    The name for this filter.

    *)
}

A filter used to restrict the results of describe calls. You can use multiple filters to return results that meet all applied filter requirements.

type nonrec filters = filter list
type nonrec file_systems = file_system list
type nonrec file_system_ids = file_system_id list
type nonrec file_caches = file_cache list
type nonrec file_cache_nfs_configuration = {
  1. dns_ips : repository_dns_ips option;
    (*

    A list of up to 2 IP addresses of DNS servers used to resolve the NFS file system domain name. The provided IP addresses can either be the IP addresses of a DNS forwarder or resolver that the customer manages and runs inside the customer VPC, or the IP addresses of the on-premises DNS servers.

    *)
  2. version : nfs_version;
    (*

    The version of the NFS (Network File System) protocol of the NFS data repository. The only supported value is NFS3, which indicates that the data repository must support the NFSv3 protocol.

    *)
}

The configuration for an NFS data repository association (DRA) created during the creation of the Amazon File Cache resource.

type nonrec file_cache_ids = file_cache_id list
type nonrec file_cache_data_repository_association = {
  1. nf_s : file_cache_nfs_configuration option;
    (*

    The configuration for a data repository association that links an Amazon File Cache resource to an NFS data repository.

    *)
  2. data_repository_subdirectories : sub_directories_paths option;
    (*

    A list of NFS Exports that will be linked with this data repository association. The Export paths are in the format /exportpath1. To use this parameter, you must configure DataRepositoryPath as the domain name of the NFS file system. The NFS file system domain name in effect is the root of the subdirectories. Note that DataRepositorySubdirectories is not supported for S3 data repositories.

    *)
  3. data_repository_path : archive_path;
    (*

    The path to the S3 or NFS data repository that links to the cache. You must provide one of the following paths:

    • The path can be an NFS data repository that links to the cache. The path can be in one of two formats:

      • If you are not using the DataRepositorySubdirectories parameter, the path is to an NFS Export directory (or one of its subdirectories) in the format nfs://nfs-domain-name/exportpath. You can therefore link a single NFS Export to a single data repository association.
      • If you are using the DataRepositorySubdirectories parameter, the path is the domain name of the NFS file system in the format nfs://filer-domain-name, which indicates the root of the subdirectories specified with the DataRepositorySubdirectories parameter.
    • The path can be an S3 bucket or prefix in the format s3://bucket-name/prefix/ (where prefix is optional).
    *)
  4. file_cache_path : namespace;
    (*

    A path on the cache that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the name is required. Two data repository associations cannot have overlapping cache paths. For example, if a data repository is associated with cache path /ns1/, then you cannot link another data repository with cache path /ns1/ns2.

    This path specifies where in your cache files will be exported from. This cache directory can be linked to only one data repository, and no data repository other can be linked to the directory.

    The cache path can only be set to root (/) on an NFS DRA when DataRepositorySubdirectories is specified. If you specify root (/) as the cache path, you can create only one DRA on the cache.

    The cache path cannot be set to root (/) for an S3 DRA.

    *)
}

The configuration for a data repository association (DRA) to be created during the Amazon File Cache resource creation. The DRA links the cache to either an Amazon S3 bucket or prefix, or a Network File System (NFS) data repository that supports the NFSv3 protocol.

The DRA does not support automatic import or automatic export.

type nonrec copy_tags_to_data_repository_associations = bool
type nonrec file_cache_creating = {
  1. data_repository_association_ids : data_repository_association_ids option;
    (*

    A list of IDs of data repository associations that are associated with this cache.

    *)
  2. lustre_configuration : file_cache_lustre_configuration option;
    (*

    The configuration for the Amazon File Cache resource.

    *)
  3. copy_tags_to_data_repository_associations : copy_tags_to_data_repository_associations option;
    (*

    A boolean flag indicating whether tags for the cache should be copied to data repository associations.

    *)
  4. tags : tags option;
  5. resource_ar_n : resource_ar_n option;
  6. kms_key_id : kms_key_id option;
    (*

    Specifies the ID of the Key Management Service (KMS) key to use for encrypting data on an Amazon File Cache. If a KmsKeyId isn't specified, the Amazon FSx-managed KMS key for your account is used. For more information, see Encrypt in the Key Management Service API Reference.

    *)
  7. dns_name : dns_name option;
    (*

    The Domain Name System (DNS) name for the cache.

    *)
  8. network_interface_ids : network_interface_ids option;
  9. subnet_ids : subnet_ids option;
  10. vpc_id : vpc_id option;
  11. storage_capacity : storage_capacity option;
    (*

    The storage capacity of the cache in gibibytes (GiB).

    *)
  12. failure_details : file_cache_failure_details option;
    (*

    A structure providing details of any failures that occurred in creating a cache.

    *)
  13. lifecycle : file_cache_lifecycle option;
    (*

    The lifecycle status of the cache. The following are the possible values and what they mean:

    • AVAILABLE - The cache is in a healthy state, and is reachable and available for use.
    • CREATING - The new cache is being created.
    • DELETING - An existing cache is being deleted.
    • UPDATING - The cache is undergoing a customer-initiated update.
    • FAILED - An existing cache has experienced an unrecoverable failure. When creating a new cache, the cache was unable to be created.
    *)
  14. file_cache_type_version : file_system_type_version option;
    (*

    The Lustre version of the cache, which must be 2.12.

    *)
  15. file_cache_type : file_cache_type option;
    (*

    The type of cache, which must be LUSTRE.

    *)
  16. file_cache_id : file_cache_id option;
    (*

    The system-generated, unique ID of the cache.

    *)
  17. creation_time : creation_time option;
  18. owner_id : aws_account_id option;
}

The response object for the Amazon File Cache resource being created in the CreateFileCache operation.

type nonrec failed_count = Smaws_Lib.CoreTypes.Int64.t
type nonrec end_time = Smaws_Lib.CoreTypes.Timestamp.t
type nonrec disassociate_file_system_aliases_response = {
  1. aliases : aliases option;
    (*

    An array of one or more DNS aliases that Amazon FSx is attempting to disassociate from the file system.

    *)
}

The system generated response showing the DNS aliases that Amazon FSx is attempting to disassociate from the file system. Use the API operation to monitor the status of the aliases Amazon FSx is removing from the file system.

type nonrec alternate_dns_names = alternate_dns_name list
type nonrec disassociate_file_system_aliases_request = {
  1. aliases : alternate_dns_names;
    (*

    An array of one or more DNS alias names to disassociate, or remove, from the file system.

    *)
  2. file_system_id : file_system_id;
    (*

    Specifies the file system from which to disassociate the DNS aliases.

    *)
  3. client_request_token : client_request_token option;
}

The request object of DNS aliases to disassociate from an Amazon FSx for Windows File Server file system.

type nonrec detach_and_delete_s3_access_point_response = {
  1. name : s3_access_point_attachment_name option;
    (*

    The name of the S3 access point attachment being deleted.

    *)
  2. lifecycle : s3_access_point_attachment_lifecycle option;
    (*

    The lifecycle status of the S3 access point attachment.

    *)
}
type nonrec detach_and_delete_s3_access_point_request = {
  1. name : s3_access_point_attachment_name;
    (*

    The name of the S3 access point attachment that you want to delete.

    *)
  2. client_request_token : client_request_token option;
}
type nonrec describe_volumes_response = {
  1. next_token : next_token option;
  2. volumes : volumes option;
    (*

    Returned after a successful DescribeVolumes operation, describing each volume.

    *)
}
type nonrec describe_volumes_request = {
  1. next_token : next_token option;
  2. max_results : max_results option;
  3. filters : volume_filters option;
    (*

    Enter a filter Name and Values pair to view a select set of volumes.

    *)
  4. volume_ids : volume_ids option;
    (*

    The IDs of the volumes whose descriptions you want to retrieve.

    *)
}
type nonrec describe_storage_virtual_machines_response = {
  1. next_token : next_token option;
  2. storage_virtual_machines : storage_virtual_machines option;
    (*

    Returned after a successful DescribeStorageVirtualMachines operation, describing each SVM.

    *)
}
type nonrec describe_storage_virtual_machines_request = {
  1. next_token : next_token option;
  2. max_results : max_results option;
  3. filters : storage_virtual_machine_filters option;
    (*

    Enter a filter name:value pair to view a select set of SVMs.

    *)
  4. storage_virtual_machine_ids : storage_virtual_machine_ids option;
    (*

    Enter the ID of one or more SVMs that you want to view.

    *)
}
type nonrec describe_snapshots_response = {
  1. next_token : next_token option;
  2. snapshots : snapshots option;
    (*

    An array of snapshots.

    *)
}
type nonrec describe_snapshots_request = {
  1. include_shared : include_shared option;
    (*

    Set to false (default) if you want to only see the snapshots owned by your Amazon Web Services account. Set to true if you want to see the snapshots in your account and the ones shared with you from another account.

    *)
  2. next_token : next_token option;
  3. max_results : max_results option;
  4. filters : snapshot_filters option;
    (*

    The filters structure. The supported names are file-system-id or volume-id.

    *)
  5. snapshot_ids : snapshot_ids option;
    (*

    The IDs of the snapshots that you want to retrieve. This parameter value overrides any filters. If any IDs aren't found, a SnapshotNotFound error occurs.

    *)
}
type nonrec describe_shared_vpc_configuration_response = {
  1. enable_fsx_route_table_updates_from_participant_accounts : verbose_flag option;
    (*

    Indicates whether participant accounts can create FSx for ONTAP Multi-AZ file systems in shared subnets.

    *)
}
type nonrec describe_shared_vpc_configuration_request = unit
type nonrec describe_s3_access_point_attachments_response = {
  1. next_token : next_token option;
  2. s3_access_point_attachments : s3_access_point_attachments option;
    (*

    Array of S3 access point attachments returned after a successful DescribeS3AccessPointAttachments operation.

    *)
}
type nonrec describe_s3_access_point_attachments_request = {
  1. next_token : next_token option;
  2. max_results : max_results option;
  3. filters : s3_access_point_attachments_filters option;
    (*

    Enter a filter Name and Values pair to view a select set of S3 access point attachments.

    *)
  4. names : s3_access_point_attachment_names option;
    (*

    The names of the S3 access point attachments whose descriptions you want to retrieve.

    *)
}
type nonrec describe_file_systems_response = {
  1. next_token : next_token option;
    (*

    Present if there are more file systems than returned in the response (String). You can use the NextToken value in the later request to fetch the descriptions.

    *)
  2. file_systems : file_systems option;
    (*

    An array of file system descriptions.

    *)
}

The response object for DescribeFileSystems operation.

type nonrec describe_file_systems_request = {
  1. next_token : next_token option;
    (*

    Opaque pagination token returned from a previous DescribeFileSystems operation (String). If a token present, the operation continues the list from where the returning call left off.

    *)
  2. max_results : max_results option;
    (*

    Maximum number of file systems to return in the response (integer). This parameter value must be greater than 0. The number of items that Amazon FSx returns is the minimum of the MaxResults parameter specified in the request and the service's internal maximum number of items per page.

    *)
  3. file_system_ids : file_system_ids option;
    (*

    IDs of the file systems whose descriptions you want to retrieve (String).

    *)
}

The request object for DescribeFileSystems operation.

type nonrec describe_file_system_aliases_response = {
  1. next_token : next_token option;
    (*

    Present if there are more DNS aliases than returned in the response (String). You can use the NextToken value in a later request to fetch additional descriptions.

    *)
  2. aliases : aliases option;
    (*

    An array of one or more DNS aliases currently associated with the specified file system.

    *)
}

The response object for DescribeFileSystemAliases operation.

type nonrec describe_file_system_aliases_request = {
  1. next_token : next_token option;
    (*

    Opaque pagination token returned from a previous DescribeFileSystemAliases operation (String). If a token is included in the request, the action continues the list from where the previous returning call left off.

    *)
  2. max_results : max_results option;
    (*

    Maximum number of DNS aliases to return in the response (integer). This parameter value must be greater than 0. The number of items that Amazon FSx returns is the minimum of the MaxResults parameter specified in the request and the service's internal maximum number of items per page.

    *)
  3. file_system_id : file_system_id;
    (*

    The ID of the file system to return the associated DNS aliases for (String).

    *)
  4. client_request_token : client_request_token option;
}

The request object for DescribeFileSystemAliases operation.

type nonrec describe_file_caches_response = {
  1. next_token : next_token option;
  2. file_caches : file_caches option;
    (*

    The response object for the DescribeFileCaches operation.

    *)
}
type nonrec describe_file_caches_request = {
  1. next_token : next_token option;
  2. max_results : max_results option;
  3. file_cache_ids : file_cache_ids option;
    (*

    IDs of the caches whose descriptions you want to retrieve (String).

    *)
}
type nonrec data_repository_task_lifecycle =
  1. | CANCELING
  2. | CANCELED
  3. | SUCCEEDED
  4. | FAILED
  5. | EXECUTING
  6. | PENDING
type nonrec data_repository_task_type =
  1. | AUTO_TRIGGERED_EVICTION
  2. | EVICTION
  3. | IMPORT
  4. | EXPORT
type nonrec data_repository_task_path = string
type nonrec data_repository_task_paths = data_repository_task_path list
type nonrec data_repository_task_failure_details = {
  1. message : error_message option;
}

Provides information about why a data repository task failed. Only populated when the task Lifecycle is set to FAILED.

type nonrec data_repository_task_status = {
  1. released_capacity : released_capacity option;
    (*

    The total amount of data, in GiB, released by an Amazon File Cache AUTO_RELEASE_DATA task that automatically releases files from the cache.

    *)
  2. last_updated_time : last_updated_time option;
    (*

    The time at which the task status was last updated.

    *)
  3. failed_count : failed_count option;
    (*

    A running total of the number of files that the task failed to process.

    *)
  4. succeeded_count : succeeded_count option;
    (*

    A running total of the number of files that the task has successfully processed.

    *)
  5. total_count : total_count option;
    (*

    The total number of files that the task will process. While a task is executing, the sum of SucceededCount plus FailedCount may not equal TotalCount. When the task is complete, TotalCount equals the sum of SucceededCount plus FailedCount.

    *)
}

Provides the task status showing a running total of the total number of files to be processed, the number successfully processed, and the number of files the task failed to process.

type nonrec completion_report = {
  1. scope : report_scope option;
    (*

    Required if Enabled is set to true. Specifies the scope of the CompletionReport; FAILED_FILES_ONLY is the only scope currently supported. When Scope is set to FAILED_FILES_ONLY, the CompletionReport only contains information about files that the data repository task failed to process.

    *)
  2. format : report_format option;
    (*

    Required if Enabled is set to true. Specifies the format of the CompletionReport. REPORT_CSV_20191124 is the only format currently supported. When Format is set to REPORT_CSV_20191124, the CompletionReport is provided in CSV format, and is delivered to {path}/task-{id}/failures.csv.

    *)
  3. path : archive_path option;
    (*

    Required if Enabled is set to true. Specifies the location of the report on the file system's linked S3 data repository. An absolute path that defines where the completion report will be stored in the destination location. The Path you provide must be located within the file system’s ExportPath. An example Path value is "s3://amzn-s3-demo-bucket/myExportPath/optionalPrefix". The report provides the following information for each file in the report: FilePath, FileStatus, and ErrorCode.

    *)
  4. enabled : flag;
    (*

    Set Enabled to True to generate a CompletionReport when the task completes. If set to true, then you need to provide a report Scope, Path, and Format. Set Enabled to False if you do not want a CompletionReport generated when the task completes.

    *)
}

Provides a report detailing the data repository task results of the files processed that match the criteria specified in the report Scope parameter. FSx delivers the report to the file system's linked data repository in Amazon S3, using the path specified in the report Path parameter. You can specify whether or not a report gets generated for a task using the Enabled parameter.

type nonrec capacity_to_release = Smaws_Lib.CoreTypes.Int64.t
type nonrec data_repository_task = {
  1. release_configuration : release_configuration option;
    (*

    The configuration that specifies the last accessed time criteria for files that will be released from an Amazon FSx for Lustre file system.

    *)
  2. file_cache_id : file_cache_id option;
    (*

    The system-generated, unique ID of the cache.

    *)
  3. capacity_to_release : capacity_to_release option;
    (*

    Specifies the amount of data to release, in GiB, by an Amazon File Cache AUTO_RELEASE_DATA task that automatically releases files from the cache.

    *)
  4. report : completion_report option;
  5. status : data_repository_task_status option;
    (*

    Provides the status of the number of files that the task has processed successfully and failed to process.

    *)
  6. failure_details : data_repository_task_failure_details option;
    (*

    Failure message describing why the task failed, it is populated only when Lifecycle is set to FAILED.

    *)
  7. paths : data_repository_task_paths option;
    (*

    An array of paths that specify the data for the data repository task to process. For example, in an EXPORT_TO_REPOSITORY task, the paths specify which data to export to the linked data repository.

    (Default) If Paths is not specified, Amazon FSx uses the file system root directory.

    *)
  8. file_system_id : file_system_id option;
    (*

    The globally unique ID of the file system.

    *)
  9. tags : tags option;
  10. resource_ar_n : resource_ar_n option;
  11. end_time : end_time option;
    (*

    The time the system completed processing the task, populated after the task is complete.

    *)
  12. start_time : start_time option;
    (*

    The time the system began processing the task.

    *)
  13. creation_time : creation_time;
  14. type_ : data_repository_task_type;
    (*

    The type of data repository task.

    • EXPORT_TO_REPOSITORY tasks export from your Amazon FSx for Lustre file system to a linked data repository.
    • IMPORT_METADATA_FROM_REPOSITORY tasks import metadata changes from a linked S3 bucket to your Amazon FSx for Lustre file system.
    • RELEASE_DATA_FROM_FILESYSTEM tasks release files in your Amazon FSx for Lustre file system that have been exported to a linked S3 bucket and that meet your specified release criteria.
    • AUTO_RELEASE_DATA tasks automatically release files from an Amazon File Cache resource.
    *)
  15. lifecycle : data_repository_task_lifecycle;
    (*

    The lifecycle status of the data repository task, as follows:

    • PENDING - The task has not started.
    • EXECUTING - The task is in process.
    • FAILED - The task was not able to be completed. For example, there may be files the task failed to process. The DataRepositoryTaskFailureDetails property provides more information about task failures.
    • SUCCEEDED - The task has completed successfully.
    • CANCELED - The task was canceled and it did not complete.
    • CANCELING - The task is in process of being canceled.

    You cannot delete an FSx for Lustre file system if there are data repository tasks for the file system in the PENDING or EXECUTING states. Please retry when the data repository task is finished (with a status of CANCELED, SUCCEEDED, or FAILED). You can use the DescribeDataRepositoryTask action to monitor the task status. Contact the FSx team if you need to delete your file system immediately.

    *)
  16. task_id : task_id;
    (*

    The system-generated, unique 17-digit ID of the data repository task.

    *)
}

A description of the data repository task.

  • You use import and export data repository tasks to perform bulk transfer operations between an Amazon FSx for Lustre file system and a linked data repository.
  • You use release data repository tasks to release files that have been exported to a linked S3 bucket from your Amazon FSx for Lustre file system.
  • An Amazon File Cache resource uses a task to automatically release files from the cache.

To learn more about data repository tasks, see Data Repository Tasks.

type nonrec data_repository_tasks = data_repository_task list
type nonrec describe_data_repository_tasks_response = {
  1. next_token : next_token option;
  2. data_repository_tasks : data_repository_tasks option;
    (*

    The collection of data repository task descriptions returned.

    *)
}
type nonrec data_repository_task_filter_name =
  1. | FILE_CACHE_ID
  2. | DATA_REPO_ASSOCIATION_ID
  3. | TASK_LIFECYCLE
  4. | FILE_SYSTEM_ID
type nonrec data_repository_task_filter_value = string
type nonrec data_repository_task_filter_values = data_repository_task_filter_value list
type nonrec data_repository_task_filter = {
  1. values : data_repository_task_filter_values option;
    (*

    Use Values to include the specific file system IDs and task lifecycle states for the filters you are using.

    *)
  2. name : data_repository_task_filter_name option;
    (*

    Name of the task property to use in filtering the tasks returned in the response.

    • Use file-system-id to retrieve data repository tasks for specific file systems.
    • Use task-lifecycle to retrieve data repository tasks with one or more specific lifecycle states, as follows: CANCELED, EXECUTING, FAILED, PENDING, and SUCCEEDED.
    *)
}

(Optional) An array of filter objects you can use to filter the response of data repository tasks you will see in the response. You can filter the tasks returned in the response by one or more file system IDs, task lifecycles, and by task type. A filter object consists of a filter Name, and one or more Values for the filter.

type nonrec data_repository_task_filters = data_repository_task_filter list
type nonrec describe_data_repository_tasks_request = {
  1. next_token : next_token option;
  2. max_results : max_results option;
  3. filters : data_repository_task_filters option;
    (*

    (Optional) You can use filters to narrow the DescribeDataRepositoryTasks response to include just tasks for specific file systems, or tasks in a specific lifecycle state.

    *)
  4. task_ids : task_ids option;
    (*

    (Optional) IDs of the tasks whose descriptions you want to retrieve (String).

    *)
}
type nonrec data_repository_task_not_found = {
  1. message : error_message option;
}

The data repository task or tasks you specified could not be found.

type nonrec data_repository_associations = data_repository_association list
type nonrec describe_data_repository_associations_response = {
  1. next_token : next_token option;
  2. associations : data_repository_associations option;
    (*

    An array of one or more data repository association descriptions.

    *)
}
type nonrec describe_data_repository_associations_request = {
  1. next_token : next_token option;
  2. max_results : limited_max_results option;
    (*

    The maximum number of resources to return in the response. This value must be an integer greater than zero.

    *)
  3. filters : filters option;
  4. association_ids : data_repository_association_ids option;
    (*

    IDs of the data repository associations whose descriptions you want to retrieve (String).

    *)
}
type nonrec backup_lifecycle =
  1. | COPYING
  2. | PENDING
  3. | FAILED
  4. | DELETED
  5. | TRANSFERRING
  6. | CREATING
  7. | AVAILABLE

The lifecycle status of the backup.

  • AVAILABLE - The backup is fully available.
  • PENDING - For user-initiated backups on Lustre file systems only; Amazon FSx hasn't started creating the backup.
  • CREATING - Amazon FSx is creating the new user-initiated backup.
  • TRANSFERRING - For user-initiated backups on Lustre file systems only; Amazon FSx is backing up the file system.
  • COPYING - Amazon FSx is copying the backup.
  • DELETED - Amazon FSx deleted the backup and it's no longer available.
  • FAILED - Amazon FSx couldn't finish the backup.
type nonrec backup_failure_details = {
  1. message : error_message option;
    (*

    A message describing the backup-creation failure.

    *)
}

If backup creation fails, this structure contains the details of that failure.

type nonrec backup_type =
  1. | AWS_BACKUP
  2. | USER_INITIATED
  3. | AUTOMATIC

The type of the backup.

type nonrec active_directory_backup_attributes = {
  1. resource_ar_n : resource_ar_n option;
  2. active_directory_id : directory_id option;
    (*

    The ID of the Amazon Web Services Managed Microsoft Active Directory instance to which the file system is joined.

    *)
  3. domain_name : active_directory_fully_qualified_name option;
    (*

    The fully qualified domain name of the self-managed Active Directory directory.

    *)
}

The Microsoft Active Directory attributes of the Amazon FSx for Windows File Server file system.

type nonrec backup = {
  1. size_in_bytes : size_in_bytes option;
    (*

    The size of the backup in bytes. This represents the amount of data that the file system would contain if you restore this backup.

    *)
  2. volume : volume option;
  3. resource_type : resource_type option;
    (*

    Specifies the resource type that's backed up.

    *)
  4. source_backup_region : region option;
    (*

    The source Region of the backup. Specifies the Region from where this backup is copied.

    *)
  5. source_backup_id : backup_id option;
  6. owner_id : aws_account_id option;
  7. directory_information : active_directory_backup_attributes option;
    (*

    The configuration of the self-managed Microsoft Active Directory directory to which the Windows File Server instance is joined.

    *)
  8. file_system : file_system;
    (*

    The metadata of the file system associated with the backup. This metadata is persisted even if the file system is deleted.

    *)
  9. tags : tags option;
    (*

    The tags associated with a particular file system.

    *)
  10. resource_ar_n : resource_ar_n option;
    (*

    The Amazon Resource Name (ARN) for the backup resource.

    *)
  11. kms_key_id : kms_key_id option;
    (*

    The ID of the Key Management Service (KMS) key used to encrypt the backup of the Amazon FSx file system's data at rest.

    *)
  12. creation_time : creation_time;
    (*

    The time when a particular backup was created.

    *)
  13. progress_percent : progress_percent option;
  14. type_ : backup_type;
    (*

    The type of the file-system backup.

    *)
  15. failure_details : backup_failure_details option;
    (*

    Details explaining any failures that occurred when creating a backup.

    *)
  16. lifecycle : backup_lifecycle;
    (*

    The lifecycle status of the backup.

    • AVAILABLE - The backup is fully available.
    • PENDING - For user-initiated backups on Lustre file systems only; Amazon FSx hasn't started creating the backup.
    • CREATING - Amazon FSx is creating the backup.
    • TRANSFERRING - For user-initiated backups on Lustre file systems only; Amazon FSx is transferring the backup to Amazon S3.
    • COPYING - Amazon FSx is copying the backup.
    • DELETED - Amazon FSx deleted the backup and it's no longer available.
    • FAILED - Amazon FSx couldn't finish the backup.
    *)
  17. backup_id : backup_id;
    (*

    The ID of the backup.

    *)
}

A backup of an Amazon FSx for Windows File Server, Amazon FSx for Lustre file system, Amazon FSx for NetApp ONTAP volume, or Amazon FSx for OpenZFS file system.

type nonrec backups = backup list
type nonrec describe_backups_response = {
  1. next_token : next_token option;
    (*

    A NextToken value is present if there are more backups than returned in the response. You can use the NextToken value in the subsequent request to fetch the backups.

    *)
  2. backups : backups option;
    (*

    An array of backups.

    *)
}

Response object for the DescribeBackups operation.

type nonrec backup_ids = backup_id list
type nonrec describe_backups_request = {
  1. next_token : next_token option;
    (*

    An opaque pagination token returned from a previous DescribeBackups operation. If a token is present, the operation continues the list from where the returning call left off.

    *)
  2. max_results : max_results option;
    (*

    Maximum number of backups to return in the response. This parameter value must be greater than 0. The number of items that Amazon FSx returns is the minimum of the MaxResults parameter specified in the request and the service's internal maximum number of items per page.

    *)
  3. filters : filters option;
    (*

    The filters structure. The supported names are file-system-id, backup-type, file-system-type, and volume-id.

    *)
  4. backup_ids : backup_ids option;
    (*

    The IDs of the backups that you want to retrieve. This parameter value overrides any filters. If any IDs aren't found, a BackupNotFound error occurs.

    *)
}

The request object for the DescribeBackups operation.

type nonrec backup_not_found = {
  1. message : error_message option;
}

No Amazon FSx backups were found based upon the supplied parameters.

type nonrec delete_volume_ontap_response = {
  1. final_backup_tags : tags option;
  2. final_backup_id : backup_id option;
}

The response object for the Amazon FSx for NetApp ONTAP volume being deleted in the DeleteVolume operation.

type nonrec delete_volume_response = {
  1. ontap_response : delete_volume_ontap_response option;
    (*

    Returned after a DeleteVolume request, showing the status of the delete request.

    *)
  2. lifecycle : volume_lifecycle option;
    (*

    The lifecycle state of the volume being deleted. If the DeleteVolume operation is successful, this value is DELETING.

    *)
  3. volume_id : volume_id option;
    (*

    The ID of the volume that's being deleted.

    *)
}
type nonrec delete_volume_ontap_configuration = {
  1. bypass_snaplock_enterprise_retention : flag option;
    (*

    Setting this to true allows a SnapLock administrator to delete an FSx for ONTAP SnapLock Enterprise volume with unexpired write once, read many (WORM) files. The IAM permission fsx:BypassSnaplockEnterpriseRetention is also required to delete SnapLock Enterprise volumes with unexpired WORM files. The default value is false.

    For more information, see Deleting a SnapLock volume.

    *)
  2. final_backup_tags : tags option;
  3. skip_final_backup : flag option;
    (*

    Set to true if you want to skip taking a final backup of the volume you are deleting.

    *)
}

Use to specify skipping a final backup, adding tags to a final backup, or bypassing the retention period of an FSx for ONTAP SnapLock Enterprise volume when deleting an FSx for ONTAP volume.

type nonrec delete_open_zfs_volume_option =
  1. | DELETE_CHILD_VOLUMES_AND_SNAPSHOTS
type nonrec delete_open_zfs_volume_options = delete_open_zfs_volume_option list
type nonrec delete_volume_open_zfs_configuration = {
  1. options : delete_open_zfs_volume_options option;
    (*

    To delete the volume's child volumes, snapshots, and clones, use the string DELETE_CHILD_VOLUMES_AND_SNAPSHOTS.

    *)
}

A value that specifies whether to delete all child volumes and snapshots.

type nonrec delete_volume_request = {
  1. open_zfs_configuration : delete_volume_open_zfs_configuration option;
    (*

    For Amazon FSx for OpenZFS volumes, specify whether to delete all child volumes and snapshots.

    *)
  2. ontap_configuration : delete_volume_ontap_configuration option;
    (*

    For Amazon FSx for ONTAP volumes, specify whether to take a final backup of the volume and apply tags to the backup. To apply tags to the backup, you must have the fsx:TagResource permission.

    *)
  3. volume_id : volume_id;
    (*

    The ID of the volume that you are deleting.

    *)
  4. client_request_token : client_request_token option;
}
type nonrec delete_storage_virtual_machine_response = {
  1. lifecycle : storage_virtual_machine_lifecycle option;
    (*

    Describes the lifecycle state of the SVM being deleted.

    *)
  2. storage_virtual_machine_id : storage_virtual_machine_id option;
    (*

    The ID of the SVM Amazon FSx is deleting.

    *)
}
type nonrec delete_storage_virtual_machine_request = {
  1. storage_virtual_machine_id : storage_virtual_machine_id;
    (*

    The ID of the SVM that you want to delete.

    *)
  2. client_request_token : client_request_token option;
}
type nonrec delete_snapshot_response = {
  1. lifecycle : snapshot_lifecycle option;
    (*

    The lifecycle status of the snapshot. If the DeleteSnapshot operation is successful, this status is DELETING.

    *)
  2. snapshot_id : snapshot_id option;
    (*

    The ID of the deleted snapshot.

    *)
}
type nonrec delete_snapshot_request = {
  1. snapshot_id : snapshot_id;
    (*

    The ID of the snapshot that you want to delete.

    *)
  2. client_request_token : client_request_token option;
}
type nonrec delete_file_system_windows_response = {
  1. final_backup_tags : tags option;
    (*

    The set of tags applied to the final backup.

    *)
  2. final_backup_id : backup_id option;
    (*

    The ID of the final backup for this file system.

    *)
}

The response object for the Microsoft Windows file system used in the DeleteFileSystem operation.

type nonrec delete_file_system_windows_configuration = {
  1. final_backup_tags : tags option;
    (*

    A set of tags for your final backup.

    *)
  2. skip_final_backup : flag option;
    (*

    By default, Amazon FSx for Windows takes a final backup on your behalf when the DeleteFileSystem operation is invoked. Doing this helps protect you from data loss, and we highly recommend taking the final backup. If you want to skip this backup, use this flag to do so.

    *)
}

The configuration object for the Microsoft Windows file system used in the DeleteFileSystem operation.

type nonrec delete_file_system_lustre_response = {
  1. final_backup_tags : tags option;
    (*

    The set of tags applied to the final backup.

    *)
  2. final_backup_id : backup_id option;
    (*

    The ID of the final backup for this file system.

    *)
}

The response object for the Amazon FSx for Lustre file system being deleted in the DeleteFileSystem operation.

type nonrec delete_file_system_open_zfs_response = {
  1. final_backup_tags : tags option;
  2. final_backup_id : backup_id option;
}

The response object for the Amazon FSx for OpenZFS file system that's being deleted in the DeleteFileSystem operation.

type nonrec delete_file_system_response = {
  1. open_zfs_response : delete_file_system_open_zfs_response option;
    (*

    The response object for the OpenZFS file system that's being deleted in the DeleteFileSystem operation.

    *)
  2. lustre_response : delete_file_system_lustre_response option;
  3. windows_response : delete_file_system_windows_response option;
  4. lifecycle : file_system_lifecycle option;
    (*

    The file system lifecycle for the deletion request. If the DeleteFileSystem operation is successful, this status is DELETING.

    *)
  5. file_system_id : file_system_id option;
    (*

    The ID of the file system that's being deleted.

    *)
}

The response object for the DeleteFileSystem operation.

type nonrec delete_file_system_lustre_configuration = {
  1. final_backup_tags : tags option;
    (*

    Use if SkipFinalBackup is set to false, and you want to apply an array of tags to the final backup. If you have set the file system property CopyTagsToBackups to true, and you specify one or more FinalBackupTags when deleting a file system, Amazon FSx will not copy any existing file system tags to the backup.

    *)
  2. skip_final_backup : flag option;
    (*

    Set SkipFinalBackup to false if you want to take a final backup of the file system you are deleting. By default, Amazon FSx will not take a final backup on your behalf when the DeleteFileSystem operation is invoked. (Default = true)

    The fsx:CreateBackup permission is required if you set SkipFinalBackup to false in order to delete the file system and take a final backup.

    *)
}

The configuration object for the Amazon FSx for Lustre file system being deleted in the DeleteFileSystem operation.

type nonrec delete_file_system_open_zfs_option =
  1. | DELETE_CHILD_VOLUMES_AND_SNAPSHOTS
type nonrec delete_file_system_open_zfs_options = delete_file_system_open_zfs_option list
type nonrec delete_file_system_open_zfs_configuration = {
  1. options : delete_file_system_open_zfs_options option;
    (*

    To delete a file system if there are child volumes present below the root volume, use the string DELETE_CHILD_VOLUMES_AND_SNAPSHOTS. If your file system has child volumes and you don't use this option, the delete request will fail.

    *)
  2. final_backup_tags : tags option;
    (*

    A list of tags to apply to the file system's final backup.

    *)
  3. skip_final_backup : flag option;
    (*

    By default, Amazon FSx for OpenZFS takes a final backup on your behalf when the DeleteFileSystem operation is invoked. Doing this helps protect you from data loss, and we highly recommend taking the final backup. If you want to skip taking a final backup, set this value to true.

    *)
}

The configuration object for the Amazon FSx for OpenZFS file system used in the DeleteFileSystem operation.

type nonrec delete_file_system_request = {
  1. open_zfs_configuration : delete_file_system_open_zfs_configuration option;
    (*

    The configuration object for the OpenZFS file system used in the DeleteFileSystem operation.

    *)
  2. lustre_configuration : delete_file_system_lustre_configuration option;
  3. windows_configuration : delete_file_system_windows_configuration option;
  4. client_request_token : client_request_token option;
    (*

    A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent deletion. This token is automatically filled on your behalf when using the Command Line Interface (CLI) or an Amazon Web Services SDK.

    *)
  5. file_system_id : file_system_id;
    (*

    The ID of the file system that you want to delete.

    *)
}

The request object for DeleteFileSystem operation.

type nonrec delete_file_cache_response = {
  1. lifecycle : file_cache_lifecycle option;
    (*

    The cache lifecycle for the deletion request. If the DeleteFileCache operation is successful, this status is DELETING.

    *)
  2. file_cache_id : file_cache_id option;
    (*

    The ID of the cache that's being deleted.

    *)
}
type nonrec delete_file_cache_request = {
  1. client_request_token : client_request_token option;
  2. file_cache_id : file_cache_id;
    (*

    The ID of the cache that's being deleted.

    *)
}
type nonrec delete_data_in_file_system = bool
type nonrec delete_data_repository_association_response = {
  1. delete_data_in_file_system : delete_data_in_file_system option;
    (*

    Indicates whether data in the file system that corresponds to the data repository association is being deleted. Default is false.

    *)
  2. lifecycle : data_repository_lifecycle option;
    (*

    Describes the lifecycle state of the data repository association being deleted.

    *)
  3. association_id : data_repository_association_id option;
    (*

    The ID of the data repository association being deleted.

    *)
}
type nonrec delete_data_repository_association_request = {
  1. delete_data_in_file_system : delete_data_in_file_system option;
    (*

    Set to true to delete the data in the file system that corresponds to the data repository association.

    *)
  2. client_request_token : client_request_token option;
  3. association_id : data_repository_association_id;
    (*

    The ID of the data repository association that you want to delete.

    *)
}
type nonrec delete_backup_response = {
  1. lifecycle : backup_lifecycle option;
    (*

    The lifecycle status of the backup. If the DeleteBackup operation is successful, the status is DELETED.

    *)
  2. backup_id : backup_id option;
    (*

    The ID of the backup that was deleted.

    *)
}

The response object for the DeleteBackup operation.

type nonrec delete_backup_request = {
  1. client_request_token : client_request_token option;
    (*

    A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent deletion. This parameter is automatically filled on your behalf when using the CLI or SDK.

    *)
  2. backup_id : backup_id;
    (*

    The ID of the backup that you want to delete.

    *)
}

The request object for the DeleteBackup operation.

type nonrec backup_restoring = {
  1. file_system_id : file_system_id option;
    (*

    The ID of a file system being restored from the backup.

    *)
  2. message : error_message option;
}

You can't delete a backup while it's being used to restore a file system.

type nonrec backup_in_progress = {
  1. message : error_message option;
}

Another backup is already under way. Wait for completion before initiating additional backups of this file system.

type nonrec backup_being_copied = {
  1. backup_id : backup_id option;
  2. message : error_message option;
}

You can't delete a backup while it's being copied.

type nonrec data_repository_task_executing = {
  1. message : error_message option;
}

An existing data repository task is currently executing on the file system. Wait until the existing task has completed, then create the new task.

type nonrec data_repository_task_ended = {
  1. message : error_message option;
}

The data repository task could not be canceled because the task has already ended.

type nonrec create_volume_response = {
  1. volume : volume option;
    (*

    Returned after a successful CreateVolume API operation, describing the volume just created.

    *)
}
type nonrec create_snaplock_configuration = {
  1. volume_append_mode_enabled : flag option;
    (*

    Enables or disables volume-append mode on an FSx for ONTAP SnapLock volume. Volume-append mode allows you to create WORM-appendable files and write data to them incrementally. The default value is false.

    For more information, see Volume-append mode.

    *)
  2. snaplock_type : snaplock_type;
    (*

    Specifies the retention mode of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. You can choose one of the following retention modes:

    • COMPLIANCE: Files transitioned to write once, read many (WORM) on a Compliance volume can't be deleted until their retention periods expire. This retention mode is used to address government or industry-specific mandates or to protect against ransomware attacks. For more information, see SnapLock Compliance.
    • ENTERPRISE: Files transitioned to WORM on an Enterprise volume can be deleted by authorized users before their retention periods expire using privileged delete. This retention mode is used to advance an organization's data integrity and internal compliance or to test retention settings before using SnapLock Compliance. For more information, see SnapLock Enterprise.
    *)
  3. retention_period : snaplock_retention_period option;
    (*

    Specifies the retention period of an FSx for ONTAP SnapLock volume.

    *)
  4. privileged_delete : privileged_delete option;
    (*

    Enables, disables, or permanently disables privileged delete on an FSx for ONTAP SnapLock Enterprise volume. Enabling privileged delete allows SnapLock administrators to delete WORM files even if they have active retention periods. PERMANENTLY_DISABLED is a terminal state. If privileged delete is permanently disabled on a SnapLock volume, you can't re-enable it. The default value is DISABLED.

    For more information, see Privileged delete.

    *)
  5. autocommit_period : autocommit_period option;
    (*

    The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.

    *)
  6. audit_log_volume : flag option;
    (*

    Enables or disables the audit log volume for an FSx for ONTAP SnapLock volume. The default value is false. If you set AuditLogVolume to true, the SnapLock volume is created as an audit log volume. The minimum retention period for an audit log volume is six months.

    For more information, see SnapLock audit log volumes.

    *)
}

Defines the SnapLock configuration when creating an FSx for ONTAP SnapLock volume.

type nonrec aggregate_list_multiplier = int
type nonrec create_aggregate_configuration = {
  1. constituents_per_aggregate : aggregate_list_multiplier option;
    (*

    Used to explicitly set the number of constituents within the FlexGroup per storage aggregate. This field is optional when creating a FlexGroup volume. If unspecified, the default value will be 8. This field cannot be provided when creating a FlexVol volume.

    *)
  2. aggregates : aggregates option;
    (*

    Used to specify the names of aggregates on which the volume will be created.

    *)
}

Used to specify the configuration options for an FSx for ONTAP volume's storage aggregate or aggregates.

type nonrec create_ontap_volume_configuration = {
  1. size_in_bytes : volume_capacity_bytes option;
    (*

    Specifies the configured size of the volume, in bytes.

    *)
  2. aggregate_configuration : create_aggregate_configuration option;
    (*

    Use to specify configuration options for a volume’s storage aggregate or aggregates.

    *)
  3. volume_style : volume_style option;
    (*

    Use to specify the style of an ONTAP volume. FSx for ONTAP offers two styles of volumes that you can use for different purposes, FlexVol and FlexGroup volumes. For more information, see Volume styles in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  4. snaplock_configuration : create_snaplock_configuration option;
    (*

    Specifies the SnapLock configuration for an FSx for ONTAP volume.

    *)
  5. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags for the volume should be copied to backups. This value defaults to false. If it's set to true, all tags for the volume are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the volume, regardless of this value.

    *)
  6. snapshot_policy : snapshot_policy option;
    (*

    Specifies the snapshot policy for the volume. There are three built-in snapshot policies:

    • default: This is the default policy. A maximum of six hourly snapshots taken five minutes past the hour. A maximum of two daily snapshots taken Monday through Saturday at 10 minutes after midnight. A maximum of two weekly snapshots taken every Sunday at 15 minutes after midnight.
    • default-1weekly: This policy is the same as the default policy except that it only retains one snapshot from the weekly schedule.
    • none: This policy does not take any snapshots. This policy can be assigned to volumes to prevent automatic snapshots from being taken.

    You can also provide the name of a custom policy that you created with the ONTAP CLI or REST API.

    For more information, see Snapshot policies in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  7. ontap_volume_type : input_ontap_volume_type option;
    (*

    Specifies the type of volume you are creating. Valid values are the following:

    • RW specifies a read/write volume. RW is the default.
    • DP specifies a data-protection volume. A DP volume is read-only and can be used as the destination of a NetApp SnapMirror relationship.

    For more information, see Volume types in the Amazon FSx for NetApp ONTAP User Guide.

    *)
  8. tiering_policy : tiering_policy option;
  9. storage_virtual_machine_id : storage_virtual_machine_id;
    (*

    Specifies the ONTAP SVM in which to create the volume.

    *)
  10. storage_efficiency_enabled : flag option;
    (*

    Set to true to enable deduplication, compression, and compaction storage efficiency features on the volume, or set to false to disable them.

    StorageEfficiencyEnabled is required when creating a RW volume (OntapVolumeType set to RW).

    *)
  11. size_in_megabytes : volume_capacity option;
    (*

    Use SizeInBytes instead. Specifies the size of the volume, in megabytes (MB), that you are creating.

    *)
  12. security_style : security_style option;
    (*

    Specifies the security style for the volume. If a volume's security style is not specified, it is automatically set to the root volume's security style. The security style determines the type of permissions that FSx for ONTAP uses to control data access. Specify one of the following values:

    • UNIX if the file system is managed by a UNIX administrator, the majority of users are NFS clients, and an application accessing the data uses a UNIX user as the service account.
    • NTFS if the file system is managed by a Windows administrator, the majority of users are SMB clients, and an application accessing the data uses a Windows user as the service account.
    • MIXED This is an advanced setting. For more information, see the topic What the security styles and their effects are in the NetApp Documentation Center.

    For more information, see Volume security style in the FSx for ONTAP User Guide.

    *)
  13. junction_path : junction_path option;
    (*

    Specifies the location in the SVM's namespace where the volume is mounted. This parameter is required. The JunctionPath must have a leading forward slash, such as /vol3.

    *)
}

Specifies the configuration of the ONTAP volume that you are creating.

type nonrec create_open_zfs_origin_snapshot_configuration = {
  1. copy_strategy : open_zfs_copy_strategy;
    (*

    Specifies the strategy used when copying data from the snapshot to the new volume.

    • CLONE - The new volume references the data in the origin snapshot. Cloning a snapshot is faster than copying data from the snapshot to a new volume and doesn't consume disk throughput. However, the origin snapshot can't be deleted if there is a volume using its copied data.
    • FULL_COPY - Copies all data from the snapshot to the new volume.

      Specify this option to create the volume from a snapshot on another FSx for OpenZFS file system.

    The INCREMENTAL_COPY option is only for updating an existing volume by using a snapshot from another FSx for OpenZFS file system. For more information, see CopySnapshotAndUpdateVolume.

    *)
  2. snapshot_ar_n : resource_ar_n;
}

The snapshot configuration to use when creating an Amazon FSx for OpenZFS volume from a snapshot.

type nonrec create_open_zfs_volume_configuration = {
  1. user_and_group_quotas : open_zfs_user_and_group_quotas option;
    (*

    Configures how much storage users and groups can use on the volume.

    *)
  2. nfs_exports : open_zfs_nfs_exports option;
    (*

    The configuration object for mounting a Network File System (NFS) file system.

    *)
  3. read_only : read_only option;
    (*

    A Boolean value indicating whether the volume is read-only.

    *)
  4. origin_snapshot : create_open_zfs_origin_snapshot_configuration option;
    (*

    The configuration object that specifies the snapshot to use as the origin of the data for the volume.

    *)
  5. copy_tags_to_snapshots : flag option;
    (*

    A Boolean value indicating whether tags for the volume should be copied to snapshots. This value defaults to false. If this value is set to true, and you do not specify any tags, all tags for the original volume are copied over to snapshots. If this value is set to true, and you do specify one or more tags, only the specified tags for the original volume are copied over to snapshots. If you specify one or more tags when creating a new snapshot, no tags are copied over from the original volume, regardless of this value.

    *)
  6. data_compression_type : open_zfs_data_compression_type option;
    (*

    Specifies the method used to compress the data on the volume. The compression type is NONE by default.

    • NONE - Doesn't compress the data on the volume. NONE is the default.
    • ZSTD - Compresses the data in the volume using the Zstandard (ZSTD) compression algorithm. ZSTD compression provides a higher level of data compression and higher read throughput performance than LZ4 compression.
    • LZ4 - Compresses the data in the volume using the LZ4 compression algorithm. LZ4 compression provides a lower level of compression and higher write throughput performance than ZSTD compression.

    For more information about volume compression types and the performance of your Amazon FSx for OpenZFS file system, see Tips for maximizing performance File system and volume settings in the Amazon FSx for OpenZFS User Guide.

    *)
  7. record_size_ki_b : integer_record_size_ki_b option;
    (*

    Specifies the suggested block size for a volume in a ZFS dataset, in kibibytes (KiB). For file systems using the Intelligent-Tiering storage class, valid values are 128, 256, 512, 1024, 2048, or 4096 KiB, with a default of 1024 KiB. For all other file systems, valid values are 4, 8, 16, 32, 64, 128, 256, 512, or 1024 KiB, with a default of 128 KiB. We recommend using the default setting for the majority of use cases. Generally, workloads that write in fixed small or large record sizes may benefit from setting a custom record size, like database workloads (small record size) or media streaming workloads (large record size). For additional guidance on when to set a custom record size, see ZFS Record size in the Amazon FSx for OpenZFS User Guide.

    *)
  8. storage_capacity_quota_gi_b : integer_no_max_from_negative_one option;
    (*

    Sets the maximum storage size in gibibytes (GiB) for the volume. You can specify a quota that is larger than the storage on the parent volume. A volume quota limits the amount of storage that the volume can consume to the configured amount, but does not guarantee the space will be available on the parent volume. To guarantee quota space, you must also set StorageCapacityReservationGiB. To not specify a storage capacity quota, set this to -1.

    For more information, see Volume properties in the Amazon FSx for OpenZFS User Guide.

    *)
  9. storage_capacity_reservation_gi_b : integer_no_max_from_negative_one option;
    (*

    Specifies the amount of storage in gibibytes (GiB) to reserve from the parent volume. Setting StorageCapacityReservationGiB guarantees that the specified amount of storage space on the parent volume will always be available for the volume. You can't reserve more storage than the parent volume has. To not specify a storage capacity reservation, set this to 0 or -1. For more information, see Volume properties in the Amazon FSx for OpenZFS User Guide.

    *)
  10. parent_volume_id : volume_id;
    (*

    The ID of the volume to use as the parent volume of the volume that you are creating.

    *)
}

Specifies the configuration of the Amazon FSx for OpenZFS volume that you are creating.

type nonrec create_volume_request = {
  1. open_zfs_configuration : create_open_zfs_volume_configuration option;
    (*

    Specifies the configuration to use when creating the OpenZFS volume.

    *)
  2. tags : tags option;
  3. ontap_configuration : create_ontap_volume_configuration option;
    (*

    Specifies the configuration to use when creating the ONTAP volume.

    *)
  4. name : volume_name;
    (*

    Specifies the name of the volume that you're creating.

    *)
  5. volume_type : volume_type;
    (*

    Specifies the type of volume to create; ONTAP and OPENZFS are the only valid volume types.

    *)
  6. client_request_token : client_request_token option;
}
type nonrec create_volume_from_backup_response = {
  1. volume : volume option;
    (*

    Returned after a successful CreateVolumeFromBackup API operation, describing the volume just created.

    *)
}
type nonrec create_volume_from_backup_request = {
  1. tags : tags option;
  2. ontap_configuration : create_ontap_volume_configuration option;
    (*

    Specifies the configuration of the ONTAP volume that you are creating.

    *)
  3. name : volume_name;
    (*

    The name of the new volume you're creating.

    *)
  4. client_request_token : client_request_token option;
  5. backup_id : backup_id;
}
type nonrec create_svm_active_directory_configuration = {
  1. self_managed_active_directory_configuration : self_managed_active_directory_configuration option;
  2. net_bios_name : net_bios_alias;
    (*

    The NetBIOS name of the Active Directory computer object that will be created for your SVM.

    *)
}

The configuration that Amazon FSx uses to join the ONTAP storage virtual machine (SVM) to your self-managed (including on-premises) Microsoft Active Directory directory.

type nonrec create_storage_virtual_machine_response = {
  1. storage_virtual_machine : storage_virtual_machine option;
    (*

    Returned after a successful CreateStorageVirtualMachine operation; describes the SVM just created.

    *)
}
type nonrec create_storage_virtual_machine_request = {
  1. root_volume_security_style : storage_virtual_machine_root_volume_security_style option;
    (*

    The security style of the root volume of the SVM. Specify one of the following values:

    • UNIX if the file system is managed by a UNIX administrator, the majority of users are NFS clients, and an application accessing the data uses a UNIX user as the service account.
    • NTFS if the file system is managed by a Microsoft Windows administrator, the majority of users are SMB clients, and an application accessing the data uses a Microsoft Windows user as the service account.
    • MIXED This is an advanced setting. For more information, see Volume security style in the Amazon FSx for NetApp ONTAP User Guide.
    *)
  2. tags : tags option;
  3. svm_admin_password : admin_password option;
    (*

    The password to use when managing the SVM using the NetApp ONTAP CLI or REST API. If you do not specify a password, you can still use the file system's fsxadmin user to manage the SVM.

    *)
  4. name : storage_virtual_machine_name;
    (*

    The name of the SVM.

    *)
  5. file_system_id : file_system_id;
  6. client_request_token : client_request_token option;
  7. active_directory_configuration : create_svm_active_directory_configuration option;
    (*

    Describes the self-managed Microsoft Active Directory to which you want to join the SVM. Joining an Active Directory provides user authentication and access control for SMB clients, including Microsoft Windows and macOS clients accessing the file system.

    *)
}
type nonrec active_directory_error_type =
  1. | INVALID_DOMAIN_STAGE
  2. | INVALID_NETWORK_TYPE
  3. | WRONG_VPC
  4. | INCOMPATIBLE_DOMAIN_MODE
  5. | DOMAIN_NOT_FOUND

The type of error relating to Microsoft Active Directory. NOT_FOUND means that no directory was found by specifying the given directory. INCOMPATIBLE_MODE means that the directory specified is not a Microsoft AD directory. WRONG_VPC means that the specified directory isn't accessible from the specified VPC. WRONG_STAGE means that the specified directory isn't currently in the ACTIVE state.

type nonrec active_directory_error = {
  1. message : error_message option;
  2. type_ : active_directory_error_type option;
    (*

    The type of Active Directory error.

    *)
  3. active_directory_id : directory_id;
    (*

    The directory ID of the directory that an error pertains to.

    *)
}

An Active Directory error.

type nonrec create_snapshot_response = {
  1. snapshot : snapshot option;
    (*

    A description of the snapshot.

    *)
}
type nonrec create_snapshot_request = {
  1. tags : tags option;
  2. volume_id : volume_id;
    (*

    The ID of the volume that you are taking a snapshot of.

    *)
  3. name : snapshot_name;
    (*

    The name of the snapshot.

    *)
  4. client_request_token : client_request_token option;
}
type nonrec create_file_system_windows_configuration = {
  1. fsrm_configuration : windows_fsrm_configuration option;
    (*

    The File Server Resource Manager (FSRM) configuration that Amazon FSx for Windows File Server uses for the file system. FSRM is disabled by default.

    *)
  2. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS (input/output operations per second) configuration for an Amazon FSx for Windows file system. By default, Amazon FSx automatically provisions 3 IOPS per GiB of storage capacity. You can provision additional IOPS per GiB of storage, up to the maximum limit associated with your chosen throughput capacity.

    *)
  3. audit_log_configuration : windows_audit_log_create_configuration option;
    (*

    The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system.

    *)
  4. aliases : alternate_dns_names option;
    (*

    An array of one or more DNS alias names that you want to associate with the Amazon FSx file system. Aliases allow you to use existing DNS names to access the data in your Amazon FSx file system. You can associate up to 50 aliases with a file system at any time. You can associate additional DNS aliases after you create the file system using the AssociateFileSystemAliases operation. You can remove DNS aliases from the file system after it is created using the DisassociateFileSystemAliases operation. You only need to specify the alias name in the request payload. For more information, see Managing DNS aliases and Accessing data using DNS aliases.

    An alias name has to meet the following requirements:

    • Formatted as a fully-qualified domain name (FQDN), hostname.domain, for example, accounting.example.com.
    • Can contain alphanumeric characters, the underscore (_), and the hyphen (-).
    • Cannot start or end with a hyphen.
    • Can start with a numeric.

    For DNS alias names, Amazon FSx stores alphabetic characters as lowercase letters (a-z), regardless of how you specify them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes.

    *)
  5. copy_tags_to_backups : flag option;
    (*

    A boolean flag indicating whether tags for the file system should be copied to backups. This value defaults to false. If it's set to true, all tags for the file system are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    *)
  6. automatic_backup_retention_days : automatic_backup_retention_days option;
    (*

    The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 30.

    *)
  7. daily_automatic_backup_start_time : daily_time option;
    (*

    The preferred time to take daily automatic backups, formatted HH:MM in the UTC time zone.

    *)
  8. weekly_maintenance_start_time : weekly_time option;
    (*

    The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone, where d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.

    *)
  9. throughput_capacity : megabytes_per_second;
    (*

    Sets the throughput capacity of an Amazon FSx file system, measured in megabytes per second (MB/s), in 2 to the nth increments, between 2^3 (8) and 2^11 (2048).

    *)
  10. preferred_subnet_id : subnet_id option;
    (*

    Required when DeploymentType is set to MULTI_AZ_1. This specifies the subnet in which you want the preferred file server to be located. For in-Amazon Web Services applications, we recommend that you launch your clients in the same Availability Zone (AZ) as your preferred file server to reduce cross-AZ data transfer costs and minimize latency.

    *)
  11. deployment_type : windows_deployment_type option;
    (*

    Specifies the file system deployment type, valid values are the following:

    • MULTI_AZ_1 - Deploys a high availability file system that is configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability. You can only deploy a Multi-AZ file system in Amazon Web Services Regions that have a minimum of three Availability Zones. Also supports HDD storage type
    • SINGLE_AZ_1 - (Default) Choose to deploy a file system that is configured for single AZ redundancy.
    • SINGLE_AZ_2 - The latest generation Single AZ file system. Specifies a file system that is configured for single AZ redundancy and supports HDD storage type.

    For more information, see Availability and Durability: Single-AZ and Multi-AZ File Systems.

    *)
  12. self_managed_active_directory_configuration : self_managed_active_directory_configuration option;
  13. active_directory_id : directory_id option;
    (*

    The ID for an existing Amazon Web Services Managed Microsoft Active Directory (AD) instance that the file system should join when it's created.

    *)
}

The configuration object for the Microsoft Windows file system used in CreateFileSystem and CreateFileSystemFromBackup operations.

type nonrec create_file_system_response = {
  1. file_system : file_system option;
    (*

    The configuration of the file system that was created.

    *)
}

The response object returned after the file system is created.

type nonrec create_file_system_lustre_metadata_configuration = {
  1. mode : metadata_configuration_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 (supported only on SSD file systems), 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.
    *)
  2. iops : metadata_iops option;
    (*

    (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.

    • For SSD file systems, valid values are 1500, 3000, 6000, 12000, and multiples of 12000 up to a maximum of 192000.
    • For Intelligent-Tiering file systems, valid values are 6000 and 12000.

    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.

    *)
}

The Lustre metadata performance configuration for the creation of an Amazon FSx for Lustre file system using a PERSISTENT_2 deployment type. The configuration uses a Metadata IOPS value to set the maximum rate of metadata disk IOPS supported by the file system.

After creation, the file system supports increasing metadata performance. For more information on Metadata IOPS, see Lustre metadata performance configuration in the Amazon FSx for Lustre User Guide.

type nonrec create_file_system_lustre_configuration = {
  1. data_read_cache_configuration : lustre_read_cache_configuration option;
    (*

    Specifies the optional provisioned SSD read cache on FSx for Lustre file systems that use the Intelligent-Tiering storage class. Required when StorageType is set to INTELLIGENT_TIERING.

    *)
  2. throughput_capacity : throughput_capacity_mbps option;
    (*

    Specifies the throughput of an FSx for Lustre file system using the Intelligent-Tiering storage class, measured in megabytes per second (MBps). Valid values are 4000 MBps or multiples of 4000 MBps. You pay for the amount of throughput that you provision.

    *)
  3. metadata_configuration : create_file_system_lustre_metadata_configuration option;
    (*

    The Lustre metadata performance configuration for the creation of an FSx for Lustre file system using a PERSISTENT_2 deployment type.

    *)
  4. root_squash_configuration : lustre_root_squash_configuration option;
    (*

    The Lustre root squash configuration used when creating an Amazon FSx for Lustre file system. When enabled, root squash restricts root-level access from clients that try to access your file system as a root user.

    *)
  5. log_configuration : lustre_log_create_configuration option;
    (*

    The Lustre logging configuration used when creating an Amazon FSx for Lustre file system. When logging is enabled, Lustre logs error and warning events for data repositories associated with your file system to Amazon CloudWatch Logs.

    *)
  6. efa_enabled : flag option;
    (*

    (Optional) Specifies whether Elastic Fabric Adapter (EFA) and GPUDirect Storage (GDS) support is enabled for the Amazon FSx for Lustre file system.

    (Default = false)

    *)
  7. data_compression_type : data_compression_type option;
    (*

    Sets the data compression configuration for the file system. DataCompressionType can have the following values:

    • NONE - (Default) Data compression is turned off when the file system is created.
    • LZ4 - Data compression is turned on with the LZ4 algorithm.

    For more information, see Lustre data compression in the Amazon FSx for Lustre User Guide.

    *)
  8. drive_cache_type : drive_cache_type option;
    (*

    The type of drive cache used by PERSISTENT_1 file systems that are provisioned with HDD storage devices. This parameter is required when storage type is HDD. Set this property to READ to improve the performance for frequently accessed files by caching up to 20% of the total storage capacity of the file system.

    This parameter is required when StorageType is set to HDD.

    *)
  9. copy_tags_to_backups : flag option;
    (*

    (Optional) Not available for use with file systems that are linked to a data repository. A boolean flag indicating whether tags for the file system should be copied to backups. The default value is false. If CopyTagsToBackups is set to true, all file system tags are copied to all automatic and user-initiated backups when the user doesn't specify any backup-specific tags. If CopyTagsToBackups is set to true and you specify one or more backup tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    (Default = false)

    For more information, see Working with backups in the Amazon FSx for Lustre User Guide.

    *)
  10. automatic_backup_retention_days : automatic_backup_retention_days option;
    (*

    The number of days to retain automatic backups. Setting this property to 0 disables automatic backups. You can retain automatic backups for a maximum of 90 days. The default is 0.

    *)
  11. daily_automatic_backup_start_time : daily_time option;
  12. per_unit_storage_throughput : per_unit_storage_throughput option;
    (*

    Required with PERSISTENT_1 and PERSISTENT_2 deployment types using an SSD or HDD storage class, provisions the amount of read and write throughput for each 1 tebibyte (TiB) of file system storage capacity, in MB/s/TiB. File system throughput capacity is calculated by multiplying file system storage capacity (TiB) by the PerUnitStorageThroughput (MB/s/TiB). For a 2.4-TiB file system, provisioning 50 MB/s/TiB of PerUnitStorageThroughput yields 120 MB/s of file system throughput. You pay for the amount of throughput that you provision.

    Valid values:

    • For PERSISTENT_1 SSD storage: 50, 100, 200 MB/s/TiB.
    • For PERSISTENT_1 HDD storage: 12, 40 MB/s/TiB.
    • For PERSISTENT_2 SSD storage: 125, 250, 500, 1000 MB/s/TiB.
    *)
  13. auto_import_policy : auto_import_policy_type option;
    (*

    (Optional) When you create your file system, your existing S3 objects appear as file and directory listings. Use this parameter to choose how Amazon FSx keeps your file and directory listings up to date as you add or modify objects in your linked S3 bucket. AutoImportPolicy can have the following values:

    • NONE - (Default) AutoImport is off. Amazon FSx only updates file and directory listings from the linked S3 bucket when the file system is created. FSx does not update file and directory listings for any new or changed objects after choosing this option.
    • NEW - AutoImport is on. Amazon FSx automatically imports directory listings of any new objects added to the linked S3 bucket that do not currently exist in the FSx file system.
    • NEW_CHANGED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket and any existing objects that are changed in the S3 bucket after you choose this option.
    • NEW_CHANGED_DELETED - AutoImport is on. Amazon FSx automatically imports file and directory listings of any new objects added to the S3 bucket, any existing objects that are changed in the S3 bucket, and any objects that were deleted in the S3 bucket.

    For more information, see Automatically import updates from your S3 bucket.

    This parameter is not supported for file systems with a data repository association.

    *)
  14. deployment_type : lustre_deployment_type option;
    (*

    (Optional) Choose SCRATCH_1 and SCRATCH_2 deployment types when you need temporary storage and shorter-term processing of data. The SCRATCH_2 deployment type provides in-transit encryption of data and higher burst throughput capacity than SCRATCH_1.

    Choose PERSISTENT_1 for longer-term storage and for throughput-focused workloads that aren’t latency-sensitive. PERSISTENT_1 supports encryption of data in transit, and is available in all Amazon Web Services Regions in which FSx for Lustre is available.

    Choose PERSISTENT_2 for longer-term storage and for latency-sensitive workloads that require the highest levels of IOPS/throughput. PERSISTENT_2 supports the SSD and Intelligent-Tiering storage classes. You can optionally specify a metadata configuration mode for PERSISTENT_2 which supports increasing metadata performance. PERSISTENT_2 is available in a limited number of Amazon Web Services Regions. For more information, and an up-to-date list of Amazon Web Services Regions in which PERSISTENT_2 is available, see Deployment and storage class options for FSx for Lustre file systems in the Amazon FSx for Lustre User Guide.

    If you choose PERSISTENT_2, and you set FileSystemTypeVersion to 2.10, the CreateFileSystem operation fails.

    Encryption of data in transit is automatically turned on when you access SCRATCH_2, PERSISTENT_1, and PERSISTENT_2 file systems from Amazon EC2 instances that support automatic encryption in the Amazon Web Services Regions where they are available. For more information about encryption in transit for FSx for Lustre file systems, see Encrypting data in transit in the Amazon FSx for Lustre User Guide.

    (Default = SCRATCH_1)

    *)
  15. imported_file_chunk_size : megabytes option;
    (*

    (Optional) For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

    The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

    This parameter is not supported for file systems with a data repository association.

    *)
  16. export_path : archive_path option;
    (*

    (Optional) Specifies the path in the Amazon S3 bucket where the root of your Amazon FSx file system is exported. The path must use the same Amazon S3 bucket as specified in ImportPath. You can provide an optional prefix to which new and changed data is to be exported from your Amazon FSx for Lustre file system. If an ExportPath value is not provided, Amazon FSx sets a default export path, s3://import-bucket/FSxLustre[creation-timestamp]. The timestamp is in UTC format, for example s3://import-bucket/FSxLustre20181105T222312Z.

    The Amazon S3 export bucket must be the same as the import bucket specified by ImportPath. If you specify only a bucket name, such as s3://import-bucket, you get a 1:1 mapping of file system objects to S3 bucket objects. This mapping means that the input data in S3 is overwritten on export. If you provide a custom prefix in the export path, such as s3://import-bucket/[custom-optional-prefix], Amazon FSx exports the contents of your file system to that export prefix in the Amazon S3 bucket.

    This parameter is not supported for file systems with a data repository association.

    *)
  17. import_path : archive_path option;
    (*

    (Optional) The path to the Amazon S3 bucket (including the optional prefix) that you're using as the data repository for your Amazon FSx for Lustre file system. The root of your FSx for Lustre file system will be mapped to the root of the Amazon S3 bucket you select. An example is s3://import-bucket/optional-prefix. If you specify a prefix after the Amazon S3 bucket name, only object keys with that prefix are loaded into the file system.

    This parameter is not supported for file systems with a data repository association.

    *)
  18. weekly_maintenance_start_time : weekly_time option;
    (*

    (Optional) The preferred start time to perform weekly maintenance, formatted d:HH:MM in the UTC time zone, where d is the weekday number, from 1 through 7, beginning with Monday and ending with Sunday.

    *)
}

The Lustre configuration for the file system being created.

The following parameters are not supported for file systems with a data repository association created with .

  • AutoImportPolicy
  • ExportPath
  • ImportedFileChunkSize
  • ImportPath
type nonrec create_file_system_ontap_configuration = {
  1. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  2. throughput_capacity_per_ha_pair : throughput_capacity_per_ha_pair option;
    (*

    Use to choose the throughput capacity per HA pair, rather than the total throughput for the file system.

    You can define either the ThroughputCapacityPerHAPair or the ThroughputCapacity when creating a file system, but not both.

    This field and ThroughputCapacity are the same for file systems powered by one HA pair.

    • For SINGLE_AZ_1 and MULTI_AZ_1 file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps.
    • For SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps.
    • For MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value for file systems with one HA pair.
    • The value of deployment type is SINGLE_AZ_2 and ThroughputCapacity / ThroughputCapacityPerHAPair is not a valid HA pair (a value between 1 and 12).
    • The value of ThroughputCapacityPerHAPair is not a valid value.
    *)
  3. ha_pairs : ha_pairs option;
    (*

    Specifies how many high-availability (HA) pairs of file servers will power your file system. First-generation file systems are powered by 1 HA pair. Second-generation multi-AZ file systems are powered by 1 HA pair. Second generation single-AZ file systems are powered by up to 12 HA pairs. The default value is 1. The value of this property affects the values of StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide. Block storage protocol support (iSCSI and NVMe over TCP) is disabled on file systems with more than 6 HA pairs. For more information, see Using block storage protocols.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of HAPairs is less than 1 or greater than 12.
    • The value of HAPairs is greater than 1 and the value of DeploymentType is SINGLE_AZ_1, MULTI_AZ_1, or MULTI_AZ_2.
    *)
  4. weekly_maintenance_start_time : weekly_time option;
  5. throughput_capacity : megabytes_per_second option;
    (*

    Sets the throughput capacity for the file system that you're creating in megabytes per second (MBps). For more information, see Managing throughput capacity in the FSx for ONTAP User Guide.

    Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions:

    • The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value.
    • The value of ThroughputCapacity when divided by the value of HAPairs is outside of the valid range for ThroughputCapacity.
    *)
  6. route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) Specifies the route tables in which Amazon FSx creates the rules for routing traffic to the correct file server. You should specify all virtual private cloud (VPC) route tables associated with the subnets in which your clients are located. By default, Amazon FSx selects your VPC's default route table.

    Amazon FSx manages these route tables for Multi-AZ file systems using tag-based authentication. These route tables are tagged with Key: AmazonFSx; Value: ManagedByAmazonFSx. When creating FSx for ONTAP Multi-AZ file systems using CloudFormation we recommend that you add the Key: AmazonFSx; Value: ManagedByAmazonFSx tag manually.

    *)
  7. preferred_subnet_id : subnet_id option;
    (*

    Required when DeploymentType is set to MULTI_AZ_1 or MULTI_AZ_2. This specifies the subnet in which you want the preferred file server to be located.

    *)
  8. disk_iops_configuration : disk_iops_configuration option;
    (*

    The SSD IOPS configuration for the FSx for ONTAP file system.

    *)
  9. fsx_admin_password : admin_password option;
    (*

    The ONTAP administrative password for the fsxadmin user with which you administer your file system using the NetApp ONTAP CLI and REST API.

    *)
  10. endpoint_ip_address_range : ip_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API, Amazon FSx selects an unused IP address range for you from the 198.19.* range. By default in the Amazon FSx console, Amazon FSx chooses the last 64 IP addresses from the VPC’s primary CIDR range to use as the endpoint IP address range for the file system. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  11. deployment_type : ontap_deployment_type;
    (*

    Specifies the FSx for ONTAP file system deployment type to use in creating the file system.

    • MULTI_AZ_1 - A high availability file system configured for Multi-AZ redundancy to tolerate temporary Availability Zone (AZ) unavailability. This is a first-generation FSx for ONTAP file system.
    • MULTI_AZ_2 - A high availability file system configured for Multi-AZ redundancy to tolerate temporary AZ unavailability. This is a second-generation FSx for ONTAP file system.
    • SINGLE_AZ_1 - A file system configured for Single-AZ redundancy. This is a first-generation FSx for ONTAP file system.
    • SINGLE_AZ_2 - A file system configured with multiple high-availability (HA) pairs for Single-AZ redundancy. This is a second-generation FSx for ONTAP file system.

    For information about the use cases for Multi-AZ and Single-AZ deployments, refer to Choosing a file system deployment type.

    *)
  12. daily_automatic_backup_start_time : daily_time option;
  13. automatic_backup_retention_days : automatic_backup_retention_days option;
}

The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.

type nonrec create_file_system_open_zfs_configuration = {
  1. read_cache_configuration : open_zfs_read_cache_configuration option;
    (*

    Specifies the optional provisioned SSD read cache on file systems that use the Intelligent-Tiering storage class.

    *)
  2. route_table_ids : route_table_ids option;
    (*

    (Multi-AZ only) Specifies the route tables in which Amazon FSx creates the rules for routing traffic to the correct file server. You should specify all virtual private cloud (VPC) route tables associated with the subnets in which your clients are located. By default, Amazon FSx selects your VPC's default route table.

    *)
  3. endpoint_ipv6_address_range : ipv6_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  4. endpoint_ip_address_range : ip_address_range option;
    (*

    (Multi-AZ only) Specifies the IPv4 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /28 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.

    *)
  5. preferred_subnet_id : subnet_id option;
    (*

    Required when DeploymentType is set to MULTI_AZ_1. This specifies the subnet in which you want the preferred file server to be located.

    *)
  6. root_volume_configuration : open_zfs_create_root_volume_configuration option;
    (*

    The configuration Amazon FSx uses when creating the root value of the Amazon FSx for OpenZFS file system. All volumes are children of the root volume.

    *)
  7. disk_iops_configuration : disk_iops_configuration option;
  8. weekly_maintenance_start_time : weekly_time option;
  9. throughput_capacity : megabytes_per_second;
    (*

    Specifies the throughput of an Amazon FSx for OpenZFS file system, measured in megabytes per second (MBps). Valid values depend on the DeploymentType that you choose, as follows:

    • For MULTI_AZ_1 and SINGLE_AZ_2, valid values are 160, 320, 640, 1280, 2560, 3840, 5120, 7680, or 10240 MBps.
    • For SINGLE_AZ_1, valid values are 64, 128, 256, 512, 1024, 2048, 3072, or 4096 MBps.

    You pay for additional throughput capacity that you provision.

    *)
  10. deployment_type : open_zfs_deployment_type;
    (*

    Specifies the file system deployment type. Valid values are the following:

    • MULTI_AZ_1- Creates file systems with high availability and durability by replicating your data and supporting failover across multiple Availability Zones in the same Amazon Web Services Region.
    • SINGLE_AZ_HA_2- Creates file systems with high availability and throughput capacities of 160 - 10,240 MB/s using an NVMe L2ARC cache by deploying a primary and standby file system within the same Availability Zone.
    • SINGLE_AZ_HA_1- Creates file systems with high availability and throughput capacities of 64 - 4,096 MB/s by deploying a primary and standby file system within the same Availability Zone.
    • SINGLE_AZ_2- Creates file systems with throughput capacities of 160 - 10,240 MB/s using an NVMe L2ARC cache that automatically recover within a single Availability Zone.
    • SINGLE_AZ_1- Creates file systems with throughput capacities of 64 - 4,096 MBs that automatically recover within a single Availability Zone.

    For a list of which Amazon Web Services Regions each deployment type is available in, see Deployment type availability. For more information on the differences in performance between deployment types, see File system performance in the Amazon FSx for OpenZFS User Guide.

    *)
  11. daily_automatic_backup_start_time : daily_time option;
  12. copy_tags_to_volumes : flag option;
    (*

    A Boolean value indicating whether tags for the file system should be copied to volumes. This value defaults to false. If it's set to true, all tags for the file system are copied to volumes where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to volumes. If you specify one or more tags when creating the volume, no tags are copied from the file system, regardless of this value.

    *)
  13. copy_tags_to_backups : flag option;
    (*

    A Boolean value indicating whether tags for the file system should be copied to backups. This value defaults to false. If it's set to true, all tags for the file system are copied to all automatic and user-initiated backups where the user doesn't specify tags. If this value is true, and you specify one or more tags, only the specified tags are copied to backups. If you specify one or more tags when creating a user-initiated backup, no tags are copied from the file system, regardless of this value.

    *)
  14. automatic_backup_retention_days : automatic_backup_retention_days option;
}

The Amazon FSx for OpenZFS configuration properties for the file system that you are creating.

type nonrec create_file_system_request = {
  1. network_type : network_type option;
    (*

    The network type of the Amazon FSx file system that you are creating. Valid values are IPV4 (which supports IPv4 only) and DUAL (for dual-stack mode, which supports both IPv4 and IPv6). The default is IPV4. Supported for FSx for OpenZFS, FSx for ONTAP, and FSx for Windows File Server file systems.

    *)
  2. open_zfs_configuration : create_file_system_open_zfs_configuration option;
    (*

    The OpenZFS configuration for the file system that's being created.

    *)
  3. file_system_type_version : file_system_type_version option;
    (*

    For FSx for Lustre file systems, sets the Lustre version for the file system that you're creating. Valid values are 2.10, 2.12, and 2.15:

    • 2.10 is supported by the Scratch and Persistent_1 Lustre deployment types.
    • 2.12 is supported by all Lustre deployment types, except for PERSISTENT_2 with a metadata configuration mode.
    • 2.15 is supported by all Lustre deployment types and is recommended for all new file systems.

    Default value is 2.10, except for the following deployments:

    • Default value is 2.12 when DeploymentType is set to PERSISTENT_2 without a metadata configuration mode.
    • Default value is 2.15 when DeploymentType is set to PERSISTENT_2 with a metadata configuration mode.
    *)
  4. ontap_configuration : create_file_system_ontap_configuration option;
  5. lustre_configuration : create_file_system_lustre_configuration option;
  6. windows_configuration : create_file_system_windows_configuration option;
    (*

    The Microsoft Windows configuration for the file system that's being created.

    *)
  7. kms_key_id : kms_key_id option;
  8. tags : tags option;
    (*

    The tags to apply to the file system that's being created. The key value of the Name tag appears in the console as the file system name.

    *)
  9. security_group_ids : security_group_ids option;
    (*

    A list of IDs specifying the security groups to apply to all network interfaces created for file system access. This list isn't returned in later requests to describe the file system.

    You must specify a security group if you are creating a Multi-AZ FSx for ONTAP file system in a VPC subnet that has been shared with you.

    *)
  10. subnet_ids : subnet_ids;
    (*

    Specifies the IDs of the subnets that the file system will be accessible from. For Windows and ONTAP MULTI_AZ_1 deployment types,provide exactly two subnet IDs, one for the preferred file server and one for the standby file server. You specify one of these subnets as the preferred subnet using the WindowsConfiguration > PreferredSubnetID or OntapConfiguration > PreferredSubnetID properties. For more information about Multi-AZ file system configuration, see Availability and durability: Single-AZ and Multi-AZ file systems in the Amazon FSx for Windows User Guide and Availability and durability in the Amazon FSx for ONTAP User Guide.

    For Windows SINGLE_AZ_1 and SINGLE_AZ_2 and all Lustre deployment types, provide exactly one subnet ID. The file server is launched in that subnet's Availability Zone.

    *)
  11. storage_type : storage_type option;
    (*

    Sets the storage class for the file system that you're creating. Valid values are SSD, HDD, and INTELLIGENT_TIERING.

    • Set to SSD to use solid state drive storage. SSD is supported on all Windows, Lustre, ONTAP, and OpenZFS deployment types.
    • Set to HDD to use hard disk drive storage, which is supported on SINGLE_AZ_2 and MULTI_AZ_1 Windows file system deployment types, and on PERSISTENT_1 Lustre file system deployment types.
    • Set to INTELLIGENT_TIERING to use fully elastic, intelligently-tiered storage. Intelligent-Tiering is only available for OpenZFS file systems with the Multi-AZ deployment type and for Lustre file systems with the Persistent_2 deployment type.

    Default value is SSD. For more information, see Storage type options in the FSx for Windows File Server User Guide, FSx for Lustre storage classes in the FSx for Lustre User Guide, and Working with Intelligent-Tiering in the Amazon FSx for OpenZFS User Guide.

    *)
  12. storage_capacity : storage_capacity option;
    (*

    Sets the storage capacity of the file system that you're creating, in gibibytes (GiB).

    FSx for Lustre file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType and the Lustre DeploymentType, as follows:

    • For SCRATCH_2, PERSISTENT_2, and PERSISTENT_1 deployment types using SSD storage type, the valid values are 1200 GiB, 2400 GiB, and increments of 2400 GiB.
    • For PERSISTENT_1 HDD file systems, valid values are increments of 6000 GiB for 12 MB/s/TiB file systems and increments of 1800 GiB for 40 MB/s/TiB file systems.
    • For SCRATCH_1 deployment type, valid values are 1200 GiB, 2400 GiB, and increments of 3600 GiB.

    FSx for ONTAP file systems - The amount of storage capacity that you can configure depends on the value of the HAPairs property. The minimum value is calculated as 1,024 * HAPairs and the maximum is calculated as 524,288 * HAPairs.

    FSx for OpenZFS file systems - The amount of storage capacity that you can configure is from 64 GiB up to 524,288 GiB (512 TiB).

    FSx for Windows File Server file systems - The amount of storage capacity that you can configure depends on the value that you set for StorageType as follows:

    • For SSD storage, valid values are 32 GiB-65,536 GiB (64 TiB).
    • For HDD storage, valid values are 2000 GiB-65,536 GiB (64 TiB).
    *)
  13. file_system_type : file_system_type;
    (*

    The type of Amazon FSx file system to create. Valid values are WINDOWS, LUSTRE, ONTAP, and OPENZFS.

    *)
  14. client_request_token : client_request_token option;
    (*

    A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent creation. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.

    *)
}

The request object used to create a new Amazon FSx file system.

type nonrec create_file_system_from_backup_response = {
  1. file_system : file_system option;
    (*

    A description of the file system.

    *)
}

The response object for the CreateFileSystemFromBackup operation.

type nonrec create_file_system_from_backup_request = {
  1. network_type : network_type option;
    (*

    Sets the network type for the Amazon FSx for OpenZFS file system that you're creating from a backup.

    *)
  2. storage_capacity : storage_capacity option;
    (*

    Sets the storage capacity of the OpenZFS file system that you're creating from a backup, in gibibytes (GiB). Valid values are from 64 GiB up to 524,288 GiB (512 TiB). However, the value that you specify must be equal to or greater than the backup's storage capacity value. If you don't use the StorageCapacity parameter, the default is the backup's StorageCapacity value.

    If used to create a file system other than OpenZFS, you must provide a value that matches the backup's StorageCapacity value. If you provide any other value, Amazon FSx responds with an HTTP status code 400 Bad Request.

    *)
  3. open_zfs_configuration : create_file_system_open_zfs_configuration option;
    (*

    The OpenZFS configuration for the file system that's being created.

    *)
  4. file_system_type_version : file_system_type_version option;
    (*

    Sets the version for the Amazon FSx for Lustre file system that you're creating from a backup. Valid values are 2.10, 2.12, and 2.15.

    You can enter a Lustre version that is newer than the backup's FileSystemTypeVersion setting. If you don't enter a newer Lustre version, it defaults to the backup's setting.

    *)
  5. kms_key_id : kms_key_id option;
  6. storage_type : storage_type option;
    (*

    Sets the storage type for the Windows, OpenZFS, or Lustre file system that you're creating from a backup. Valid values are SSD, HDD, and INTELLIGENT_TIERING.

    • Set to SSD to use solid state drive storage. SSD is supported on all Windows and OpenZFS deployment types.
    • Set to HDD to use hard disk drive storage. HDD is supported on SINGLE_AZ_2 and MULTI_AZ_1 FSx for Windows File Server file system deployment types.
    • Set to INTELLIGENT_TIERING to use fully elastic, intelligently-tiered storage. Intelligent-Tiering is only available for OpenZFS file systems with the Multi-AZ deployment type and for Lustre file systems with the Persistent_2 deployment type.

    The default value is SSD.

    HDD and SSD storage types have different minimum storage capacity requirements. A restored file system's storage capacity is tied to the file system that was backed up. You can create a file system that uses HDD storage from a backup of a file system that used SSD storage if the original SSD file system had a storage capacity of at least 2000 GiB.

    *)
  7. lustre_configuration : create_file_system_lustre_configuration option;
  8. windows_configuration : create_file_system_windows_configuration option;
    (*

    The configuration for this Microsoft Windows file system.

    *)
  9. tags : tags option;
    (*

    The tags to be applied to the file system at file system creation. The key value of the Name tag appears in the console as the file system name.

    *)
  10. security_group_ids : security_group_ids option;
    (*

    A list of IDs for the security groups that apply to the specified network interfaces created for file system access. These security groups apply to all network interfaces. This value isn't returned in later DescribeFileSystem requests.

    *)
  11. subnet_ids : subnet_ids;
    (*

    Specifies the IDs of the subnets that the file system will be accessible from. For Windows MULTI_AZ_1 file system deployment types, provide exactly two subnet IDs, one for the preferred file server and one for the standby file server. You specify one of these subnets as the preferred subnet using the WindowsConfiguration > PreferredSubnetID property.

    Windows SINGLE_AZ_1 and SINGLE_AZ_2 file system deployment types, Lustre file systems, and OpenZFS file systems provide exactly one subnet ID. The file server is launched in that subnet's Availability Zone.

    *)
  12. client_request_token : client_request_token option;
    (*

    A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent creation. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.

    *)
  13. backup_id : backup_id;
}

The request object for the CreateFileSystemFromBackup operation.

type nonrec create_file_cache_response = {
  1. file_cache : file_cache_creating option;
    (*

    A description of the cache that was created.

    *)
}
type nonrec create_file_cache_lustre_configuration = {
  1. metadata_configuration : file_cache_lustre_metadata_configuration;
    (*

    The configuration for a Lustre MDT (Metadata Target) storage volume.

    *)
  2. weekly_maintenance_start_time : weekly_time option;
  3. deployment_type : file_cache_lustre_deployment_type;
    (*

    Specifies the cache deployment type, which must be CACHE_1.

    *)
  4. per_unit_storage_throughput : per_unit_storage_throughput;
    (*

    Provisions the amount of read and write throughput for each 1 tebibyte (TiB) of cache storage capacity, in MB/s/TiB. The only supported value is 1000.

    *)
}

The Amazon File Cache configuration for the cache that you are creating.

type nonrec create_file_cache_data_repository_associations = file_cache_data_repository_association list
type nonrec create_file_cache_request = {
  1. data_repository_associations : create_file_cache_data_repository_associations option;
    (*

    A list of up to 8 configurations for data repository associations (DRAs) to be created during the cache creation. The DRAs link the cache to either an Amazon S3 data repository or a Network File System (NFS) data repository that supports the NFSv3 protocol.

    The DRA configurations must meet the following requirements:

    • All configurations on the list must be of the same data repository type, either all S3 or all NFS. A cache can't link to different data repository types at the same time.
    • An NFS DRA must link to an NFS file system that supports the NFSv3 protocol.

    DRA automatic import and automatic export is not supported.

    *)
  2. lustre_configuration : create_file_cache_lustre_configuration option;
    (*

    The configuration for the Amazon File Cache resource being created.

    *)
  3. kms_key_id : kms_key_id option;
    (*

    Specifies the ID of the Key Management Service (KMS) key to use for encrypting data on an Amazon File Cache. If a KmsKeyId isn't specified, the Amazon FSx-managed KMS key for your account is used. For more information, see Encrypt in the Key Management Service API Reference.

    *)
  4. copy_tags_to_data_repository_associations : copy_tags_to_data_repository_associations option;
    (*

    A boolean flag indicating whether tags for the cache should be copied to data repository associations. This value defaults to false.

    *)
  5. tags : tags option;
  6. security_group_ids : security_group_ids option;
    (*

    A list of IDs specifying the security groups to apply to all network interfaces created for Amazon File Cache access. This list isn't returned in later requests to describe the cache.

    *)
  7. subnet_ids : subnet_ids;
  8. storage_capacity : storage_capacity;
    (*

    The storage capacity of the cache in gibibytes (GiB). Valid values are 1200 GiB, 2400 GiB, and increments of 2400 GiB.

    *)
  9. file_cache_type_version : file_system_type_version;
    (*

    Sets the Lustre version for the cache that you're creating, which must be 2.12.

    *)
  10. file_cache_type : file_cache_type;
    (*

    The type of cache that you're creating, which must be LUSTRE.

    *)
  11. client_request_token : client_request_token option;
    (*

    An idempotency token for resource creation, in a string of up to 63 ASCII characters. This token is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.

    By using the idempotent operation, you can retry a CreateFileCache operation without the risk of creating an extra cache. This approach can be useful when an initial call fails in a way that makes it unclear whether a cache was created. Examples are if a transport level timeout occurred, or your connection was reset. If you use the same client request token and the initial call created a cache, the client receives success as long as the parameters are the same.

    *)
}
type nonrec create_data_repository_task_response = {
  1. data_repository_task : data_repository_task option;
    (*

    The description of the data repository task that you just created.

    *)
}
type nonrec create_data_repository_task_request = {
  1. release_configuration : release_configuration option;
    (*

    The configuration that specifies the last accessed time criteria for files that will be released from an Amazon FSx for Lustre file system.

    *)
  2. capacity_to_release : capacity_to_release option;
    (*

    Specifies the amount of data to release, in GiB, by an Amazon File Cache AUTO_RELEASE_DATA task that automatically releases files from the cache.

    *)
  3. tags : tags option;
  4. client_request_token : client_request_token option;
  5. report : completion_report;
    (*

    Defines whether or not Amazon FSx provides a CompletionReport once the task has completed. A CompletionReport provides a detailed report on the files that Amazon FSx processed that meet the criteria specified by the Scope parameter. For more information, see Working with Task Completion Reports.

    *)
  6. file_system_id : file_system_id;
  7. paths : data_repository_task_paths option;
    (*

    A list of paths for the data repository task to use when the task is processed. If a path that you provide isn't valid, the task fails. If you don't provide paths, the default behavior is to export all files to S3 (for export tasks), import all files from S3 (for import tasks), or release all exported files that meet the last accessed time criteria (for release tasks).

    • For export tasks, the list contains paths on the FSx for Lustre file system from which the files are exported to the Amazon S3 bucket. The default path is the file system root directory. The paths you provide need to be relative to the mount point of the file system. If the mount point is /mnt/fsx and /mnt/fsx/path1 is a directory or file on the file system you want to export, then the path to provide is path1.
    • For import tasks, the list contains paths in the Amazon S3 bucket from which POSIX metadata changes are imported to the FSx for Lustre file system. The path can be an S3 bucket or prefix in the format s3://bucket-name/prefix (where prefix is optional).
    • For release tasks, the list contains directory or file paths on the FSx for Lustre file system from which to release exported files. If a directory is specified, files within the directory are released. If a file path is specified, only that file is released. To release all exported files in the file system, specify a forward slash (/) as the path.

      A file must also meet the last accessed time criteria specified in for the file to be released.

    *)
  8. type_ : data_repository_task_type;
    (*

    Specifies the type of data repository task to create.

    • EXPORT_TO_REPOSITORY tasks export from your Amazon FSx for Lustre file system to a linked data repository.
    • IMPORT_METADATA_FROM_REPOSITORY tasks import metadata changes from a linked S3 bucket to your Amazon FSx for Lustre file system.
    • RELEASE_DATA_FROM_FILESYSTEM tasks release files in your Amazon FSx for Lustre file system that have been exported to a linked S3 bucket and that meet your specified release criteria.
    • AUTO_RELEASE_DATA tasks automatically release files from an Amazon File Cache resource.
    *)
}
type nonrec create_data_repository_association_response = {
  1. association : data_repository_association option;
    (*

    The response object returned after the data repository association is created.

    *)
}
type nonrec create_data_repository_association_request = {
  1. tags : tags option;
  2. client_request_token : client_request_token option;
  3. s3 : s3_data_repository_configuration option;
    (*

    The configuration for an Amazon S3 data repository linked to an Amazon FSx Lustre file system with a data repository association. The configuration defines which file events (new, changed, or deleted files or directories) are automatically imported from the linked data repository to the file system or automatically exported from the file system to the data repository.

    *)
  4. imported_file_chunk_size : megabytes option;
    (*

    For files imported from a data repository, this value determines the stripe count and maximum amount of data per file (in MiB) stored on a single physical disk. The maximum number of disks that a single file can be striped across is limited by the total number of disks that make up the file system.

    The default chunk size is 1,024 MiB (1 GiB) and can go as high as 512,000 MiB (500 GiB). Amazon S3 objects have a maximum size of 5 TB.

    *)
  5. batch_import_meta_data_on_create : batch_import_meta_data_on_create option;
    (*

    Set to true to run an import data repository task to import metadata from the data repository to the file system after the data repository association is created. Default is false.

    *)
  6. data_repository_path : archive_path;
    (*

    The path to the Amazon S3 data repository that will be linked to the file system. The path can be an S3 bucket or prefix in the format s3://bucket-name/prefix/ (where prefix is optional). This path specifies where in the S3 data repository files will be imported from or exported to.

    *)
  7. file_system_path : namespace option;
    (*

    A path on the file system that points to a high-level directory (such as /ns1/) or subdirectory (such as /ns1/subdir/) that will be mapped 1-1 with DataRepositoryPath. The leading forward slash in the name is required. Two data repository associations cannot have overlapping file system paths. For example, if a data repository is associated with file system path /ns1/, then you cannot link another data repository with file system path /ns1/ns2.

    This path specifies where in your file system files will be exported from or imported to. This file system directory can be linked to only one Amazon S3 bucket, and no other S3 bucket can be linked to the directory.

    If you specify only a forward slash (/) as the file system path, you can link only one data repository to the file system. You can only specify "/" as the file system path for the first data repository associated with a file system.

    *)
  8. file_system_id : file_system_id;
}
type nonrec create_backup_response = {
  1. backup : backup option;
    (*

    A description of the backup.

    *)
}

The response object for the CreateBackup operation.

type nonrec create_backup_request = {
  1. volume_id : volume_id option;
    (*

    (Optional) The ID of the FSx for ONTAP volume to back up.

    *)
  2. tags : tags option;
    (*

    (Optional) The tags to apply to the backup at backup creation. The key value of the Name tag appears in the console as the backup name. If you have set CopyTagsToBackups to true, and you specify one or more tags using the CreateBackup operation, no existing file system tags are copied from the file system to the backup.

    *)
  3. client_request_token : client_request_token option;
    (*

    (Optional) A string of up to 63 ASCII characters that Amazon FSx uses to ensure idempotent creation. This string is automatically filled on your behalf when you use the Command Line Interface (CLI) or an Amazon Web Services SDK.

    *)
  4. file_system_id : file_system_id option;
    (*

    The ID of the file system to back up.

    *)
}

The request object for the CreateBackup operation.

type nonrec access_point_policy = string
type nonrec create_and_attach_s3_access_point_s3_configuration = {
  1. policy : access_point_policy option;
    (*

    Specifies an access policy to associate with the S3 access point configuration. For more information, see Configuring IAM policies for using access points in the Amazon Simple Storage Service User Guide.

    *)
  2. vpc_configuration : s3_access_point_vpc_configuration option;
    (*

    If included, Amazon S3 restricts access to this S3 access point to requests made from the specified virtual private cloud (VPC).

    *)
}

Used to create an S3 access point that accepts requests only from a virtual private cloud (VPC) to restrict data access to a private network.

type nonrec create_and_attach_s3_access_point_response = {
  1. s3_access_point_attachment : s3_access_point_attachment option;
    (*

    Describes the configuration of the S3 access point created.

    *)
}
type nonrec create_and_attach_s3_access_point_open_zfs_configuration = {
  1. file_system_identity : open_zfs_file_system_identity;
    (*

    Specifies the file system user identity to use for authorizing file read and write requests that are made using this S3 access point.

    *)
  2. volume_id : volume_id;
    (*

    The ID of the FSx for OpenZFS volume to which you want the S3 access point attached.

    *)
}

Specifies the FSx for OpenZFS volume that the S3 access point will be attached to, and the file system user identity.

type nonrec create_and_attach_s3_access_point_ontap_configuration = {
  1. file_system_identity : ontap_file_system_identity;
    (*

    Specifies the file system user identity to use for authorizing file read and write requests that are made using this S3 access point.

    *)
  2. volume_id : volume_id;
    (*

    The ID of the FSx for ONTAP volume to which you want the S3 access point attached.

    *)
}

Specifies the FSx for ONTAP volume that the S3 access point will be attached to, and the file system user identity.

type nonrec create_and_attach_s3_access_point_request = {
  1. s3_access_point : create_and_attach_s3_access_point_s3_configuration option;
    (*

    Specifies the virtual private cloud (VPC) configuration if you're creating an access point that is restricted to a VPC. For more information, see Creating access points restricted to a virtual private cloud.

    *)
  2. ontap_configuration : create_and_attach_s3_access_point_ontap_configuration option;
  3. open_zfs_configuration : create_and_attach_s3_access_point_open_zfs_configuration option;
    (*

    Specifies the configuration to use when creating and attaching an S3 access point to an FSx for OpenZFS volume.

    *)
  4. type_ : s3_access_point_attachment_type;
    (*

    The type of S3 access point you want to create. Only OpenZFS is supported.

    *)
  5. name : s3_access_point_attachment_name;
    (*

    The name you want to assign to this S3 access point.

    *)
  6. client_request_token : client_request_token option;
}
type nonrec access_point_already_owned_by_you = {
  1. message : error_message option;
  2. error_code : error_code option;
    (*

    An error code indicating that an access point with that name already exists in the Amazon Web Services Region in your Amazon Web Services account.

    *)
}

An access point with that name already exists in the Amazon Web Services Region in your Amazon Web Services account.

type nonrec copy_snapshot_and_update_volume_response = {
  1. administrative_actions : administrative_actions option;
    (*

    A list of administrative actions for the file system that are in process or waiting to be processed. Administrative actions describe changes to the Amazon FSx system.

    *)
  2. lifecycle : volume_lifecycle option;
    (*

    The lifecycle state of the destination volume.

    *)
  3. volume_id : volume_id option;
    (*

    The ID of the volume that you copied the snapshot to.

    *)
}
type nonrec copy_snapshot_and_update_volume_request = {
  1. options : update_open_zfs_volume_options option;
    (*

    Confirms that you want to delete data on the destination volume that wasn’t there during the previous snapshot replication.

    Your replication will fail if you don’t include an option for a specific type of data and that data is on your destination. For example, if you don’t include DELETE_INTERMEDIATE_SNAPSHOTS and there are intermediate snapshots on the destination, you can’t copy the snapshot.

    • DELETE_INTERMEDIATE_SNAPSHOTS - Deletes snapshots on the destination volume that aren’t on the source volume.
    • DELETE_CLONED_VOLUMES - Deletes snapshot clones on the destination volume that aren't on the source volume.
    • DELETE_INTERMEDIATE_DATA - Overwrites snapshots on the destination volume that don’t match the source snapshot that you’re copying.
    *)
  2. copy_strategy : open_zfs_copy_strategy option;
    (*

    Specifies the strategy to use when copying data from a snapshot to the volume.

    • FULL_COPY - Copies all data from the snapshot to the volume.
    • INCREMENTAL_COPY - Copies only the snapshot data that's changed since the previous replication.

    CLONE isn't a valid copy strategy option for the CopySnapshotAndUpdateVolume operation.

    *)
  3. source_snapshot_ar_n : resource_ar_n;
  4. volume_id : volume_id;
    (*

    Specifies the ID of the volume that you are copying the snapshot to.

    *)
  5. client_request_token : client_request_token option;
}
type nonrec copy_backup_response = {
  1. backup : backup option;
}
type nonrec copy_backup_request = {
  1. tags : tags option;
  2. copy_tags : flag option;
    (*

    A Boolean flag indicating whether tags from the source backup should be copied to the backup copy. This value defaults to false.

    If you set CopyTags to true and the source backup has existing tags, you can use the Tags parameter to create new tags, provided that the sum of the source backup tags and the new tags doesn't exceed 50. Both sets of tags are merged. If there are tag conflicts (for example, two tags with the same key but different values), the tags created with the Tags parameter take precedence.

    *)
  3. kms_key_id : kms_key_id option;
  4. source_region : region option;
    (*

    The source Amazon Web Services Region of the backup. Specifies the Amazon Web Services Region from which the backup is being copied. The source and destination Regions must be in the same Amazon Web Services partition. If you don't specify a Region, SourceRegion defaults to the Region where the request is sent from (in-Region copy).

    *)
  5. source_backup_id : source_backup_id;
    (*

    The ID of the source backup. Specifies the ID of the backup that's being copied.

    *)
  6. client_request_token : client_request_token option;
}
type nonrec cancel_data_repository_task_response = {
  1. task_id : task_id option;
    (*

    The ID of the task being canceled.

    *)
  2. lifecycle : data_repository_task_lifecycle option;
    (*

    The lifecycle status of the data repository task, as follows:

    • PENDING - Amazon FSx has not started the task.
    • EXECUTING - Amazon FSx is processing the task.
    • FAILED - Amazon FSx was not able to complete the task. For example, there may be files the task failed to process. The DataRepositoryTaskFailureDetails property provides more information about task failures.
    • SUCCEEDED - FSx completed the task successfully.
    • CANCELED - Amazon FSx canceled the task and it did not complete.
    • CANCELING - FSx is in process of canceling the task.
    *)
}
type nonrec cancel_data_repository_task_request = {
  1. task_id : task_id;
    (*

    Specifies the data repository task to cancel.

    *)
}

Cancels a data repository task.

type nonrec associate_file_system_aliases_response = {
  1. aliases : aliases option;
    (*

    An array of the DNS aliases that Amazon FSx is associating with the file system.

    *)
}

The system generated response showing the DNS aliases that Amazon FSx is attempting to associate with the file system. Use the API operation to monitor the status of the aliases Amazon FSx is associating with the file system. It can take up to 2.5 minutes for the alias status to change from CREATING to AVAILABLE.

type nonrec associate_file_system_aliases_request = {
  1. aliases : alternate_dns_names;
    (*

    An array of one or more DNS alias names to associate with the file system. The alias name has to comply with the following formatting requirements:

    • Formatted as a fully-qualified domain name (FQDN), hostname.domain, for example, accounting.corp.example.com.
    • Can contain alphanumeric characters and the hyphen (-).
    • Cannot start or end with a hyphen.
    • Can start with a numeric.

    For DNS alias names, Amazon FSx stores alphabetic characters as lowercase letters (a-z), regardless of how you specify them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes.

    *)
  2. file_system_id : file_system_id;
    (*

    Specifies the file system with which you want to associate one or more DNS aliases.

    *)
  3. client_request_token : client_request_token option;
}

The request object specifying one or more DNS alias names to associate with an Amazon FSx for Windows File Server file system.