AWS fsx medium security documentation change
Summary
Added documentation about storage classes (SSD/HDD/Intelligent-Tiering), IP address requirements, and Intelligent-Tiering data tiering mechanics. Removed specific encryption implementation details that were previously stated.
Security assessment
The diff removes a paragraph stating that encryption at rest is automatically enabled and that encryption in transit occurs when accessed from supported EC2 instances. This constitutes removal of security documentation, which could lead to misconfigurations if users are unaware of these protections. However, the encryption implementation might still exist - this change only removes the documentation aspect.
Diff
diff --git a/fsx/latest/LustreGuide/using-fsx-lustre.md b/fsx/latest/LustreGuide/using-fsx-lustre.md index 12b8c649c..2a5ed37a2 100644 --- a//fsx/latest/LustreGuide/using-fsx-lustre.md +++ b//fsx/latest/LustreGuide/using-fsx-lustre.md @@ -5 +5 @@ -Persistent file systemsDeployment type availability +Persistent file systemsIP addressesFSx for Lustre storage classesHow the Intelligent-Tiering storage class tiers dataDeployment type availability @@ -7 +7 @@ Persistent file systemsDeployment type availability -# Deployment options for FSx for Lustre file systems +# Deployment and storage class options for FSx for Lustre file systems @@ -9 +9 @@ Persistent file systemsDeployment type availability -Amazon FSx for Lustre provides two file system deployment options: **persistent** and **scratch**. +Amazon FSx for Lustre provides two file system deployment options: **persistent** and **scratch**. It provides three storage classes: **SSD** (solid state drive), **Intelligent-Tiering** , and **HDD** (hard disk drive). @@ -11,3 +11 @@ Amazon FSx for Lustre provides two file system deployment options: **persistent* -You choose the file system deployment type when you create a new file system, using the AWS Management Console, the AWS Command Line Interface (AWS CLI), or the Amazon FSx for Lustre API. For more information, see [Step 1: Create your FSx for Lustre file system](./getting-started.html#getting-started-step1) and [CreateFileSystem](https://docs.aws.amazon.com/fsx/latest/APIReference/API_CreateFileSystem.html) in the _Amazon FSx API Reference_. - -Encryption of data at rest is automatically enabled when you create an Amazon FSx for Lustre file system, regardless of the deployment type you use. Scratch 2 and persistent file systems automatically encrypt data in transit when they are accessed from Amazon EC2 instances that support encryption in transit. For more information on encryption, see [Data encryption in Amazon FSx for Lustre](./encryption-fsxl.html). +You choose the file system deployment type and storage class when you create a new file system, using the AWS Management Console, the AWS Command Line Interface (AWS CLI), or the Amazon FSx for Lustre API. For more information, see [Step 1: Create your FSx for Lustre file system](./getting-started.html#getting-started-step1) and [CreateFileSystem](https://docs.aws.amazon.com/fsx/latest/APIReference/API_CreateFileSystem.html) in the _Amazon FSx API Reference_. @@ -17 +15 @@ Encryption of data at rest is automatically enabled when you create an Amazon FS -_Persistent file systems_ are designed for longer-term storage and workloads. The file servers are highly available, and data is automatically replicated within the same Availability Zone in which the file system is located. The data volumes attached to the file servers are replicated independently from the file servers to which they are attached. +_Persistent file systems_ are designed for longer-term storage and workloads, and the file servers are highly available. For SSD and HDD-based file systems, data is automatically replicated within the same Availability Zone in which the file system is located. For Intelligent-Tiering file systems, data is replicated across multiple Availability Zones. The data volumes attached to the file servers are replicated independently from the file servers to which they are attached. @@ -29 +27 @@ Amazon FSx for Lustre supports two persistent deployment types: Persistent 1 and -Persistent 2 is the latest generation of Persistent deployment type, and is best-suited for use cases that require longer-term storage, and have latency-sensitive workloads that require the highest levels of IOPS and throughput. Persistent 2 deployment types support higher levels of throughput per unit storage (that is, 125, 250, 500, and 1000 MBps/TiB), higher metadata IOPS (if you specify a metadata configuration), and higher throughput per client (if you enable EFA support), compared to Persistent 1 file systems. +Persistent 2 is the latest generation of Persistent deployment type, and is best-suited for use cases that require longer-term storage, and that require the highest levels of IOPS and throughput. Persistent 2 file systems support SSD and Intelligent-Tiering storage classes. @@ -31 +29 @@ Persistent 2 is the latest generation of Persistent deployment type, and is best -You can create Persistent 2 file systems with a metadata configuration and EFA enabled using the Amazon FSx console, AWS Command Line Interface, and API. +You can create Persistent 2 file systems with a metadata configuration and EFA enabled using the Amazon FSx console, AWS Command Line Interface, and Amazon FSx API. @@ -35,3 +33 @@ You can create Persistent 2 file systems with a metadata configuration and EFA e -The Persistent 1 deployment type is well-suited for use cases that require longer-term storage, and have throughput-focused workloads that aren't latency-sensitive. Persistent 1 deployment types support SSD (solid state drive) and HDD (hard disk drive) storage options. - -For a Persistent 1 file system with SSD storage, the throughput per unit of storage is either 50, 100, or 200 MBps per tebibyte (TiB). For HDD storage, Persistent 1 throughput per unit of storage is 12 or 40 MBps per TiB. +The Persistent 1 deployment type is well-suited for use cases that require longer-term storage. Persistent 1 deployment types support SSD (solid state drive) and HDD (hard disk drive) storage classes. @@ -43 +39 @@ You can create Persistent 1 deployment types only by using the AWS CLI and the A -_Scratch file systems_ are designed for temporary storage and shorter-term processing of data. Data isn't replicated and doesn't persist if a file server fails. Scratch file systems provide high burst throughput of up to six times the baseline throughput of 200 MBps per TiB of storage capacity. For more information, see [Aggregate file system performance](./performance.html#fsx-aggregate-perf). +_Scratch file systems_ are designed for temporary storage and shorter-term processing of data. Data isn't replicated and doesn't persist if a file server fails. Scratch file systems provide high burst throughput of up to six times the baseline throughput of 200 MBps per TiB of storage capacity. For more information, see [Performance characteristics of SSD and HDD storage classes](./ssd-storage.html). @@ -58,0 +55,57 @@ File system size (TiB) | Number of file servers | Availability/durability over o +## IP addresses for file systems + +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 systems using SSD or HDD storage class 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 + +File systems using Intelligent-Tiering storage class File System Type | Throughput per OSS +---|--- +Intelligent-Tiering* | 4000 MBps per OSS + +###### Note + +* Amazon FSx provisions a metadata server for every 12,000 Metadata IOPS on Persistent 2 SSD and Intelligent-Tiering file systems configured with metadata configuration. + +## FSx for Lustre storage classes + +Amazon FSx for Lustre offers solid state drive (SSD), Intelligent-Tiering, and hard disk drive (HDD) storage classes that are optimized for different data processing requirements: + + * The SSD storage class provides low-latency (sub-millisecond) access to your full dataset. The SSD storage class is provisioned, which means that you specify a file system size and pay storage costs for the amount of storage provisioned. Use the SSD storage class for latency-sensitive workloads that require the performance of all-flash storage across all data. + +Persistent 2 file systems with SSD storage support higher levels of throughput per unit of storage (that is, 250, 500, or 1000 MBps per TiB) compared to Persistent 1 file systems. For a Persistent 1 file system with SSD storage, the throughput per unit of storage is either 50, 100, or 200 MBps per TiB. For a Scratch file system with SSD storage, the throughput per unit of storage is 200 MBps per TiB. + + * The Intelligent-Tiering storage class provides fully elastic, intelligently tiered storage. Elasticity means that you pay for the amount of data you store and do not have to specify a file system size. Intelligent tiering means that you automatically pay less to store data that you haven’t accessed recently. This storage class automatically optimizes costs by tiering cold data to lower-cost storage tiers. You can provision an optional SSD read cache for low-latency (sub-millisecond) access to your frequently-accessed data. The Intelligent-Tiering storage class provides the best balance of price and performance for most workloads. Use the Intelligent-Tiering storage class for workloads that are cache-friendly and do not require the performance of all-flash storage across all data. Intelligent-Tiering file systems support throughput capacities in increments of 4000 MBps. + + * The HDD storage class can be used with workloads that need consistent single-digit ms latency across all data. You can provision an optional SSD read cache that is sized to 20% of your HDD storage capacity to provide low-latency access to frequently-accessed data. With HDD storage, you specify a file system size and pay for the amount of storage that you provision. For a Persistent 1 file system with HDD storage, the throughput per unit of storage is either 12 or 40 MBps per TiB. + + + + +For more information about performance of these storage classes, see [Performance characteristics of SSD and HDD storage classes](./ssd-storage.html) and [Performance characteristics of Intelligent-Tiering storage class](./intelligent-tiering-file-systems.html). + +## How the Intelligent-Tiering storage class tiers data + +The Amazon FSx Intelligent-Tiering storage class automatically stores data in three access tiers. It is designed to optimize storage costs by automatically moving data to the most cost-effective access tier, without performance impact or operational overhead. The Intelligent-Tiering storage class automatically tiers data based on last access time, thus automatically optimizing costs for less active data: + + * Data accessed in the last 30 days is stored in the Frequent Access tier. + + * Data that hasn’t been accessed in 30 consecutive days automatically moves to the Infrequent Access tier, and costs less than data in the Frequent Access tier. + + * Data that hasn’t been accessed in 90 consecutive days automatically moves to the Archive Instant Access tier, and costs less than data in the Infrequent Access tier. + + + + +When you access data in the Infrequent Access or Archive Instant Access tiers, the data automatically moves back to the Frequent Access tier. All access to non-cached data has the same performance characteristics, independent of the data’s tier, and there are no additional IOPS, retrieval, or transition costs beyond your normal read/write operation costs. + @@ -67,2 +120,2 @@ US East (N. Virginia) | ✓ | ✓ | ✓ -US East (Atlanta) Local Zone | ✓ * (Persistent 125 and 250 only) | | -US East (Dallas) Local Zone | ✓ * (Persistent 125 and 250 only) | | +US East (Atlanta) Local Zone | ✓ * | | +US East (Dallas) Local Zone | ✓ * | | @@ -76 +129 @@ Asia Pacific (Jakarta) | | ✓ | ✓ -Asia Pacific (Malaysia) | ✓ * (Persistent 125 and 250 only) | | +Asia Pacific (Malaysia) | ✓ * | | @@ -83 +136 @@ Asia Pacific (Sydney) | ✓ | ✓ | ✓ -Asia Pacific (Thailand) | ✓ | | +Asia Pacific (Thailand) | ✓ * | | @@ -86 +139 @@ Canada (Central) | ✓ | ✓ | ✓ -Canada West (Calgary) | ✓ * (Persistent 125 and 250 only) | | +Canada West (Calgary) | ✓ * | | @@ -95,2 +148,2 @@ Europe (Zurich) | | ✓ | ✓ -Israel (Tel Aviv) | ✓ * (Persistent 125 and 250 only) | | ✓ -Mexico (Central) | ✓ | | +Israel (Tel Aviv) | ✓ * | | ✓ +Mexico (Central) | ✓ * | | @@ -105 +158 @@ AWS GovCloud (US-West) | | ✓ | ✓ -* These AWS Regions support Persistent-125 and Persistent-250 file systems without EFA enabled. Persistent-500, Persistent-1000, and enabling EFA is not supported in these AWS Regions. +* These AWS Regions support Persistent-125 and Persistent-250 file systems with SSD storage class without EFA.