AWS has a range of storage services designed for different scenarios, but there's enough overlap that potential users can struggle to select the best one for the job at hand. Amazon FSx for Windows File Server is the latest example of the challenges that come with so many choices. That may or may not be the case, but our goal here is to sort out the confusion and provide guidance on the usage scenarios for each AWS file service.
It is conceptually analogous to Amazon Relational Database Service. Because FSx runs on Windows, it is compatible with any server application designed for on-premises Windows Server environments.
AWS manages, monitors and patches FSx infrastructure. Its resilient design automatically replicates data within an AZ.
But since the Lustre file system is designed for high-performance computing workloads that typically run on compute clusters, users tend to know when they need it and when they don't.
Editor's note: For the purposes of this article and the comparison to EFS, all other references to FSx will pertain to the Windows variant. In terms of EFS vs. FSx, the key attribute of the former is that it uses NFS, one of the first network file sharing protocols native to Unix and Linux.
Windows has long provided an NFS client and server. FSx supports other Windows security features, such as data encryption at rest and in transit, along with Amazon security services, such as network traffic control using Amazon Virtual Private Cloud security groups and user access policies with Identity and Access Management.
FSx is built for high performance and submillisecond latency using solid-state drive storage volumes. This design enables users to select storage capacity and latency independently. Thus, even a subterabyte file system can have Mbps or higher throughput and support volumes up to 64 TB.
However, the particular scenarios for each primarily differ in how much the applications rely upon native Windows features, as opposed to being able to operate with a generic, OS-agnostic network file system. Those that require Windows-specific features will do better with FSx.
Typical application categories for FSx include:. But EFS is better for applications designed for heterogeneous environments and those that run on Linux systems.When you cancel a task, Amazon FSx does the following.
Creating regular backups for your file system is a best practice that complements the replication that Amazon FSx for Windows File Server performs for your file system. It also enables you to restore from user modification of data. If a backup with the specified client request token exists, and the parameters match, this operation returns the description of the existing backup.
If a backup specified client request token exists, and the parameters don't match, this operation returns IncompatibleParameterError. If a backup with the specified client request token doesn't exist, CreateBackup does the following:.
By using the idempotent operation, you can retry a CreateBackup operation without the risk of creating an extra backup. This approach can be useful when an initial call fails in a way that makes it unclear whether a backup was created. If you use the same client request token and the initial call created a backup, the operation returns a successful result because all the parameters are the same.
You can check the file system creation status by calling the DescribeBackups operation, which returns the backup state along with other information. 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.
A value that specifies the TagKeythe name of the tag. Tag keys must be unique for the resource to which they are attached. A value that specifies the TagValuethe 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.
The response object for the CreateBackup operation. Metadata of the file system associated with the backup. This metadata is persisted even if the file system is deleted.
The AWS account that created the file system.AWS storage costs are complex, and are scattered in multiple places on the Amazon website. We collected the most pertinent pricing information and condensed them into several easy to read tables, to help you gain a quick understanding of your storage costs in the most common scenarios. Amazon provides several popular cloud storage services.
We briefly review them below, and in the following section explain their pricing structure in more detail.
Designed for workloads that require persistent storage accessible by single EC2 instances. Can scale elastically to petabytes. Provides shared access to data across thousands of Amazon EC2 instances. Amazon S3 The popular object storage service designed to store and access any type of data. Provides Can be used for backup and archiving, user-generated content, and as a data lake for big data scenarios.
It provides low-cost cloud storage for archiving and long-term backupwith additional charges for data retrieval. Additional Storage-Related Services The following are additional storage services we will not cover in-depth in this article:. Amazon storage pricing is complex.
Unless specified otherwise, all the pricing shown is for the US East N. Virginia region. Amazon pricing changes frequently. Consult the official pricing page for the latest prices. Prices are different for each of five types of EBS storage units. AWS EFS provides three storage classes, with an option to limit bandwidth when accessing EFS file shares or pay separate for a specific amount of provisioned throughput, which lets you use more bandwidth.
To learn more about these options, see our article on EFS performance. Price per GB-month, with a fee charged each time you read from or write to a file. Price per MB-month, provision the throughput of your file system and pay separately for storage and throughput. S3 pricing is a bit complex, and is broken down into storage costs, payment per data requests, and data transfer costs.
In addition, there are management and data replication costs which we have not detailed below. S3 charges for objects stored in buckets per GB, with a volume discount for larger data quantities. Pricing differs for two storage tiers:. Requests In addition to storage space, S3 charges for requests made on objects stored in your S3 buckets.
Data Transfer The final component of S3 pricing is for data transfer in and out of S3. There are a few exceptions, for which you do not need to pay for bandwidth: data transferred in from the internet, data transferred to EC2 when in the same AWS region, and data transferred to AWS CloudFront content delivery network. There are several Amazon storage tiers you can use to save storage costs for less-frequently-used data.
There are additional charges for requests and data transfers out of Amazon Glacier. Data access options Amazon Glacier provides three options for access to archives, with different pricing for each option:.
Want to get started?
AWS Storage Costs: All in One Place
Cloud Central. Feb 5, AM.There are no minimum fees or set-up charges.
You pay for the storage and throughput capacity that you specify for your file system, and for any backups of your file system. Standard data transfer fees apply for inter-AZ or inter-region access to file systems. You pay for the average amount of storage provisioned for your file systems per month, measured in gigabyte-months "GB-Months", as shown in the pricing example.
Throughput capacity: The price of throughput capacity depends on the deployment type single-AZ or multi-AZ you choose for your file system. For multi-AZ file systems, the cost to transfer data between Availability Zones for replication of data is included in the throughput capacity price. Backups: Backups—both automatic and user-initiated—incur backup storage charges. Backups are incremental, which means that only the changes after your most recent backup are saved, so you save on storage costs by not duplicating data.
Amazon FSx also supports Data Deduplication, which reduces costs associated with redundant data by storing duplicated portions of your files only once.
Typical savings are as follows:. Virginia Region. Assume you have an average backup storage of 5 TB during the month. Pricing calculator. Learn how to get started. Sign up for a free account.
Amazon FSx for Windows File Server: Should You Consider It?
Start building in the console.This domain was used for user authentication and authorization as well as for enforcing corporate policies, auditing, and other tasks. However, this setup was most commonly employed with on-premises servers, and, while it was simple to use, it had limitations.
For example, each time you were about to run out of space, you had to expand your resources to accommodate more data—a time-consuming process which necessitated acquiring and setting up new hardware.
You also had to think about licensing and maintaining your Windows operating system. Altogether, the total cost of ownership for running file shares on-premises was significant.
The impact of these limitations prompted Amazon to release a fully managed solution called Amazon FSx. Amazon FSx is a service that provides file systems for various workloads, such as storage for Windows applications, machine learning, electronic design automation, and high-performance computing. FSx is a fully managed service, so the provisioning of hardware, configuration, and backups are all handled by Amazon behind the scenes. Amazon FSx also supports file systems for Lustre.
It relies on SSD storage and performs quickly, with high levels of IOPS and throughput, as well as consistent sub-millisecond latencies. Additionally, all data is encrypted both in transit and at rest, and all activities are logged to CloudTrail. With Amazon FSx for Windows File Servers, you pay for your defined storage and throughput capacity and for any backups you create.
They are incremental, and this can help you keep costs down. These backup costs are high—almost twice the cost of storing data in S3. This is not surprising, considering that Amazon FSx is less than a year old, and a price correction typically occurs with newer services sometime after their release.How to Create Trust Between AWS Managed Active Directory and On-Premises Active Directory
Assuming FSx follows this trend, these prices should decrease in the near future. It is important to note that, unlike EFSwhich charges you for the storage you are actually using, Amazon FSx for Windows File Server charges you for provisioned capacity. This means that you should be careful when provisioning FSx in order to avoid unnecessary overspending.
Before you create your file systems using Amazon FSx, you must make sure that you have an Active Directory AD to use for authentication. You are now ready to specify all the necessary information to configure your file system. First, choose a logical name and a storage capacity amount. The minimum you can opt for is GiB, and the maximum is GiB.
You will also need to pick your throughput capacity. Next, you need to establish the network settings. If you choose an incorrect security group, you will not have network access to your FSx file system.
After this, you will be prompted to set the Active Directory settings. Encryption can be left at its default setting. The optional maintenance preferences include the daily automatic backups and the weekly maintenance window. Consider setting your maintenance window during off-hours or weekends. Click on Next, and, after reviewing the settings one more time, click on Create File System. This process will take around 10 to 15 minutes to complete.Amazon FSx provides you with the native compatibility of third-party file systems with feature sets for workloads such as Windows-based storage, high-performance computing HPCmachine learning, and electronic design automation EDA.
Amazon FSx integrates the file systems with cloud-native AWS services, making them even more useful for a broader set of workloads. This compatibility, performance, and scalability enables business-critical workloads such as home directories, media workflows, and business applications. User quotas give you the option to better monitor and control costs. You pay for only the resources used, with no upfront costs, or licensing fees.
High availability: Amazon FSx automatically replicates your data within an Availability Zone AZ it resides in which you specify during creation to protect it from component failure, continuously monitors for hardware failures, and automatically replaces infrastructure components in the event of a failure.
Multi-AZ: Amazon FSx offers a multiple availability AZ deployment option, designed to provide continuous availability to data, even in the event that an AZ is unavailable. Multi-AZ file systems include an active and standby file server in separate AZs, and any changes written to disk in your file system are synchronously replicated across AZs to the standby. Using DFS Namespaces, you can scale performance up to tens of gigabytes per second of throughput, with millions of IOPS, across hundreds of petabytes of data.
User quotas provide tracking, monitoring, and enforcing of storage consumption to help reduce costs.
Amazon FSx for Lustre provides a high-performance file system optimized for fast processing of workloads such as machine learning, high performance computing HPCvideo processing, financial modeling, and electronic design automation EDA. These workloads commonly require data to be presented via a fast and scalable file system interface, and typically have data sets stored on long-term data stores like Amazon S3.
Amazon FSx for Lustre provides a fully managed high-performance Lustre file system that allows file-based applications to access data with hundreds of gigabytes per second of data, millions of IOPS, and sub millisecond latencies. You can then write results back to S3, and simply delete your file system. You can also use FSx for Lustre as a standalone high-performance file system to burst your workloads from on-premises to the cloud.
By copying on-premises data to an FSx for Lustre file system, you can make that data available for fast processing by compute instances running on AWS.
With Amazon FSx, you pay for only the resources you use. There are no minimum commitments, upfront hardware or software costs, or additional fees. Lustre is a popular open-source parallel file system that is designed for high-performance workloads.
These workloads include HPC, machine learning, analytics, and media processing.
A parallel file system provides high throughput for processing large amounts of data and performs operations with consistently low latencies.
It does so by storing data across multiple networked servers that thousands of compute instances can interact with concurrently. Amazon FSx provides high throughput for processing large amounts of data and performs operations with consistent, sub-millisecond latencies.
Amazon FSx for Lustre supports file access to thousands of EC2 instances, enabling you to provide file storage for your high-performance workloads, like genomics, seismic exploration, and video rendering.If you've got a moment, please tell us what we did right so we can do more of it. Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. You can monitor file systems using Amazon CloudWatch, which collects and processes raw data from Amazon FSx for Windows File Server into readable, near real-time metrics.
These statistics are retained for a period of 15 months, so that you can access historical information and gain a better perspective on how your web application or service is performing. Bytes are not rounded to either a decimal or binary multiple of the unit.
The Sum statistic is the total number of bytes associated with read operations during the period. To calculate the average throughput Bytes per second for a period, divide the Sum statistic by the number of seconds in the period.
The Sum statistic is the total number of bytes associated with write operations during the period. The Sum statistic is the count of read operations during the time period. To calculate the average number of read operations operations per second for a period, divide the Sum statistic by the number of seconds in the period.
AWS tries to lure Windows users with Amazon FSx for Windows File Server
The Sum statistic is the count of write operations during the time period. To calculate the average number of write operations operations per second for a period, divide the Sum statistic by the number of seconds in the period.
The Sum statistic is the count of metadata operations during the time period. To calculate the average number of metadata operations operations per second for a period, divide the Sum statistic by the number of seconds in the period. The metrics reported by Amazon FSx provide information that you can analyze in different ways.
Please refer to your browser's Help pages for instructions. Did this page help you? Thanks for letting us know we're doing a good job! Units: Bytes Valid statistics: AverageMinimum. How Do I Determine Relevant Metrics My file system's throughput?