Instructor: So AWS is starting to push for hybrid cloud.
And what does hybrid cloud?
That means that part of your infrastructure
is going to be on the cloud of AWS,
and part of your infrastructure
is going to stay on-premises.
And this can be due to multiple reasons,
maybe you have a longer cloud migration,
maybe of security requirements or compliance requirements,
maybe it's part of your strategy to only leverage a cloud
for elastic workloads
but you keep a lot of stuff on-premises.
So we have some services that we really like in AWS,
such as Amazon S3.
Which is a proprietary storage technology
which is unlike EFS, which is an NFS compliance file system.
So how would you expose for example, the S3 data on-premises
and the bridge between this S3
and your on-premises infrastructure
is going to be AWS Storage Gateway.
So if we look at the Storage Cloud Native Options on AWS,
we have Block Storage, which is Amazon EBS
or the EC2 Instance Store.
We have file systems, such as Amazon EFS or Amazon FSX
and we have object level storage,
such as Amazon S3 or Amazon Glacier.
So Storage Gateway is going to bridge your on-premise data
And the cloud in S3.
The use cases of Storage Gateway can be multiple,
for example, disaster recovery, backup and restore
doing tiered storage.
And there are three kinds of Storage Gateway
you need to know about going into the exam.
So there's the File Storage Gateway,
the Volume Storage Gateway and the Tape Gateway.
And the Storage Gateway will then and we'll see those
in details in a second,
import this data into either Amazon EBS,
Amazon S3, or Glacier.
So at the exam, you need to know the differences
between all three types of gateways
and there's a lot of scenarios on it.
So the File Gateway is for you
to have configured S3 buckets being accessible
using the NFS and SMB protocol.
And this supports the kind of storage classes
such as S3 Standard, S3 IA and S3 One Zone IA,
and then the bucket access using IAM roles
for each File Gateway will be secured this way.
And the most recently used data
will be cached in the File Gateway.
So the File Gateway can be mounted
on many servers on-premises
and finally something to know for the exam as well.
If you need user authentication
you can have integration with active directory on-premises
to perform that user authentication.
So let's do a diagram to make it more clear.
The application server we'll be talking
using the NFS protocol V3 or V4.12 to the File Gateway
and then the File Gateway will do the bridge
to the AWS cloud.
So we have S3 Standard and S3 IA
or even Glacier available in the cloud, okay?
The File Gateway will be interfacing
and talking with HTTPS to these buckets in the cloud.
Now, as I said, if you want user authentication
and you have set up Active Directory
then there is an integration between Active Directory
and a File Gateway to provide authentication
at the File Gateway level.
'Cause we can see here, the files are going to be accessible
and extended to Amazon S3.
So this gives you a lot more storage for your file system.
And on top of it, the most commonly used files
are going to be cached onto the File Gateway
which is going to be helpful to have low-latency access
to some files.
So this really gives you a way to expand the size
of your NFS on-premises by leveraging Amazon S3
in the backend.
The second kind of gateway is the Volume Gateway
and this is Block Storage
using the iSCSI protocol backed by Amazon S3.
And the idea is that you will have your volumes
being backed up by EBS snapshots,
which can in turn help you restore on-premise volumes
in case you need to.
So you have two types of Volume Gateway.
You have the Cached Volumes to get low latency access
to the most recent data,
or Stored Volume where the entire dataset is on-premises
and there is a scheduled backup to Amazon S3.
So here our application server needs to be backed up.
And so using this protocol,
we're going to get a Volume Gateway
and the Volume Gateway will create Amazon EBS snapshots
backed by Amazon S3.
So the same logic here, the goal of the Volume Gateway
really is to back up your volumes
of your on-premises servers.
Tape Gateway is that if you have some companies
that have like, for example a tape backup system
using physical tapes then with the Tape Gateway,
uses the same process but the tapes
are going to be backed up in the cloud.
And so this Virtual Tape Library or VTL
is going to be backed by Amazon S3 and Glacier.
You're going to back up existing data
using tape-based process and using the iSCSI interface.
And then this is going to work
with leading backup software vendors.
So diagram you can expect the Corporate Data Center
has a backup server, which is tape-based.
The Tape Gateway will do the interface into the cloud
by storing the tapes into Amazon S3 or in Amazon Glacier.
Finally, if you, as you can see
in all these diagrams from before,
the gateway has to be installed
on your Corporate Data Center,
it has to run within your Corporate Data Center.
But sometimes you do not have virtual servers
to run these additional gateway.
So an option for you is to leverage hardware from AWS.
So it's called Storage Gateway Hardware Appliance.
So if you don't have virtualization on-premises
you can use a Storage Gateway Hardware Appliance
and you can order it literally on amazon.com, okay?
And then once you install this hardware appliance,
so this mini server into your infrastructure
then you can set it up as a File Gateway
or Volume Gateway or a Tape gateway.
And this is really something physical you have to install
and it will have the enough CPU, memory, network
and SSD cache resources to function correctly.
So this is very helpful,
for example for daily NFS backups
in small data centers
where you don't have the virtualization available.
So as a summary for Storage Gateway
read the exam question really well,
it will really hint at which gateway to use.
So if you need to have a bridge
between the on-premise data to the cloud,
Storage Gateway is going to be the answer.
Now if you need a network file system
with optionally some user authentication
with active directory think File Gateway
and the data will go S3 in the backend.
If you need Volumes, Block Storage and iSCSI backup,
use the Volume Gateway and then EBS snapshots
will be created and they will be backed by Amazon S3.
And finally, if you need a Tape solution for backups
use the Tape Gateway.
And if you don't have any on-premises virtualization systems
then you order the Hardware Appliance from source gateway
and install it in your Data Center.
So that's it for this lecture.
I hope you liked it.
And I will see you in the next lecture.