AWS fsx documentation change
Summary
Updated documentation for FSx for Lustre deployment options, storage classes, throughput configurations, metadata IOPS provisioning, SSD read cache management, and console workflow reorganization. Added details about Intelligent-Tiering storage class and updated step numbering.
Security assessment
The changes primarily focus on storage class options, performance configurations, and console workflow updates. While there are references to encryption and security groups, these are standard configuration elements rather than addressing specific security vulnerabilities. The root squash configuration mention (step 16) is a pre-existing security control without evidence of new security content or vulnerability mitigation.
Diff
diff --git a/fsx/latest/LustreGuide/getting-started.md b/fsx/latest/LustreGuide/getting-started.md index 892fd0efd..ed2e1dc47 100644 --- a//fsx/latest/LustreGuide/getting-started.md +++ b//fsx/latest/LustreGuide/getting-started.md @@ -48,16 +48,3 @@ Besides Amazon Linux 2023, the Lustre client supports the Amazon Linux 2, Red Ha - * Determine which type of Amazon FSx for Lustre file system you want to create, _scratch_ or _persistent_. For more information, see [Deployment options for FSx for Lustre file systems](./using-fsx-lustre.html). - - * Each FSx for Lustre file system requires one IP address for each metadata server (MDS) and one IP address for each storage server (OSS). - -File System Type | Throughput, MBps/TiB | Storage per OSS ----|---|--- -Persistent 2 EFA | 125 | 38.4 TiB per OSS -250 | 19.2 TiB per OSS -500 | 9.6 TiB per OSS -1000 | 4.8 TiB per OSS -Persistent 2 non-EFA | 125, 250, 500, 1000 | 2.4 TiB per OSS -Persistent 1 SSD | 50, 100, 200 | 2.4 TiB per OSS -Persistent HDD | 12 | 6 TiB per OSS -40 | 1.8 TiB per OSS -Scratch 2 | 200 | 2.4 TiB per OSS -Scratch 1 | 200 | 3.6 TiB per OSS + * Determine which type of Amazon FSx for Lustre file system you want to create, _scratch_ or _persistent_. For more information, see [Deployment and storage class options for FSx for Lustre file systems](./using-fsx-lustre.html). + + * Each FSx for Lustre file system requires one IP address for each metadata server (MDS) and one IP address for each storage server (OSS). For more information, see [IP addresses for file systems](./using-fsx-lustre.html#ip-addesses-for-fs). @@ -72 +59 @@ Scratch 1 | 200 | 3.6 TiB per OSS -You create your file system in the Amazon FSx console. +You create your file system in the Amazon FSx console. Note that all FSx for Lustre file systems are built on Lustre version 2.15 when created using the Amazon FSx console. @@ -82 +69 @@ You create your file system in the Amazon FSx console. - 4. Provide the information in the **File system details** section: +Begin your configuration with the **File system details** section. @@ -84 +71 @@ You create your file system in the Amazon FSx console. - * For **File system name-optional** , provide a name for your file system. You can use up to 256 Unicode letters, white space, and numbers plus the special characters **\+ - = . _ : /**. + 4. For **File system name-optional** , provide a name for your file system. You can use up to 256 Unicode letters, white space, and numbers plus the special characters **\+ - = . _ : /**. @@ -86 +73 @@ You create your file system in the Amazon FSx console. - * For **Deployment and storage class** , choose one of the options: + 5. For **Deployment and storage class** , choose one of the options: @@ -88 +75 @@ You create your file system in the Amazon FSx console. - * Choose the **Persistent, SSD** deployment type for longer-term storage and for latency-sensitive workloads requiring the highest levels of IOPS/throughput. _Persistent, SSD_ uses Persistent 2, the latest-generation of persistent file systems. + * Choose **Persistent, SSD** for longer-term storage and for latency-sensitive workloads. With SSD storage, you are billed for the amount of storage that you provision. @@ -90 +77 @@ You create your file system in the Amazon FSx console. -Optionally, choose **with EFA support** to enable Elastic Fabric Adapter (EFA) support for the file system. For more information about EFA, see [Working with EFA-enabled file systems](./efa-file-systems.html). +Optionally, choose **with EFA enabled** to enable Elastic Fabric Adapter (EFA) support for the file system. For more information about EFA, see [Working with EFA-enabled file systems](./efa-file-systems.html). @@ -92 +79 @@ Optionally, choose **with EFA support** to enable Elastic Fabric Adapter (EFA) s - * Choose the **Persistent, HDD** deployment type for longer-term storage and for throughput-focused workloads that aren't latency-sensitive. _Persistent, HDD_ uses the Persistent 1 deployment type. + * Choose **Persistent, Intelligent-Tiering** for longer-term storage. The Intelligent-Tiering storage class provides fully elastic, cost-effective storage that is suitable for most workloads, as well as an optional SSD read cache that provides SSD latencies for reads of frequently accessed data. With Intelligent-Tiering, you are billed for the data you store, depending on the size of your dataset, and do not need to specify a file system size. @@ -94 +81 @@ Optionally, choose **with EFA support** to enable Elastic Fabric Adapter (EFA) s -Optionally, choose **with SSD cache** to create an SSD cache that is sized to 20 percent of your HDD storage capacity to provide sub-millisecond latencies and higher IOPS for frequently accessed files. +Optionally, choose **with EFA enabled** to enable Elastic Fabric Adapter (EFA) support for the file system. @@ -96 +83 @@ Optionally, choose **with SSD cache** to create an SSD cache that is sized to 20 - * Choose the **Scratch, SSD** deployment type for temporary storage and shorter-term processing of data. _Scratch, SSD_ uses Scratch 2 file systems. + * Choose **Scratch, SSD** deployment for temporary storage and shorter-term processing of data. With SSD storage, you are billed for the amount of storage that you provision. @@ -98 +85 @@ Optionally, choose **with SSD cache** to create an SSD cache that is sized to 20 - * Choose the amount of **Throughput per unit of storage** for your file system. This option is only valid for **Persistent** deployment types. + 6. Choose the amount of throughput for your file system. You pay for the amount of throughput that you provision. @@ -100 +87 @@ Optionally, choose **with SSD cache** to create an SSD cache that is sized to 20 -_Throughput per unit of storage_ is the amount of read and write throughput for each 1 tebibyte (TiB) of storage provisioned, in MBps/TiB. You pay for the amount of throughput that you provision: + * For Persistent SSD storage, choose a **Throughput per unit of storage** value. _Throughput per unit of storage_ is the amount of read and write throughput for each 1 tebibyte (TiB) of storage provisioned. @@ -102 +89 @@ _Throughput per unit of storage_ is the amount of read and write throughput for - * For Persistent SSD storage, choose a value of 125, 250, 500, or 1,000 MBps/TiB. + * For Scratch SSD storage, choose a **Throughput per unit of storage** value. @@ -104 +91 @@ _Throughput per unit of storage_ is the amount of read and write throughput for - * For Persistent HDD storage, choose a value of 12 or 40 MBps/TiB. + * For Intelligent-Tiering storage, choose a **Throughput capacity** value. @@ -106 +93 @@ _Throughput per unit of storage_ is the amount of read and write throughput for - * For **Storage capacity** , set the amount of storage capacity for your file system, in TiB: + 7. For **Storage capacity** (SSD storage class only), set the amount of storage capacity for your file system, in TB: @@ -112,2 +98,0 @@ _Throughput per unit of storage_ is the amount of read and write throughput for - * For a _Persistent, HDD_ deployment type, this value can be increments of 6.0 TiB for 12 MBps/TiB file systems and increments of 1.8 TiB for 40 MBps/TiB file systems. - @@ -116 +101,5 @@ You can increase the amount of storage capacity as needed after you create the f - * For **Metadata Configuration** , you have two options to provision the number of Metadata IOPS for your file system: + 8. For the metadata configuration, choose one of the following options to provision the number of Metadata IOPS for your file system: + + * Choose **Automatic** (SSD storage class only) if you want Amazon FSx for Lustre to automatically provision and scale the metadata IOPS on your file system based on your file system's storage capacity. + + * Choose **User-provisioned** if you want to specify the number of Metadata IOPS to provision for your file system with SSD or Intelligent-Tiering storage class. Valid values are as follows: @@ -118 +107 @@ You can increase the amount of storage capacity as needed after you create the f - * Choose **Automatic** (the default) if you want Amazon FSx to automatically provision and scale the Metadata IOPS on your file system based on your file system's storage capacity. + * For SSD file systems, valid values are `1500`, `3000`, `6000`, `12000`, and multiples of `12000` up to a maximum of `192000`. @@ -120 +109 @@ You can increase the amount of storage capacity as needed after you create the f - * Choose **User-provisioned** if you want to specify the number of Metadata IOPS to provision for your file system. 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`. @@ -124 +113 @@ For more information about Metadata IOPS, see [Lustre metadata performance confi - * For **Data compression type** , choose **NONE** to turn off data compression or choose **LZ4** to turn on data compression with the LZ4 algorithm. For more information, see [Lustre data compression](./data-compression.html). + 9. For **SSD read cache** (Intelligent-Tiering only), select either **Automatic (proportional to throughput capacity)** or **Custom (user-provisioned)**. With the Automatic option, Amazon FSx for Lustre automatically chooses a read cache size based on your provisioned throughput. If you know the approximate size of your active working dataset, you can select Custom to customize the size of the SSD read cache. For more information, see [Managing provisioned SSD read cache](./managing-ssd-read-cache.html). @@ -126 +115 @@ For more information about Metadata IOPS, see [Lustre metadata performance confi -All FSx for Lustre file systems are built on Lustre version 2.15 when created using the Amazon FSx console. + 10. For **Data compression type** , choose **NONE** to turn off data compression or choose **LZ4** to turn on data compression with the LZ4 algorithm. For more information, see [Lustre data compression](./data-compression.html). @@ -128 +117 @@ All FSx for Lustre file systems are built on Lustre version 2.15 when created us - 5. In the **Network & security** section, provide the following networking and security group information: + 11. In the **Network & security** section, provide the following networking and security group information: @@ -148 +137 @@ All TCP | TCP | 0-65535 | Custom ``the_ID_of_this_security_group`` | Inbound Lu - 6. For the **Encryption** section, the options available vary depending upon which file system type you're creating: + 12. For the **Encryption** section, the options available vary depending upon which file system type you're creating: @@ -156 +145 @@ All TCP | TCP | 0-65535 | Custom ``the_ID_of_this_security_group`` | Inbound Lu - 7. For the **Data Repository Import/Export - optional** section, linking your file system to Amazon S3 data repositories is disabled by default. For information about enabling this option and creating a data repository association to an existing S3 bucket, see [To link an S3 bucket while creating a file system (console)](./create-linked-dra.html#export-path-lustre-console-dra-new). + 13. For **Data Repository Import/Export _optional_** section, linking your file system to Amazon S3 data repositories is disabled by default. For information about enabling this option and creating a data repository association to an existing S3 bucket, see [To link an S3 bucket while creating a file system (console)](./create-linked-dra.html#export-path-lustre-console-dra-new). @@ -164 +153 @@ All TCP | TCP | 0-65535 | Custom ``the_ID_of_this_security_group`` | Inbound Lu - 8. For **Logging -_optional_** , logging is enabled by default. When enabled, failures and warnings for data repository activity on your file system are logged to Amazon CloudWatch Logs. For information about configuring logging, see [Managing logging](./cw-event-logging.html#manage-logging). + * Intelligent-Tiering file systems don't support linking to Amazon S3 data repositories. @@ -166 +155 @@ All TCP | TCP | 0-65535 | Custom ``the_ID_of_this_security_group`` | Inbound Lu - 9. In **Backup and maintenance -_optional_** , you can do the following. + 14. For **Logging _optional_** , logging is enabled by default. When enabled, failures and warnings for data repository activity on your file system are logged to Amazon CloudWatch Logs. For information about configuring logging, see [Managing logging](./cw-event-logging.html#manage-logging). @@ -168 +157 @@ All TCP | TCP | 0-65535 | Custom ``the_ID_of_this_security_group`` | Inbound Lu -For daily automatic backups: + 15. In **Backup and maintenance _optional_** , you can do the following. @@ -170 +159 @@ For daily automatic backups: - * Disable the **Daily automatic backup**. This option is enabled by default, unless you enabled **Data Repository Import/Export** ,. + * Disable the **Daily automatic backup**. This option is enabled by default, unless you enabled **Data Repository Import/Export**. @@ -176 +165 @@ For daily automatic backups: -For more information, see [Protecting your data with backups](./using-backups-fsx.html). + * Set the **Weekly maintenance window** start time, or keep it set to the default **No preference**. @@ -178 +167 @@ For more information, see [Protecting your data with backups](./using-backups-fs - 10. Set the **Weekly maintenance window** start time, or keep it set to the default **No preference**. +For more information, see [Protecting your data with backups](./using-backups-fsx.html) and [Amazon FSx for Lustre maintenance windows](./maintenance-windows.html). @@ -180 +169 @@ For more information, see [Protecting your data with backups](./using-backups-fs - 11. For **Root Squash -_optional_** , root squash is disabled by default. For information about enabling and configuring root squash, see [To enable root squash when creating a file system (console)](./root-squash.html#create-root-squash-console). + 16. For **Root Squash _optional_** , root squash is disabled by default. For information about enabling and configuring root squash, see [To enable root squash when creating a file system (console)](./root-squash.html#create-root-squash-console). @@ -182 +171 @@ For more information, see [Protecting your data with backups](./using-backups-fs - 12. Create any tags that you want to apply to your file system. + 17. Create any tags that you want to apply to your file system. @@ -184 +173 @@ For more information, see [Protecting your data with backups](./using-backups-fs - 13. Choose **Next** to display the **Create file system summary** page. + 18. Choose **Next** to display the **Create file system summary** page. @@ -186 +175 @@ For more information, see [Protecting your data with backups](./using-backups-fs - 14. Review the settings for your Amazon FSx for Lustre file system, and choose **Create file system**. + 19. Review the settings for your Amazon FSx for Lustre file system, and choose **Create file system**. @@ -191 +180 @@ For more information, see [Protecting your data with backups](./using-backups-fs -Now that you've created your file system, note its fully qualified domain name and mount name for a later step. You can find the fully qualified domain name and mount name for a file system by choosing the name of the file system in the **Caches** dashboard, and then choosing **Attach**. +Now that you've created your file system, note its fully qualified domain name and mount name for a later step. You can find the fully qualified domain name and mount name for a file system by choosing the name of the file system in the **File systems** dashboard, and then choosing **Attach**. @@ -333 +322 @@ Setting up -File system deployment options +Deployment and storage class options