Hello and welcome back.
Now it's time to talk about a new HBO service and that is Amazon Elastic file system or abbreviated
us.
We will learn what it is how it works what our amount targets and why do we need them.
And also we learn about security groups and as they relate to each other.
So let's dive in and find out what if this is all about.
So for us is an elastic find system what does it provide you.
It provides you with politics compliant or Unix based.
Basically file system.
So if you are used to mounting file systems on your Linux servers or instances that is what if this
is going to provide to you.
So that's a highly available durable scalable file storage not object storage.
So it's not a replacement for three.
And at the same time it's not drive virtual drive that you can install an operating system and use it.
This is going to provide the file service where the files saved on this file system can be accessed
and can be read or written to from multiple clients and the clients will be on easy two instances or
on premise servers.
So let's go through the text.
So if s provides simple scalable file storage in the cloud for use with easy to or on premise servers
but all have to be Linux because if it is on premise that will be through direct connect connections.
One might ask why not through a VPN.
Think about it.
Now you want to move files back and forth from an IP perspective.
That should be fine.
But from a service perspective it appears once high performance wants that mission of transferring files
from on premise to each of us to be highly reliable and performance.
Right.
And that's why Direct Connect is the main one recommended by abuse with Amazon.
If yes applications have the storage they need when they need it.
So it is elastic.
OK.
So what do I need to state at the beginning with a 10 gig or one tier or petabytes.
You don't have to just store files and it grows.
It stretches as you store files and you will be built based on usage airfares storage capacity is elastic
growing and shrinking automatically as you add and remove files.
It has a simple Web services interface.
So when you go to the ESF service in Italy as console you will easily be able to create file systems
and use them as you need.
And that simple interface will allow you to create and configure file systems quickly and easily.
Do you need to worry about what the underlying infrastructure that's not yours that's managed by it
obvious for you and by using f us you are avoiding the complexity of patching configuring creating deleting
file systems in the cloud.
So if we look quickly at the drawing we have multiple Availability Zones in one Italy s region and this
multiple Availability Zones they can use a file system by mounting a file system to easy two instances
we we're going to talk about the amount targets and it is going to use NF s or network file system Protocol
Version 4 and also supports version four point one.
And the DCP port so all the communication between the AC two instances and the amount targets as we
learn later on our DCP IP based on Port 2049.
The service itself each of us is designed to be highly scalable highly available and highly Europe so
you don't need to worry about data to be lost.
You don't need to worry about a single failure in within the database infrastructure that will take
down your file system.
Amazon if first file system store data and meta data so not only your files but the meta data all the
files of course multiple Availability Zones in an obvious region.
Remember when we were talking about UBS UBS.
If you are using it locally on an easy to instance what will happen.
It's limited to an availability zone in each of us.
Your data is already in multiple of any citizen in the region.
If it's file systems can grow two petabytes scale.
As we mentioned it can drive high levels of throughput and it will allow massively parallel access from
Amazon to instances to your data.
So multiple instances can use that if as file system at the same time as opposed to e-business where
it's only one instance that can have that UBS attached to it at a time.
Amazon he feels provides file system access semantics such as strong data consistency and file looking
and we'll talk about that in more detail later on.
It is limited to Linux instances why as we mentioned it is POS X compliant and that's why it requires
Linux or Unix based operating system.
And for some eyes there are some NFA s client tools that you need to install on the AC two instances
in order to be able to mount that to each of us.
So as we mentioned it supports the little file system version four point one and 4.0 and that will be
the protocol that can be between the instance and the amount targets.
So the applications and tools that you are going to use on your easy two instances or on premise servers
today with any other five system are going to be the same that you use them with Amazon airfares basically
migrating to ESFS is all about migrating your files and it should be the same protocol that you used
with your NF S. based file system multiple Amazon you two instances in the same region in the same VPC
an indifferent availability zones so they could be in the set so they are in the same region in the
same VPC but they could be in different availability zones as we have here a b and c they can access
the if as file system at the same time.
And this will provide a common data source so the files if they are all or the application on all these
they need it they will find these files available for them on the file system.
So it's a common data source for workloads and applications running on more than one instance or server
so it can be accessed from on premise and from on NWS instances or servers at the same time and you
can mount an Amazon airfares file system on instances in only one VPC at a time.
So I haven't.
If as instances a file system can that be served by VPC 1 and VPC 2 at the same time.
The answer is no.
So let's talk now about mon targets.
What are these blue rectangles.
The easy two instances will use them in order to connect to the if a service or the file system that
I have created.
How can that happen.
So the amount targets are no more than Ian eyes that will be launched in your VPC when you create them.
So as are configuring you have to define which VPC you cannot just say that I want to create a file
system that will be everywhere.
So you select a VPC from your VIP is and then the next step will be define which availability zones
you want mount targets to be installed at or fixed at and what anybody else will do it will introduce
in ice elastic network interfaces.
These are the amount targets so they have IP addresses from the subnet where you can choose to be created
and they will take the IP addresses and they will be accessible to your instances using IP or disappear
IP protocol.
Fine.
Is that all what I need to do.
No.
There is a security group considerations that will talk about shortly.
So to access your Amazon your first file system in a VPC you create one or more mound targets in the
VPC.
Okay I have three availability zones.
Do I need one in each availability zone.
No you can create one in any availability zone and you can reach it from the other subnet but other
subnets in the other availability zones.
But this is not recommended by.
Yes.
So what do I do.
It is recommended by GW that you have one mount target in each availability zone.
How about if I have multiple subnets in an availability zone.
Do I need to create more than one.
No.
One is enough and the amount target in itself is highly available so you don't need to worry about that
mount.
Target failing and then you will not have access to it.
So to access that you need to install amount targets and the main target will provide an IP address
for NSF V4 in point at which you can mount an Amazon.
If as filesystem you mount your file system using DNS names which resolves the IP address of the ESFS
mount target in the same availability zone as your easy to answer so you can provide the file system
name and then the mounting will happen as you go with a command Linux command.
You can create only one mount target in each of ageism so it's only one and it is recommended but it
really has to have one in each available it is known that you are going to use if there are multiple
subnets in and if anybody's on in your VPC you create a mound target in one of those objects only one
then only see two instances in that celebrities on even the ones in different subnets can reach out
using IP to these mound target you can mount an Amazon if file system in your VPC through NF s.
As we mentioned and mound targets you don't need to air about their failures.
They are in themselves highly available now.
I went on into the operating system the Linux operating system and I applied the mount command for that
file system into my is it or onto my easy to instances.
Then what.
Then it becomes a directory as you name it while you are doing that it will become a directory that
you can use as any other Unix directory so you can upload files copy files make directories or some
directories.
So on and so forth.
One thing to note that the IP addresses and the DNS names for your amount targets and availability zone
are static so they're not dynamic.
They're not keep changing.
They're all the same.
And keep this in mind when you designed for high availability and feel overs to other Availability Zones.
So if your application tries the Mount target on available it is on one and cannot.
It can fail over to another Liberty Zone.
What does a W recommend.
It obviously commands that you create mon targets in all the availability zones.
So you can easily mount the file system on easy two instances that you might launch in any of the related
zones.
How about if I'm not using it now I haven't availabilities on I'm not launching an easy two instances.
Why don't you create them on target and use it later on you're not being charged for the wrong target.
Security Group considerations.
Remember when I said that NF S. is going to be used between the amount target war between DC and I and
you're easy to instance in ISO that will be the IP routing back and forth between them in the same subnet
or in different subnets based on where the mouse target is and where the easy to instance is fine but
the Eon I as we know any and I need be US will have a security group attached to it.
So this rectangle that is red and black.
Same thing here.
These are security groups.
So these security groups must allow the traffic going out from here to there an eye of the Mount target
and that security group in the Mount target should allow that traffic inbound if the outbound from here
is allowed and the inbound here is allowed.
The response will be allowed automatically and this association or mounting will happen.
And then you can use it freely.
What if one of the security groups does not allow the traffic the mounting will not happen and you will
not be able to use it as simple as that.
So imagine as if these are too easy two instances that Id like to communicate and apply the same that
we learned of applying security groups of different easy to instances.
So both the easy to instance and amount target need to have associated security groups and the security
groups act as a virtual firewall as we know.
And you can use the security groups you associated with the amount target to control inbound traffic.
So can I reference here in this security group as the source the security group off the easy to instance.
Yes you can.
So you can do it by the side there block or the subnet and you can do it also by the name of the security
group.
All right.
So let's take a break.
I will see you after the break.
Thank you.