Comparing EBS vs. EFS
Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Time
19 hours 19 minutes
Difficulty
Intermediate
CEU/CPE
20
Video Transcription
00:00
>> Hey, everybody and welcome back.
00:00
In this lecture we're going
00:00
>> to be talking about comparing
00:00
>> the differences between EBS and EFS.
00:00
Sometimes there's a confusion between the two,
00:00
and if the previous videos
00:00
that we went through didn't help,
00:00
hopefully this one will answer that big question.
00:00
Learning objectives, we're going to be comparing
00:00
the differences between EBS and EFS.
00:00
Let's go ahead and dive into it.
00:00
EBS volumes can be attached to
00:00
only one instance at a time.
00:00
I remember we talked about this in
00:00
a few lectures earlier in
00:00
this module where we're
00:00
saying this is like a hard drive,
00:00
and just like when you're building a
00:00
computer on your desk,
00:00
you can't put a hard drive and plug it into
00:00
two different computers and have
00:00
both computers leverage the same hard drive.
00:00
Same idea with an EBS volume,
00:00
one EBS volume to one EC2 instance.
00:00
But on the flip side, an EC2 instance
00:00
can have multiple EBS volumes,
00:00
just like a computer can have
00:00
multiple hard drives or
00:00
storage drives that are plugged into it.
00:00
Keep that in mind. EBS volumes
00:00
are locked within an availability zone.
00:00
They require that you take
00:00
a snapshot to rebuild and to renew availability zone,
00:00
the root EBS volumes of the instance,
00:00
they get terminated when
00:00
the EC2 instance gets terminated.
00:00
Keep that in mind,
00:00
but all additional EBS volumes,
00:00
those you would have to terminate manually.
00:00
Now, elastic file system EFS.
00:00
There's no limitation on which
00:00
availability zone it is or how many
00:00
reaches you can do that.
00:00
You can span it out with EBS,
00:00
one availability zone,
00:00
it's designated to that one availability zone.
00:00
But with EFS, you can span out as outside of
00:00
that availability zone if you want to.
00:00
There's no limitation to the number of instances or
00:00
EC2 instances that can be mounted to the EFS.
00:00
This is a network file share.
00:00
So share it,
00:00
it meant to be shared.
00:00
Only can be used for Linux synthesis.
00:00
EBS can be used for all kinds of instances,
00:00
doesn't just have to be Linux.
00:00
EFS is more costly than EBS.
00:00
Remember it's managed,
00:00
so it's going to be more expensive.
00:00
EFS-IA,
00:00
or infrequently access can
00:00
help reduce some of that cost,
00:00
but you're going into
00:00
the IA tier because you're looking to share these files,
00:00
but you probably don't access
00:00
the files as much as you would,
00:00
some local network shares something like that.
00:00
You're not paying as much as you would for the premium
00:00
EFS, but still expensive.
00:00
I know this was a quick one,
00:00
but to quickly summarize,
00:00
in this lecture, we discuss
00:00
differences between EFS and EBS.
00:00
EBS can be used for single EC2 instances,
00:00
EFS is intended to be shared
00:00
out with as many as you
00:00
would like to have it shared with.
00:00
EFS can be used across more than one instance.
00:00
EFS can be used across multiple availability zones,
00:00
EBS locked into the availability zone
00:00
that you built it in.
00:00
With EFS is more expensive,
00:00
If you're using EFS infrequently access or EFS-IA,
00:00
then it's going be a little bit cheaper,
00:00
but that's intended for people that
00:00
don't use the file share as much.
00:00
EFS, fully managed, EBS not managed.
00:00
You got to take care of it yourself.
00:00
That wraps up this lecture.
00:00
I hope you found this helpful.
00:00
If you have any questions, reach out to me,
00:00
I'll point you to some documentation that will help you
00:00
answer some questions if
00:00
you would like to learn more about this.
00:00
Again, documentation is a really good resource for that.
00:00
Make sure that you are leveraging that.
00:00
That wraps up this one.
00:00
In the next lecture we're going to
00:00
conclude this whole thing.
00:00
Wrap this whole lecture or this whole module up,
00:00
and then we're going to move on to
00:00
the next module. I'll see you there.
Up Next
Module 5 Conclusion
6m
S3 Consistency Model
33m
Similar Content
