How you doing and will come back.
Now, in today's video, we are going to discuss about the Amazon elastic file system, also referred
to as FS.
Now, at a high level overview, the Amazon FS provides a simple serverless set and forget elastic file
system for use with the cloud services as well as the on premise resources.
For example, you have the elastic file system on the left.
All you need to do is you have to mount it on top of your easy two instance, and that's about it.
You can store terabytes of data, you can store petabytes of data, it will scale automatically.
So in the second pointer, again, we have added it, which states that it is built to scale on demand
to petabytes without disrupting your application, growing and shrinking automatically as you add and
remove the files.
Now when you make use of FS, you don't really need to worry about what is the storage size that you
will give to FS.
It will automatically grow when you start to add more data and when you start to remove the data, it
will automatically shrink.
So everything is taken by the address itself.
Now one of the great things about the elastic file system is that you can attach it to multiple targets.
It can be easy to instances X, Lambda and various others.
And also note that it can be seen continuously attached to multiple targets and things will work perfectly
well.
So you can also consider it to be some kind of a shared storage which is connected to multiple set of
servers.
So for today's video, I have our elastic file system already available.
So you see the name is demo hyphen FS.
And for today's demo I have created two easy, two instances named easy to instance one and easy to
instance two.
And I have associated this specific file system with both of these easy two instances.
So within my ClA, I am already connected to both of these instances.
One with IP negate 163 second with the IPA ending with 190.
Now if you'll quickly do a DF hyphen here, you see that we have an elastic file system.
This is the exact URL associated with it and it is mounted on this specific part which is root FS,
hyphen, mount hyphen point.
So any data you want to add in your elastic file system, you will add it to this specific folder.
Similarly, in a second server as well.
The overall approach is very similar where you have the elastic file system mounted on this specific
path.
So let's do one thing.
Let's quickly go to route FS Mount Point on both the service.
Alright.
Now from the first step, let's go ahead and quickly create a new file.
I'll say touch followed by server, hyphen one, hyphen file, dot text.
And from our second server let's create a new file as say server hyphen two hyphen file dot text.
Okay.
Now if you do a list over here, you should see that both of these files are listed.
And similarly from the other server, if you do a list again, you will see both of these files are
listed.
So you can say that same storage device is mounted on two different servers and both of the applications
that are running on each of the server in case they will be able to access the shared storage device.
Now, if you'll quickly look into the elastic file system here, you will generally see the URL associated
with it.
So whenever you want to associate this elastic file system in the EC two instance, you can go ahead
and use this URL for the overall mounting.
Now also note that it will also show you the size associated with the data as part of the elastic file
system.
As we already know that the elastic file system can go ahead and scale up whenever you add data and
it can automatically scale down whenever you remove the data.
Now, at a high level overview, whenever you want to access the file system from instances that are
inside the VPC, generally, you will have to create a mount target in the VPC.
So when you have an elastic file system here, you see that there are multiple targets in multiple set
of availability zones and the instances can go ahead and use this target for the oral connectivity.
So when you open up the FS once more, if you go to the network, you see that there are multiple mount
targets in different availability zones.
There are in total of six availability zones in the North Virginia region and you have the mount target
associated with all of them, similar to what we were seeing in the diagram.
Now when we discuss about FS, it is also important for us to understand the basics of network file
system also referred to as NFS.
So NFS is a networking protocol for distributed file sharing.
So if you'll see you have an NFS server and there are multiple disks and depending upon the permission
that you associate, you can go ahead and mount this disk on a set of plans.
And this is similar to how FS also works and at a high level overview, if uses the network file system
protocol.
Now I remember during a Red Hat certification time, I think it was the Red Hat certified engineer.
I did see there was a specific question where there was a network server, this network server had a
disk and we had to mount this specific disk from the NFS server towards the client.
And we also had to restart the set of server to verify the disk remains mounted even if the system gets
restarted.
So very similar in case if we have worked with NFS, FS is very similar in terms of the overall implementation.
Now when we hear that FS can scale up if we add data and it shrinks when we remove data, question that
comes is do we really need another storage?
Because this seems to be very convenient.
And the answer to this is pricing.
So not that FS is quite expensive when you compare it with other storage options like EBS, S3, etc.
for example, one TB of data in FS with 80% frequently accessed data.
Among this it will cost you two $50.
One TB of EBS storage will cost you somewhere around $102 and one TB of S3 storage will cost you $24.
So all comes to pricing and also the use cases for your application.
So before we conclude, let's look into some of the important pointers here.
First one is that if performance is your concern, if you need a very fast performance for your application,
you should not use FS.
You should always pay for EBS.
EBS provides much more better performance when compared to FS.
Second is FS can be accessed from on premises data center as well using the direct connect or VPN connection.
So it's not that FS can be mounted only on EC two instances.
Even if you have servers in your on premise location, you can use FS as well.
And third is with the Amazon FS, you pay only for what you use per month grade.
So that's the high level overview about FS and with this will conclude today's video.