You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've added support for two new FSx Lustre deployment types
* `SCRATCH_2` - The latest generation of scratch file systems that supports up to six times the baseline throughput for spiky workloads, and supports in-transit encryption of data for supported instance types. With this deployment type, the storage_capacity settings has possible values of 1200 and any multiple of 2400.
* `PERSISTENT_1` - Designed for longer-term storage. The file servers are highly available and the data is replicated within the file systems AWS Availability Zone (AZ), and supports in-transit encryption of data for supported instance types. With this deployment type, the storage_capacity settings has possible values of 1200 and any multiple of 2400.
Added parameters:
* Add `deployment_type` parameter
* Add `per_unit_storage_throughput` parameter
Added IAM parameters:
* `fsx:DescribeFileSystems` This is needed to retreive the FSx MountName from the DescribeFileSystems API
Added Validatations:
* Validate `kms_key_id` and `per_unit_storage_throughput` are only set when `PERSISTENT_1`
* Add FSx Deployment Type Options to the integration tests
* Get FSx MountName from Boto3
* For the new FSx FileSystem Types, the mountname changes from always /fsx to a value returned from the API. This is backwards compatible, so the API returns /fsx for `SCRATCH_1` (current default) filesystems.
Validate Storage Capacity
* If deployment_type == 'PERSISTENT_1' or 'SCRATCH_2' then
storage_capacity can be 1200 GiB, 2400 GiB, or multiples of 2400
* If deployment_type == 'SCRATCH_1' then
storage_capacity can be 1200 GiB, 2400 GiB, or multiples of 3600
Signed-off-by: Sean Smith <[email protected]>
0 commit comments