1 00:00:06,676 --> 00:00:10,843 - Now let's talk about Instance Store Volumes in Amazon EC2. 2 00:00:13,117 --> 00:00:16,255 Instance Store Volumes are volumes that 3 00:00:16,255 --> 00:00:19,888 essentially come with the EC2 Instance. 4 00:00:19,888 --> 00:00:23,434 They're what we might consider built in to the EC2 Instance, 5 00:00:23,434 --> 00:00:26,759 at least those instances that actually include them, 6 00:00:26,759 --> 00:00:28,056 not all of them do. 7 00:00:28,056 --> 00:00:31,571 And so the nice thing about Instance Store Volumes are 8 00:00:31,571 --> 00:00:33,658 one, you're not paying anything extra, 9 00:00:33,658 --> 00:00:37,810 they're already included in the cost of the EC2 Instance. 10 00:00:37,810 --> 00:00:41,094 We can get very high IOPs, 11 00:00:41,094 --> 00:00:44,292 upwards of a hundred thousand plus IOPs, 12 00:00:44,292 --> 00:00:46,959 with these particular Instance Stores. 13 00:00:46,959 --> 00:00:48,984 But, what we trade for that, 14 00:00:48,984 --> 00:00:51,529 is the fact that they are ephemeral. 15 00:00:51,529 --> 00:00:54,640 It means that when we stop or terminate that machine, 16 00:00:54,640 --> 00:00:58,057 the data on that drive will be gone. 17 00:00:59,140 --> 00:01:01,444 Amazon does not give us the ability to perform 18 00:01:01,444 --> 00:01:03,975 snapshots on Instance Volumes. 19 00:01:03,975 --> 00:01:07,584 So there are plenty of customers that are using 20 00:01:07,584 --> 00:01:11,613 these Instance Volumes so that we can get that high degree 21 00:01:11,613 --> 00:01:14,507 of IOPs but they are also leveraging 22 00:01:14,507 --> 00:01:16,668 some kind of other software, 23 00:01:16,668 --> 00:01:18,683 perhaps a custom-written application 24 00:01:18,683 --> 00:01:20,346 or a third-party application, 25 00:01:20,346 --> 00:01:24,325 that helps back up that data to either S3 26 00:01:24,325 --> 00:01:26,771 or the Elastic Block storage, 27 00:01:26,771 --> 00:01:28,988 some other storage mechanism 28 00:01:28,988 --> 00:01:31,642 that has a longer life span and more durable. 29 00:01:31,642 --> 00:01:35,197 So, again, it's really important to remember 30 00:01:35,197 --> 00:01:39,070 that while we do get this high degree of IOPs, 31 00:01:39,070 --> 00:01:42,309 the data on this drive is ephemeral and could be gone, 32 00:01:42,309 --> 00:01:44,641 it will be gone, when that machine is 33 00:01:44,641 --> 00:01:46,752 either stopped or terminated. 34 00:01:46,752 --> 00:01:49,905 Just as an example here, this is not a comprehensive list, 35 00:01:49,905 --> 00:01:53,520 but I wanted to give you an example of the types of volumes 36 00:01:53,520 --> 00:01:55,211 that we might expect to see 37 00:01:55,211 --> 00:01:57,237 with different types of machines. 38 00:01:57,237 --> 00:02:00,214 So one example here is the M3 Medium. 39 00:02:00,214 --> 00:02:03,186 The M3 Medium would come with one 40 00:02:03,186 --> 00:02:06,185 4-gig SSD volume. 41 00:02:06,185 --> 00:02:09,135 Whereas the M3 Extra Large 42 00:02:09,135 --> 00:02:12,199 would come with two 40-gig volumes. 43 00:02:12,199 --> 00:02:14,291 And yes you could raid them if you wanted to, 44 00:02:14,291 --> 00:02:17,130 you could put them into a logical volume manager. 45 00:02:17,130 --> 00:02:21,085 Some of the other instances you can see here, 46 00:02:21,085 --> 00:02:24,252 the D2 8 Extra Large comes with about 47 00:02:24,252 --> 00:02:27,335 48 terabytes worth of volumes, 48 00:02:27,335 --> 00:02:31,231 that is 24 2-terabyte devices 49 00:02:31,231 --> 00:02:35,793 that are included with the hourly cost of that machine. 50 00:02:35,793 --> 00:02:38,770 And that is Instance Store Volumes 51 00:02:38,770 --> 00:02:40,270 within Amazon EC2.