1
00:00:00,960 --> 00:00:07,790
Come back this is domain number five the storage options or the storage services in the US.

2
00:00:08,370 --> 00:00:13,350
And we are going to start with some research or service or three.

3
00:00:13,500 --> 00:00:20,220
This is not planned to be started from scratch or a 0 2 here on S-3 So it assumes that you already have

4
00:00:20,730 --> 00:00:26,040
the associate level knowledge about S-3 you know what S-3 is what an S3 bucket is worth as an object

5
00:00:26,070 --> 00:00:27,520
and so on and so forth.

6
00:00:27,870 --> 00:00:33,680
This is going to stress on features of S3 that are important and relevant to that exam.

7
00:00:33,690 --> 00:00:39,980
So just to set expectations right please do a quick review for the s 3 knowledge that you have had before.

8
00:00:40,230 --> 00:00:48,120
And let's get into stressing or reinforcing what the features are and how important they are when we

9
00:00:48,120 --> 00:00:49,990
use them and for the exam as well.

10
00:00:50,130 --> 00:00:53,960
So let's dive in and find out what we have in the last couple of lectures.

11
00:00:53,970 --> 00:01:00,150
Versioning is important when you would like to keep different versions of your files or when you want

12
00:01:00,240 --> 00:01:05,440
to give yourself a second chance so let's say you edit a file you uploaded that to the bucket and it

13
00:01:05,440 --> 00:01:07,210
is not in every version what will happen.

14
00:01:07,260 --> 00:01:10,350
The new one that you're uploading will override the old one.

15
00:01:10,350 --> 00:01:13,830
If they have the same key or the same name if you don't want that to happen.

16
00:01:13,860 --> 00:01:20,760
And at the same time or you want to keep versions of the file so you can do versioning of the file and

17
00:01:20,760 --> 00:01:24,120
you can keep track of what changes happen between the different versions.

18
00:01:24,240 --> 00:01:26,380
Then you enable bucket version.

19
00:01:26,460 --> 00:01:30,560
So bucket version is S3 bucket Sabri source.

20
00:01:30,630 --> 00:01:37,890
It is used to protect against accidental object or data deletion or overwrite version can also be used

21
00:01:37,890 --> 00:01:39,980
for data retention and archive.

22
00:01:39,990 --> 00:01:41,500
So I will keep versions.

23
00:01:41,530 --> 00:01:47,190
But I mean starting and keep let's say for vergence can't and anything older than four versions will

24
00:01:47,190 --> 00:01:52,530
be archived so I can use it later on for other things or for any other purposes.

25
00:01:52,650 --> 00:01:57,360
Once you are unable to back it versioning on a bucket it cannot be disabled but it can be suspended

26
00:01:57,390 --> 00:02:03,000
and we'll discuss what happens when you suspend versioning on a bucket that had it enabled before when

27
00:02:03,000 --> 00:02:03,620
enabled.

28
00:02:03,690 --> 00:02:07,540
But that version will protect existing and new objects.

29
00:02:07,560 --> 00:02:12,000
So if I had the bucket and the bucket already had objects before the Enable versioning.

30
00:02:12,030 --> 00:02:19,140
Once you enable it then both the existing and the new objects that you will upload to the bucket will

31
00:02:19,140 --> 00:02:26,310
be protected or we'll have versioning effective on them and it will start maintaining versions as these

32
00:02:26,310 --> 00:02:33,520
objects the existing ones or the new ones are updated edited right into how can you update objects.

33
00:02:33,690 --> 00:02:38,290
These are all HTP actions like the pupils to copy and delete action.

34
00:02:38,290 --> 00:02:41,490
So these are all etched ETP delete markers.

35
00:02:41,490 --> 00:02:48,030
So let's say I have a bucket the bucket has all objects uploaded to it and I enabled versioning on the

36
00:02:48,030 --> 00:02:50,280
bucket when you tried to delete an object.

37
00:02:50,430 --> 00:02:51,500
What happens to that.

38
00:02:51,510 --> 00:02:58,880
I would do an HDTV delete four object ABC 2:59 this object doesn't get deleted permanently.

39
00:02:58,980 --> 00:03:03,750
So when you do that the file will be merged with a delete marker.

40
00:03:03,780 --> 00:03:05,820
So the file will not be deleted immediately.

41
00:03:05,850 --> 00:03:12,420
It will have a delete marker on it from the object can still view that version or that the file.

42
00:03:12,420 --> 00:03:15,860
Yes you can still view the object and the delete marker.

43
00:03:15,890 --> 00:03:21,900
Now let's say I did that by mistake and I have the delete marker is not deleted permanently.

44
00:03:21,900 --> 00:03:28,380
Can I reconsider deleting the object if it was a mistake can I just remove that delete marker and then

45
00:03:28,380 --> 00:03:30,180
make the object available again.

46
00:03:30,180 --> 00:03:30,930
Yes you can.

47
00:03:30,990 --> 00:03:31,710
You can do that.

48
00:03:31,740 --> 00:03:32,920
You will be charged.

49
00:03:32,940 --> 00:03:39,240
And that's one thing to note that if you have any versioning it's cute and neat feature that you can

50
00:03:39,240 --> 00:03:42,420
use comes in handy protect your files and all that.

51
00:03:42,420 --> 00:03:44,300
But this is all storage right.

52
00:03:44,310 --> 00:03:51,610
The more versions you store the more size you are using of a street the more cost will be there as well.

53
00:03:51,780 --> 00:03:56,590
So we need to have a strategy as to how many versions you can keep and for how long.

54
00:03:56,700 --> 00:03:58,200
So this is very important as well.

55
00:03:58,320 --> 00:04:02,610
So you can use versioning with something we call S-3 lifecycle policy.

56
00:04:02,610 --> 00:04:08,280
You can have a policy to decide what to do with the objects that do delete them do you archive them

57
00:04:08,280 --> 00:04:11,180
to a cheaper storage what exactly you want to do with that.

58
00:04:11,370 --> 00:04:17,430
So you can combine versioning with lifecycle policies and both are sub resources to as a three bucket

59
00:04:17,730 --> 00:04:21,780
in order to either delete them or move them to a cheaper storage.

60
00:04:21,780 --> 00:04:24,580
Glacier is one example and I'll talk about it later on.

61
00:04:24,570 --> 00:04:27,050
That's the archiving of it.

62
00:04:27,080 --> 00:04:28,830
Yes but it virginals state.

63
00:04:28,830 --> 00:04:33,850
So if you have a bucket from a versioning standpoint what are the possible states for that bucket.

64
00:04:34,020 --> 00:04:41,220
It's either version is enabled on the bucket or it was enabled and you suspended it or it was an inversion.

65
00:04:41,220 --> 00:04:46,530
So this is the the initial one when you enable versioning you get to that enabled if he's suspended

66
00:04:46,530 --> 00:04:51,840
you going to spend suspended state versioning applies to all objects in a bucket and not personally

67
00:04:51,840 --> 00:04:52,200
applied.

68
00:04:52,200 --> 00:04:59,130
So if I have a bucket and I have multiple objects can I say I want this object to be version but I don't

69
00:04:59,250 --> 00:05:00,690
care about this one or that one.

70
00:05:00,690 --> 00:05:04,060
No it's across the bucket the entire bucket.

71
00:05:04,110 --> 00:05:11,850
Either it's all Virgine or it's all virgin or suspended objects existing before enabling versioning.

72
00:05:11,940 --> 00:05:19,170
Have a virgin ID of null case or any version of the object that you upload before enabling versioning

73
00:05:19,260 --> 00:05:20,150
on your bucket.

74
00:05:20,160 --> 00:05:23,230
It will have a version ID of none.

75
00:05:23,430 --> 00:05:29,570
If you have a bucket that is already divergent then you suspend versioning existing objects and their

76
00:05:29,580 --> 00:05:31,070
versions remains as is.

77
00:05:31,110 --> 00:05:32,220
So I have this bucket.

78
00:05:32,220 --> 00:05:33,900
It was version it was enabled.

79
00:05:33,900 --> 00:05:38,790
And then I went and suspended that and changed the state change it into suspended.

80
00:05:38,790 --> 00:05:43,710
What happens to the objects that I had and their versions of these objects.

81
00:05:43,800 --> 00:05:50,600
They are as is now what will happen if I upload a new version of an existing object.

82
00:05:50,670 --> 00:05:54,390
After the versioning was suspended what happens to this one.

83
00:05:54,750 --> 00:05:58,440
And what happens if I upload new ones.

84
00:05:58,440 --> 00:06:00,060
Can I delete.

85
00:06:00,090 --> 00:06:03,480
Let's see that in our next slide.

86
00:06:03,510 --> 00:06:08,660
One thing to add before we move to the next line is if you have an object with its versions and you

87
00:06:08,760 --> 00:06:14,730
suspended versioning the object on the verge of women as is however they will not be updated or version

88
00:06:14,730 --> 00:06:16,620
further with future updates.

89
00:06:16,650 --> 00:06:20,810
So what will happen then when I upload a new version to the bucket.

90
00:06:20,820 --> 00:06:26,460
This is what we'll see in our next light while the bucket version is suspended.

91
00:06:26,460 --> 00:06:29,580
What happens to the new object I'm going to upload.

92
00:06:29,820 --> 00:06:34,180
New objects uploaded will have a version ID of nothing.

93
00:06:34,260 --> 00:06:40,720
Now if I uploaded an object and it has an object id of NULL and then I upload a new version.

94
00:06:40,720 --> 00:06:44,440
What will happen it will override the existing one.

95
00:06:44,660 --> 00:06:50,220
So in this complete object over an object deletion in a suspended version bucket will only lead the

96
00:06:50,220 --> 00:06:51,800
object with ID.

97
00:06:51,910 --> 00:06:59,250
And if you delete totum if it delete if I need to protect my files and my file versions on my object

98
00:06:59,250 --> 00:07:01,140
versions from being deleted.

99
00:07:01,140 --> 00:07:06,310
So you want to do a second level of security and protection for your objects and your bucket.

100
00:07:06,310 --> 00:07:10,020
OK so now we use MFH which is multi-factor authentication.

101
00:07:10,020 --> 00:07:15,840
So basically if you have the credentials and permissions to access the bucket if you want to change

102
00:07:15,840 --> 00:07:22,500
Buckett creatures or you want to delete objects or virgins within the bucket then your credentials are

103
00:07:22,500 --> 00:07:30,660
not enough you will be prompted to have an MF a key combination of letters or digits depending on the

104
00:07:30,660 --> 00:07:33,520
device you are using that you have to enter as well.

105
00:07:33,720 --> 00:07:39,150
In addition to your permission so you have two levels of security in order to be able to do that change

106
00:07:39,150 --> 00:07:42,020
the bucket or two an object multi-factor is in the kitchen.

107
00:07:42,030 --> 00:07:44,200
Delete is a versioning capability.

108
00:07:44,200 --> 00:07:45,430
So it's called M.F. delete.

109
00:07:45,480 --> 00:07:49,010
That adds another level of security and keeps your account is compromised.

110
00:07:49,050 --> 00:07:50,290
So it's a multi-part upload.

111
00:07:50,310 --> 00:07:53,760
It's used to upload an object or a object in parts.

112
00:07:53,760 --> 00:07:58,520
So instead of loading the whole object in one operation.

113
00:07:58,680 --> 00:08:05,760
So what you do is if you use multipart upload the file will be divided into pieces and then these will

114
00:08:05,850 --> 00:08:08,870
all be uploaded in parallel.

115
00:08:08,940 --> 00:08:09,960
So what do you gain.

116
00:08:10,020 --> 00:08:17,540
Of course you gain speed and you gain faster upload better use of performance or experience as well.

117
00:08:17,820 --> 00:08:22,090
So parts are uploaded independently and in parallel in any order.

118
00:08:22,110 --> 00:08:27,440
So which object size are recommended for that object sites hundred make or larger.

119
00:08:27,510 --> 00:08:33,000
However you can use for object sizes starting from 5 megabyte to 5 kilobytes remember this is the largest

120
00:08:33,000 --> 00:08:36,070
size you can do in S3.

121
00:08:36,090 --> 00:08:39,940
You must use it for objects larger than 5 gigabytes.

122
00:08:39,960 --> 00:08:42,770
So it is recommended for five hundred gigabytes or more.

123
00:08:42,780 --> 00:08:46,110
It is a must for files five gigabytes or more.

124
00:08:46,140 --> 00:08:47,300
The copy operation.

125
00:08:47,310 --> 00:08:48,090
What does it do.

126
00:08:48,090 --> 00:08:51,780
So you are copying an object in an S3 bucket.

127
00:08:51,780 --> 00:08:57,340
You can copy it to the same budget you can copy to another bucket you can copy it even to another region.

128
00:08:57,360 --> 00:09:04,630
You can create a copy of an object of your object up to five gigabyte in size in a single atomic operation.

129
00:09:04,650 --> 00:09:10,980
Remember when we said the multipart upload is from a hundred megabyte recommended at 5 gigabyte it's

130
00:09:10,980 --> 00:09:11,530
a must.

131
00:09:11,640 --> 00:09:16,980
So up to five gigabyte you can make the copy in one atomic operations and basically are copying the

132
00:09:16,980 --> 00:09:18,450
file as a whole.

133
00:09:18,670 --> 00:09:24,680
But if it is larger than that larger than 5 gigabyte then multipart upload is your only option.

134
00:09:24,720 --> 00:09:26,860
Use the copy operation to do what.

135
00:09:26,940 --> 00:09:32,730
Generate additional copies of the objects renaming objects so you can copy the object to a new name

136
00:09:32,790 --> 00:09:39,510
a new key changing the copy's storage class or encrypted at rest so you can have an object that is not

137
00:09:39,510 --> 00:09:44,300
encrypted and then you can change the encryption status and then you have the choices.

138
00:09:44,510 --> 00:09:48,520
It's as easy as three camis to encrypt it.

139
00:09:48,720 --> 00:09:50,870
Let's discuss storage classes.

140
00:09:50,880 --> 00:09:58,340
The first class which is the default when you try to upload something to an S-3 bucket is the as three

141
00:09:58,350 --> 00:10:04,850
standard storage This one comes with or is designed for ninety nine point nine nine availability per

142
00:10:04,850 --> 00:10:14,060
year what does that mean the chances are that you will not have access to your storage storage or S3

143
00:10:14,060 --> 00:10:17,760
bucket is Point 1 percent per year.

144
00:10:17,790 --> 00:10:24,450
We need to look at something called your ability as well what are the chances that I may lose some of

145
00:10:24,450 --> 00:10:30,750
my data or objects of my data when it is stored on S3 and in that sense.

146
00:10:30,960 --> 00:10:37,220
Has done a very good job and it is a machine mission critical storage they have what they call eleven

147
00:10:37,220 --> 00:10:38,970
nines data durability.

148
00:10:39,000 --> 00:10:41,960
So you need to distinguish between availability and your ability.

149
00:10:42,000 --> 00:10:45,080
So what does the 11:19 rating mean.

150
00:10:45,090 --> 00:10:51,840
So this is the ninety nine ninety nine point nine nine nine nine nine nine nine nine nine percent per

151
00:10:51,840 --> 00:10:52,450
year.

152
00:10:52,530 --> 00:10:57,210
So this is the fact that they will keep your data intact without any data.

153
00:10:57,210 --> 00:11:00,940
So what is my chances to lose something that will be present.

154
00:11:01,080 --> 00:11:06,250
So that the chances that you will lose data in Italy last year.

155
00:11:06,270 --> 00:11:10,400
So as you can see it's a very small probability that you will lose your day.

156
00:11:10,410 --> 00:11:15,690
So the third thing we need to look at is getting encrypted in transit and I trust you as you are uploading

157
00:11:15,690 --> 00:11:17,900
data that is the three endpoint.

158
00:11:17,910 --> 00:11:21,890
What happens then actually to us or SSL is used for that.

159
00:11:21,930 --> 00:11:26,160
It is designed to sustain the concurrent loss of data in facilities.

160
00:11:26,160 --> 00:11:32,410
The second type is called S-3 infrequent access class or S3.

161
00:11:32,730 --> 00:11:36,100
So this is for long lived less frequently access data.

162
00:11:36,120 --> 00:11:43,480
So data that will not be sync as frequent and it is designed like the previous one to to sustain the

163
00:11:43,480 --> 00:11:51,230
concurrent loss of data into facilities and this is suitable for backups and older data so you have

164
00:11:51,230 --> 00:11:58,550
all that data and you want to move it from a story into a story I say because this is cheaper and you

165
00:11:58,550 --> 00:11:59,260
can do that.

166
00:11:59,300 --> 00:12:01,600
It has lower availability.

167
00:12:01,610 --> 00:12:08,150
So it's designed for ninety nine point nine nine the previous one the S3 standard was 9 9 which means

168
00:12:08,150 --> 00:12:13,750
higher availability and it has the same durable if you have the same access speed.

169
00:12:13,790 --> 00:12:19,670
So data is available in real time for you to access quick access and high performance like S3 standard

170
00:12:20,030 --> 00:12:24,040
data is also like a stream encrypted in transit and at rest.

171
00:12:24,050 --> 00:12:32,240
The flipside is if you want to put your data in street I say it has to be at least for 30 days and it

172
00:12:32,240 --> 00:12:36,670
is suitable for objects greater than 128 kilobytes.

173
00:12:36,680 --> 00:12:44,990
The third type is S3 used reduced redundancy storage or S3 r r s This one has less redundancy and it

174
00:12:44,990 --> 00:12:51,650
is designed to sustain the data loss in one facility only the previous two were two facilities not one.

175
00:12:51,650 --> 00:12:58,190
And consequently if you if this is only to sustain that data loss in one facility that means you have

176
00:12:58,190 --> 00:13:05,600
higher probability of losing your data availability it's the same like the S3 standard but the is exactly

177
00:13:05,600 --> 00:13:10,110
much less than the S3 standard and the S3.

178
00:13:10,140 --> 00:13:17,400
So when the ninety nine point nine nine which is four nines the previous ones where 11 times when we

179
00:13:17,410 --> 00:13:20,850
use it use it for non-critical reproducible data.

180
00:13:20,930 --> 00:13:27,800
So if you saved anything in Honoris since it has a higher probability of losing data that means the

181
00:13:27,800 --> 00:13:31,730
data you store here you must be able to reproduce it.

182
00:13:31,730 --> 00:13:34,730
Let's take a break now and come back.

183
00:13:34,730 --> 00:13:39,760
In order to continue on as three features and see what we have to do with nature as well.