LustreConfiguration
- class aws_cdk.aws_fsx.LustreConfiguration(*, deployment_type, export_path=None, imported_file_chunk_size_mib=None, import_path=None, per_unit_storage_throughput=None, weekly_maintenance_start_time=None)
Bases:
object
The configuration for the Amazon FSx for Lustre file system.
- Parameters:
deployment_type (
LustreDeploymentType
) – The type of backing file system deployment used by FSx.export_path (
Optional
[str
]) – The path in Amazon S3 where the root of your Amazon FSx file system is exported. The path must use the same Amazon S3 bucket as specified in ImportPath. If you only specify 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. Default: s3://import-bucket/FSxLustre[creation-timestamp]imported_file_chunk_size_mib (
Union
[int
,float
,None
]) – 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. Allowed values are between 1 and 512,000. Default: 1024import_path (
Optional
[str
]) – 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. Must be of the format “s3://{bucketName}/optional-prefix” and cannot exceed 900 characters. Default: - no bucket is importedper_unit_storage_throughput (
Union
[int
,float
,None
]) – Required for the PERSISTENT_1 deployment type, describes the amount of read and write throughput for each 1 tebibyte of storage, in MB/s/TiB. Valid values are 50, 100, 200. Default: - no default, conditionally required for PERSISTENT_1 deployment typeweekly_maintenance_start_time (
Optional
[LustreMaintenanceTime
]) – The preferred day and time to perform weekly maintenance. The first digit is the day of the week, starting at 1 for Monday, then the following are hours and minutes in the UTC time zone, 24 hour clock. For example: ‘2:20:30’ is Tuesdays at 20:30. Default: - no preference
- See:
- ExampleMetadata:
infused
Example:
# vpc: ec2.Vpc file_system = fsx.LustreFileSystem(self, "FsxLustreFileSystem", lustre_configuration=fsx.LustreConfiguration(deployment_type=fsx.LustreDeploymentType.SCRATCH_2), storage_capacity_gi_b=1200, vpc=vpc, vpc_subnet=vpc.private_subnets[0] )
Attributes
- deployment_type
The type of backing file system deployment used by FSx.
- export_path
The path in Amazon S3 where the root of your Amazon FSx file system is exported.
The path must use the same Amazon S3 bucket as specified in ImportPath. If you only specify 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.
- Default:
s3://import-bucket/FSxLustre[creation-timestamp]
- import_path
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.
Must be of the format “s3://{bucketName}/optional-prefix” and cannot exceed 900 characters.
- Default:
no bucket is imported
- imported_file_chunk_size_mib
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.
Allowed values are between 1 and 512,000.
- Default:
1024
- per_unit_storage_throughput
Required for the PERSISTENT_1 deployment type, describes the amount of read and write throughput for each 1 tebibyte of storage, in MB/s/TiB.
Valid values are 50, 100, 200.
- Default:
no default, conditionally required for PERSISTENT_1 deployment type
- weekly_maintenance_start_time
The preferred day and time to perform weekly maintenance.
The first digit is the day of the week, starting at 1 for Monday, then the following are hours and minutes in the UTC time zone, 24 hour clock. For example: ‘2:20:30’ is Tuesdays at 20:30.
- Default:
no preference