1 00:00:00,250 --> 00:00:02,510 Okay, so first to talk about Amazon S3. 2 00:00:02,510 --> 00:00:04,420 We need to talk about buckets. 3 00:00:04,420 --> 00:00:07,840 So S3 is a system, a service that allows us 4 00:00:07,840 --> 00:00:09,260 to store objects. 5 00:00:09,260 --> 00:00:12,430 So files into buckets or directories 6 00:00:12,430 --> 00:00:15,980 and each buckets must have a globally unique name. 7 00:00:15,980 --> 00:00:17,070 As you'll see in the hands-on. 8 00:00:17,070 --> 00:00:19,800 we can't create a bucket that are already being taken 9 00:00:19,800 --> 00:00:21,270 in terms of names. 10 00:00:21,270 --> 00:00:23,830 The buckets are defined at the region level, 11 00:00:23,830 --> 00:00:25,860 so even though S3 is a global service, 12 00:00:25,860 --> 00:00:27,920 buckets are regional resource, 13 00:00:27,920 --> 00:00:29,520 and there is a naming convention 14 00:00:29,520 --> 00:00:30,900 which includes no upper case, 15 00:00:30,900 --> 00:00:34,280 no underscore three to 63 characters long, 16 00:00:34,280 --> 00:00:35,700 it should not be an IP, 17 00:00:35,700 --> 00:00:39,880 and it must start with a lowercase letter or a number. 18 00:00:39,880 --> 00:00:40,770 Okay. 19 00:00:40,770 --> 00:00:45,050 Now in these S3 buckets, we need to create objects. 20 00:00:45,050 --> 00:00:47,770 And objects are files and they must have a key. 21 00:00:47,770 --> 00:00:48,750 And what is a key? 22 00:00:48,750 --> 00:00:51,330 It is the full path to that file. 23 00:00:51,330 --> 00:00:54,230 So if we have a bucket named my buckets 24 00:00:54,230 --> 00:00:58,060 and of object named my_file.txt 25 00:00:58,060 --> 00:01:01,020 then the key is my underscore file.txt, 26 00:01:01,020 --> 00:01:02,500 it's the blue part. 27 00:01:02,500 --> 00:01:05,390 But if we have folder structures within our S3 buckets 28 00:01:05,390 --> 00:01:08,140 so my underscore folder one another folder. 29 00:01:08,140 --> 00:01:11,930 And in my file.txt, the key is the full path. 30 00:01:11,930 --> 00:01:15,860 So that's, again, the entire thing in blue. 31 00:01:15,860 --> 00:01:18,990 And the key can be decomposed in two things. 32 00:01:18,990 --> 00:01:20,650 The key prefix 33 00:01:20,650 --> 00:01:22,870 and the object name. 34 00:01:22,870 --> 00:01:25,520 So if we take the same long example, 35 00:01:25,520 --> 00:01:30,250 the prefix for my_file.txt is my underscore folder one, 36 00:01:30,250 --> 00:01:34,190 slash another folder, slash okay, that is the prefix. 37 00:01:34,190 --> 00:01:38,780 Whereas the object name is my underscore file.txt 38 00:01:38,780 --> 00:01:41,450 So even though there's no concepts of directories 39 00:01:41,450 --> 00:01:44,710 within buckets, just very, very long key names 40 00:01:44,710 --> 00:01:47,900 then the UI will try to trick you into thinking otherwise 41 00:01:47,900 --> 00:01:49,680 because we could create quote unquote 42 00:01:49,680 --> 00:01:51,910 create directories within S3. 43 00:01:51,910 --> 00:01:54,710 So what we really have in S3 is just keys 44 00:01:54,710 --> 00:01:57,180 with very long names that contains slashes. 45 00:01:57,180 --> 00:02:00,120 Okay, so now let's go again for this objects. 46 00:02:00,120 --> 00:02:03,820 So the object values are the content of the body. 47 00:02:03,820 --> 00:02:07,890 So a maximum object size on Amazon S3 is five terabytes 48 00:02:07,890 --> 00:02:10,930 so 5,000 gigabyte, which is a huge object 49 00:02:10,930 --> 00:02:14,890 but you cannot upload more than five gigabytes at a time. 50 00:02:14,890 --> 00:02:17,350 So that means that if you want to upload a big object 51 00:02:17,350 --> 00:02:18,680 of five terabytes 52 00:02:18,680 --> 00:02:21,790 you must divide that object into parts 53 00:02:21,790 --> 00:02:23,380 of less than five gigabytes 54 00:02:23,380 --> 00:02:26,480 and upload these parts independently 55 00:02:26,480 --> 00:02:29,113 into what's called a multi-part upload. 56 00:02:30,010 --> 00:02:33,620 Now each object in Amazon S3, can have metadata. 57 00:02:33,620 --> 00:02:36,270 So it list of key value pairs 58 00:02:36,270 --> 00:02:38,520 that could be system or user metadata. 59 00:02:38,520 --> 00:02:41,400 And this is to add information onto your objects 60 00:02:41,400 --> 00:02:42,830 and also tags. 61 00:02:42,830 --> 00:02:44,600 You can also have key value pair and tags 62 00:02:44,600 --> 00:02:45,540 which is very useful 63 00:02:45,540 --> 00:02:47,540 when you don't you have security on your objects 64 00:02:47,540 --> 00:02:49,340 or lifecycle policies. 65 00:02:49,340 --> 00:02:51,580 Finally, we'll see when we go into versioning 66 00:02:51,580 --> 00:02:55,170 that there is a version ID onto our Amazon S3 objects, 67 00:02:55,170 --> 00:02:57,420 and we'll see what the value of that is 68 00:02:57,420 --> 00:02:59,180 in the versioning lectures. 69 00:02:59,180 --> 00:03:01,060 So without further ado 70 00:03:01,060 --> 00:03:03,220 let's get into the Amazon S3 console 71 00:03:03,220 --> 00:03:04,343 and do a hands-on.