AWS live blog post from Storage Field Day

Here’s my 2nd post from Storage Field Day – AWS live blog post.


In this section we got some of the business reasons to use AWS managed file services. For example, some customers want to move to cloud for file service because they don’t want to deal with the on-prem hardware anymore (procuring and managing the file infrastructure.

Others want to create their entire ecosystem in cloud without the headaches like backups patches, licensing, etc. That way they deal w what’s important to biz.

ML, genome, health care system, fin risk apps, general purpose file

FSx for popular file systems

Amazon EFS (elastic file system) was the native born in cloud file system. Thee solutions make it easy to migrate workloads to the clouds. You won’t have to do another migration again because AWS manages the hardware.

For example, There is FSx on Netapp for Netapp customers, Windows FSx for general purpose win servers, or even for VMware servers, FSx Microsoft for customers who want to self-mange windows.

Time to Result is the big measurement for their customers (or and AWS).

Amazon File Cache

This is a native service that’s pretty configurable, it went GA 9/29 this year. Some use cases are:

  • Media and entertainment
  • HPC
  • AI/ML
  • Unify datasets in a single view
  • FsX for Open ZFS
  • Lustre (fully managed that you can connect to your S3 buckets)


S3 has 11 9s durability. The Availability Zones within a region are always 10 – 60 miles apart (for resiliency). S3 has moved from eventual consistent to strongly consistent.

There are 5 classes, but it’s important to think about all the costs involved (get ready for finops!). The price varies based on how much the data is accessed, and since it’s lower you will pay for puts and gets.

Storage lens

Used for visibility. There are 15 free metrics, and 14 advanced. The free level is available by default for each customer. When you turn it on you’ll see 2 weeks of the most current data automatically.

Two common errors are 500 and 503, but refreshing usually fixes those

S3 backups

I asked questions in this section sorry. Make sure to watch the video when it posts! I will say that the messaging and the way AWS is are doing data protection is very different.