Welcome back to BackSpace Academy. Coming up next. What I'm going to do is 2
run through all of the products and services that are offered on AWS. 3
Now there's an enormous amount of services, so rather than go through them 4
all in one hit I'm going to break it up into a lot of sections and then at the 5
end of each section I'm going to give you an example of how to use those 6
services and then after that we'll do a hands-on session or a lab where you can 7
actually use those services yourself hands-on. So what I need to do now is 8
just give you a very quick introduction to the different types of cloud 9
computing models that are available. Infrastructure as a service it contains 10
the basic building blocks for cloud IT. What that means is that is nuts 11
and bolts stuff. So if we want to launch a Linux server and, we want to manage 12
that Linux server ourselves, that is how we would do that as infrastructure as a 13
service and we would do that using the Elastic Compute cloud or EC2 service. 14
The next level is platform as a service or PaaS and that's where AWS will take a 15
little bit more control over the underlying infrastructure. 16
AWS manages their underlying infrastructure and the hardware and 17
operating system normally and, a good example of that would be the relational 18
database service and, in that service AWS they provision all the operating system 19
the server and everything to run that but, you still need to do the high-level 20
administration of that database, and then finally we've got software as a service 21
or SaS and that is a complete product that normally runs in a browser 22
and it mostly refers to end-user applications. A good example that would 23
be Office 365 or salesforce.com, and you'll hear another term used a lot with 24
AWS and that is serverless computing. 25
That allows you to build and run applications without having to think 26
about servers. You don't need to provision the server yourself AWS will 27
do that for you. It's also referred to as function as a service or abstract 28
services. Examples of that are the simple storage service where we will be using 29
at the end of this lecture where we create a bucket and we put objects and 30
files into that bucket. We don't know what's behind that bucket, obviously 31
there's going to be an operating system, most probably a Linux operating system, 32
a file server. There's going to be hard drives. 33
We don't need to worry about that because AWS they look after all 34
that for us. AWS Lambda is where can run code in the cloud, again without servers. 35
You just provide AWS your code and AWS looks after everything for you. 36
Dynamodb is a NoSQL database in the cloud as a service and, Amazon simple 37
notification service they can send out notifications to your users. 38
So that's a pretty quick introduction of the different types of cloud computing 39
models. The best way to really get a good knowledge of it is to go through all 40
these products, get your hands on with them and then you'll fully understand it 41
a lot better. So there's only one more thing to do and that is let's get into 42
it! 43
Welcome back to BackSpace Academy. In this lecture we're going to run through 44
some of the storage services that are available on AWS. Then we'll look at some 45
examples of how you can use these and finally we'll finish up with a hands-on 46
lab using one of these services, Amazon simple storage service or s3 for short. 47
It's designed to store and access any type of data over the Internet. 48
It's a serverless service and as such we don't need to worry about what is behind it. 49
There's obviously a file server an operating system a hard drive but we 50
don't need to be concerned about that at all. We just simply need to create this 51
thing called a bucket and then we upload objects to that bucket, the bucket grows 52
as we add objects to it and the size of that bucket is theoretically unlimited. 53
AWS just looks after everything for us. 54
Amazon Glacier is the cheapest storage option on AWS and it's used for 55
long-term archiving of data. It's a serverless service just like Amazon s3 but 56
it is not as readily accessible as s3 so it should only be used for content that 57
is to be archived. You can also set up a lifecycle rule that will automatically 58
migrate old data in Amazon s3 automatically over to Glacier for long-term archiving. 59
Amazon elastic block store or EBS for short is a highly 60
available, low latency block storage and it's specifically for attaching to 61
servers that are launched with the Amazon ec2 service. We'll learn more 62
about the EC2 service coming up and it's similar to attaching a hard drive to 63
your computer at home, works in the same manner. It's block device storage. 64
Amazon Elastic file system or EFS for short is network attached storage and it's 65
specifically for Amazon EC2 servers. Because it is network attached store, 66
this allows multiple servers to access one data source in a similar way to NAS 67
on your network at home can be accessed by multiple computers on that network. 68
The AWS Storage Gateway enables hybrid storage between on-premise environments 69
and the AWS cloud. It provides a low latency performance by caching 70
frequently used data on-premises while storing the less frequently data in 71
Amazon Cloud storage services. A Snowball device is a portable, petabyte scale, data 72
storage device that can be used to migrate data and large amount of data 73
from on-premise environments over to the AWS cloud. You simply download your data 74
to the Snowball device, then you send it off to AWS who will then upload that 75
data to an AWS storage service for you. Okay so let's have a look at some 76
examples of using the AWS storage services. In orange there we've got the 77
AWS cloud. Now we can create a VPC inside that AWS cloud and that VPC or virtual 78
private cloud is our own private space within the AWS cloud, and that is an 79
impenetrable fortress against attack and no one will be able to enter our own 80
private space without us allowing that to happen. 81
So let's just say we launched two servers in our VPC now we want these 82
servers to have access to data and somewhere to store that data and so in a 83
normal environment you would just add a hard drive to that server so in the same 84
way we can attach an Amazon Elastic block storage device to our server. 85
So that's great, we've now got high-speed access to our data but, what if we want 86
that data to be available to both of those servers? So here we've only got 87
two EBS volumes. What if we want that data to be on one volume only. 88
So as we know on our computer at home we can't attach a hard drive or a block 89
device hard drive to multiple computers, it just doesn't work like that. 90
So in a situation like that in your home network at home you would just go out and 91
purchase a NAS network attached storage device. You would attach it to your 92
network you would set up your operating system in your desktop computers to have 93
a mount target for that network attached storage so when you go to your G Drive 94
or whatever it is or E drive or F Drive, whatever it is, that will point to that 95
network attached storage. In the same way that we can do that with our network at home, 96
we can do the same thing with AWS. So elastic file system is network 97
attached storage and so that with a mount target can enable multiple servers 98
to access the one data source. Now what if we don't want to worry about mount 99
targets and block devices and all this sort of stuff? 100
We just want somewhere we can upload objects to in a similar way do we do 101
with Google Drive or something like that and we also want to have an automated 102
solution that over time migrates that data over to something more low cost and 103
more long term for archiving now. That is where 104
Amazon s3 comes in and so we can use Amazon s3 to create a bucket, 105
store objects in that bucket, delete objects, do whatever we want with it 106
and we can also set up a lifecycle rule on that bucket so that over a period of time 107
as objects age, they can be migrated over to an Amazon Glacier vault for 108
long-term archiving. It will still be accessible, it just won't be as readily 109
accessible as the s3 bucket, but the advantage is that we'll be using the 110
lowest cost storage that's available on AWS. Now the s3 bucket will be located in 111
the AWS cloud it's not located in our VPC. So remember we said the VPC is our 112
private space within the AWS cloud and nothing gets through it without us 113
allowing it to come through. So that is where the VPC endpoint comes in. So we 114
can create one of those and that will allow traffic to flow in and out of our 115
VPC specifically for that s3 service. So let's have a look at a hybrid storage 116
example, where we've got on-site storage in a corporate data center and we've 117
also got that stored in the AWS cloud in Amazon s3. Why would we do that? 118
Well it's great for a disaster recovery solution because it provides high speed access to 119
our data in our corporate datacenter and at the same time we're taking advantage 120
of the durability and availability of Amazon s3 as a disaster recovery 121
solution. So the first problem that we're going to encounter is that this 122
corporate data center will have petabytes of data and to transfer that 123
over via the Internet to the AWS cloud is not going to be practical. So AWS they 124
can send out to us a Snowball and that is a high-capacity device that 125
can store petabytes of data and so we can upload when we receive that 126
Snowball device from AWS. We can upload our data to that and then we can send 127
that back to AWS and they will upload that for us into the Amazon s3 bucket 128
and so that solves that problem for us. So then we've got to find a solution for 129
making sure that the data in our corporate datacenter is synced with our 130
AWS cloud. Now that's where the AWS Storage Gateway comes in and that will 131
orchestrate all of that for us and so if you have got a high-speed link between 132
your corporate data center and the AWS cloud which you can with the AWS Direct 133
Connect service, you can have the AWS Storage Gateway to orchestrate and 134
manage that all for you and what it will do it will get your popular content, 135
your content that is frequently accessed and it will store copies of that on-site in 136
your on-site storage but at the same time it will store all of that data in 137
an Amazon s3 bucket for you and so then you've got the advantage of having all 138
of the all of the durability and availability of Amazon s3 as a disaster 139
recovery solution but at the same time you've got high-speed access to your 140
data which is cached on the corporate data center Let's have a go at using the 141
Amazon s3 service so what we're going to do now is that we're going to use the 142
AWS management console to connect into the AWS cloud and then we're going to 143
create an Amazon s3 bucket, we're going to upload files to that bucket and then 144
we're going to download files from that bucket, and then finally we're going to 145
empty and delete that bucket. Now there are lab notes for this lab and the 146
further ones coming up make sure that you download the 147
introduction to AWS lab notes that come with this course and let's get into it. 148
Now before we start the lab you need to make sure that you have signed up for an 149
AWS account if you haven't click on the sign up button up here at the AWS 150
website. Once you've completed that signup process make sure that you take 151
note of the email address and password that you use to sign up with. 152
So once that's done you can go to my account and select the AWS management console 153
once you've done that you can login using that email address that you use to 154
create your account and the password that you used as well. So once you do 155
that you'll be into the AWS management console. Okay once we've logged in we'll 156
be at the AWS management console from there we can go to services, and try and 157
find the s3 service now that will be in the storage category. I actually don't 158
like to use these categories because they change quite a bit and when you're 159
looking for stuff it might might be moved into a different category, 160
so it does make life a little bit difficult. The easiest way is to select up in the 161
top right hand corner here is A to Z and then if you're looking for s3 just 162
go to s3 and you'll find it there. Once we've got into the s3 console the 163
first thing we need to do is to create a bucket. Now I've already created quite a 164
number of buckets here for different labs and whatever I've done in the past 165
but yours will be obviously empty, you've never created a bucket and it's a 166
brand new account so your screen here might look a little bit different to 167
mine but there will still be a create button or create bucket button there. 168
We'll click on that and we need to give our bucket a name so I'm just going to 169
put in anything there just a whole heap of rubbish there but you can give it 170
whatever you want to call it. Now a bucket name needs to be unique across 171
AWS so if someone else has actually used that name you can't use it as well 172
so it's a bit like domain names once you've got it no one else can use 173
it after that. 174
So if I, for example if I type backspace - lab or something no doubt that would have been 175
gone. So I'll leave that as it is it's just a whole scramble of letters and 176
we'll click on next. We're not going to worry about versioning or anything like 177
that book just click on next it's going to be a private bucket so only us will 178
only I will have access to this bucket. So we're not going to make a public 179
we're not going to change anything here and next. So that's all we do there it's 180
got our name and region so we're going to be in the US East region and for all 181
of the labs make sure that you are in the US East region it's the largest 182
region and has the most services and when services come out they normally 183
first come out in US East. It's also normally the cheapest region to use as 184
well. So that looks all ok to me. We'll just click on create bucket. If I scroll 185
down I should be able to find that bucket name that I did. There we go. 186
just that scramble of letters there so it will have a link to that bucket so 187
we'll just click on that and there we can see our bucket is empty so our 188
bucket it's simply a repository to dump objects to. It could be files, could be videos 189
could be a whole directory so what we'll do now is we'll upload a 190
folder to this bucket. So we click on upload now, we can click on add files here 191
but I don't like to use that. The easiest way is to drag and drop 192
So you're going to bring it in a folder for example it's much easier to grab the 193
whole folder and just drop it on the form. So that's what I'm gonna do now and 194
we just dropped that whole folder onto that form and we click on next and it's 195
only going to be access for us so it's going to be private. 196
We'll leave that as it is and the storage class, we've got a number of 197
different storage classes depending on what the availability is, how long 198
we're going to be using it, how quickly we need access 199
to it, all this sort of thing. So we're just going to use this standard storage 200
class. We'll click on next and that's just a review screen and we'll click on 201
upload. So there you can see down the bottom it's starting to upload those 202
files at the whole folder with all the files inside of it. So now that has uploaded 203
we can select this folder, open it up and we can download a file, get it 204
back again. So let's do that so we just click on the link in this folder to open 205
up that folder and I'm just going to download these lab notes if I click on 206
those on that link for the lab notes and I just do download that notes and there 207
we go so that's downloading those that PDF. Now I just want to talk about this 208
screen because a lot of people have a bit of trouble with this because instead 209
of clicking on download, they scroll down here and they click on the object URL. 210
Now if we click on that and I'll do that now, this is what you get, access denied 211
so what that is, is you're trying to access through your browser directly to 212
that object and it's a private object, so you can't access it, so if you want to 213
have a file that is accessed like that you need to have it public and you also 214
need to enable web site hosting in Amazon S3. So we'll just get out of that 215
so if you get that screen that's what's happened you click this object URL 216
instead of clicking the download link here. So that brings us to an end now. 217
At the end of all of these labs I like to clean them all up and delete everything 218
that we've done simply because we don't want to get billed for it. So if you're 219
operating on a new account you're going to be getting a free tier and so all of 220
this stuff that we're doing here today will be free and we just need to make 221
sure that we clean it up afterwards. So I'm just going to jump back and click up 222
the top here to the link to that bucket and I'm just going to select that folder 223
I'm going to go to actions and scroll down until I find delete 224
and I'll delete that and now our bucket is empty. So one more thing we can do is 225
we really want to clean this up we can go back into our s3 management console 226
by clicking on Amazon s3 up the top right-hand side or top left hand side 227
and if we scroll down to find that bucket and there it is and then we can 228
just click delete to delete the bucket. So we need to put in the name of 229
the bucket and confirm to delete it so there we go if we have a look for that 230
bucket it's no longer there so that brings us to an end and coming up next 231
we're going to be doing some more looking into some of the services of AWS 232
in particular database services and we're going to be creating a MySQL 233
database and connecting to that database so some pretty cool stuff coming up and 234
I look forward to seeing you in that one.