1 00:00:00,010 --> 00:00:02,270 ‫Okay, so we are getting to a new section 2 00:00:02,270 --> 00:00:05,270 ‫on Global Infrastructure in AWS. 3 00:00:05,270 --> 00:00:08,000 ‫So why would you make a global application? 4 00:00:08,000 --> 00:00:09,800 ‫Well, a global application is an application 5 00:00:09,800 --> 00:00:12,550 ‫that will be deployed in multiple geographies. 6 00:00:12,550 --> 00:00:15,420 ‫And when you translate this onto AWS, 7 00:00:15,420 --> 00:00:17,670 ‫that could mean that you deploy your application 8 00:00:17,670 --> 00:00:21,430 ‫onto different AWS Regions or Edge Locations. 9 00:00:21,430 --> 00:00:24,610 ‫What this gives you is that for users around the world, 10 00:00:24,610 --> 00:00:26,750 ‫they will have decreased latency. 11 00:00:26,750 --> 00:00:30,120 ‫So latency is the time it takes for a network packet 12 00:00:30,120 --> 00:00:31,800 ‫to reach a server. 13 00:00:31,800 --> 00:00:34,730 ‫And so if you consider that the earth is big, 14 00:00:34,730 --> 00:00:36,650 ‫it will take a lot of time for, 15 00:00:36,650 --> 00:00:38,270 ‫I mean a "lot" 16 00:00:38,270 --> 00:00:40,220 ‫it would take more time for a packet 17 00:00:40,220 --> 00:00:42,270 ‫from Asia to reach the US. 18 00:00:42,270 --> 00:00:44,940 ‫So if you have a user in India, for example, 19 00:00:44,940 --> 00:00:46,380 ‫and your server is in the US, 20 00:00:46,380 --> 00:00:47,570 ‫they will have more lag, 21 00:00:47,570 --> 00:00:49,730 ‫it will be having more latency, 22 00:00:49,730 --> 00:00:52,700 ‫but if you deploy your application closer to users, 23 00:00:52,700 --> 00:00:54,160 ‫they will have a better experience. 24 00:00:54,160 --> 00:00:58,410 ‫So if we deploy our application in the US and in Asia, 25 00:00:58,410 --> 00:01:00,180 ‫then both our users in the US, 26 00:01:00,180 --> 00:01:04,340 ‫and both our users in Asia will have a better latency, 27 00:01:04,340 --> 00:01:07,850 ‫because it will be fast to reach your application servers. 28 00:01:07,850 --> 00:01:09,210 ‫So that will be the first reason. 29 00:01:09,210 --> 00:01:12,310 ‫The second reason would be to have a disaster recovery plan. 30 00:01:12,310 --> 00:01:13,900 ‫So the idea is that you don't wanna rely on 31 00:01:13,900 --> 00:01:16,410 ‫only one data center or one region. 32 00:01:16,410 --> 00:01:18,320 ‫For example, if an entire region goes down, 33 00:01:18,320 --> 00:01:19,160 ‫this has never happened 34 00:01:19,160 --> 00:01:20,930 ‫but it may happen someday, 35 00:01:20,930 --> 00:01:22,820 ‫because of an earthquake or a storm, 36 00:01:22,820 --> 00:01:25,310 ‫a power shutdown, politics, whatever, 37 00:01:25,310 --> 00:01:28,290 ‫then by having a disaster recovery strategy in place, 38 00:01:28,290 --> 00:01:30,320 ‫you can fail-over to another region 39 00:01:30,320 --> 00:01:32,670 ‫and your application will still be working. 40 00:01:32,670 --> 00:01:34,960 ‫So having a DR plan, a disaster recovery plan, 41 00:01:34,960 --> 00:01:36,350 ‫is super important 42 00:01:36,350 --> 00:01:40,360 ‫to increase the availability of your application. 43 00:01:40,360 --> 00:01:42,390 ‫Finally, the last reason why you would have 44 00:01:42,390 --> 00:01:45,940 ‫a global application is in case you are under attack. 45 00:01:45,940 --> 00:01:48,450 ‫So it is coming for hackers online 46 00:01:48,450 --> 00:01:50,180 ‫to attack your application, 47 00:01:50,180 --> 00:01:52,250 ‫to try to take it down for various reasons. 48 00:01:52,250 --> 00:01:55,980 ‫And so if you have your application across multiple regions 49 00:01:55,980 --> 00:01:57,520 ‫and distributed globally, 50 00:01:57,520 --> 00:02:00,200 ‫then it's going to be much harder for an attacker 51 00:02:00,200 --> 00:02:02,070 ‫to attack all of these locations at once. 52 00:02:02,070 --> 00:02:05,660 ‫And so you are more protected against these attacks. 53 00:02:05,660 --> 00:02:07,900 ‫Now AWS, they have this really cool website 54 00:02:07,900 --> 00:02:09,280 ‫that I will show you in a second, 55 00:02:09,280 --> 00:02:10,970 ‫which shows you all the regions, 56 00:02:10,970 --> 00:02:12,770 ‫Availability Zones and so on. 57 00:02:12,770 --> 00:02:14,770 ‫And so this will show you the regions, 58 00:02:14,770 --> 00:02:16,730 ‫this is where we are deploying our applications 59 00:02:16,730 --> 00:02:17,930 ‫and infrastructure. 60 00:02:17,930 --> 00:02:18,980 ‫And the regions, as we know, 61 00:02:18,980 --> 00:02:21,540 ‫they're made of multiple Availability Zones, 62 00:02:21,540 --> 00:02:24,430 ‫they are made themselves of multiple data centers. 63 00:02:24,430 --> 00:02:25,810 ‫And then we have Edge Locations. 64 00:02:25,810 --> 00:02:27,130 ‫We haven't seen them yet, 65 00:02:27,130 --> 00:02:29,250 ‫but they're called also Points of Presence, 66 00:02:29,250 --> 00:02:31,450 ‫and they're used for content delivery 67 00:02:31,450 --> 00:02:33,800 ‫to be as close as possible to users. 68 00:02:33,800 --> 00:02:36,250 ‫And then let's have a look at this website right now 69 00:02:36,250 --> 00:02:38,040 ‫to see how it works. 70 00:02:38,040 --> 00:02:40,060 ‫So this website shows you a map of the world, 71 00:02:40,060 --> 00:02:41,420 ‫and if you click on it, 72 00:02:41,420 --> 00:02:43,430 ‫you're able to look around the globe 73 00:02:43,430 --> 00:02:46,480 ‫and see where AWS has some presence. 74 00:02:46,480 --> 00:02:48,673 ‫So every orange box is going to be a region, 75 00:02:48,673 --> 00:02:51,190 ‫and as you can see you have regions all around the world, 76 00:02:51,190 --> 00:02:52,430 ‫but not everywhere. 77 00:02:52,430 --> 00:02:54,260 ‫And right now, if you click on regions, 78 00:02:54,260 --> 00:02:55,830 ‫you will see where they are 79 00:02:55,830 --> 00:02:58,300 ‫and how they are structured and so on. 80 00:02:58,300 --> 00:02:59,480 ‫And so for example, for Europe, 81 00:02:59,480 --> 00:03:01,000 ‫your region's Spain, London, 82 00:03:01,000 --> 00:03:03,910 ‫Ireland, Paris, Frankfurt, Milan, and Stockholm. 83 00:03:03,910 --> 00:03:06,250 ‫Then it is talking about Availability Zones. 84 00:03:06,250 --> 00:03:07,210 ‫So if we look at, 85 00:03:07,210 --> 00:03:10,200 ‫for example, a region like Northern Virginia, 86 00:03:10,200 --> 00:03:11,740 ‫this is a region right here, 87 00:03:11,740 --> 00:03:13,900 ‫but we have six blue points. 88 00:03:13,900 --> 00:03:17,200 ‫So we have six AZ in the Northern Virginia region. 89 00:03:17,200 --> 00:03:19,720 ‫But if we look for example at Europe 90 00:03:19,720 --> 00:03:21,440 ‫and we look at the Paris region, 91 00:03:21,440 --> 00:03:23,720 ‫we can see we have three blue dots around it, 92 00:03:23,720 --> 00:03:25,570 ‫so there're three Availability Zones. 93 00:03:25,570 --> 00:03:27,470 ‫So these AZ as you can see, 94 00:03:27,470 --> 00:03:30,160 ‫they're distant from one another 95 00:03:30,160 --> 00:03:31,660 ‫because in case something happens, 96 00:03:31,660 --> 00:03:33,150 ‫for example, North of Paris, 97 00:03:33,150 --> 00:03:36,240 ‫then the AZ South of Paris should not be affected, 98 00:03:36,240 --> 00:03:38,510 ‫but still these AZ are linked 99 00:03:38,510 --> 00:03:41,260 ‫by some very, very fast network. 100 00:03:41,260 --> 00:03:42,170 ‫So these are the AZ 101 00:03:42,170 --> 00:03:44,160 ‫and we can see every region has multiple AZ. 102 00:03:44,160 --> 00:03:46,500 ‫And then you have Points of Presence. 103 00:03:46,500 --> 00:03:48,840 ‫So these are the pink dots in this map, 104 00:03:48,840 --> 00:03:50,630 ‫and they are for content delivery networks, 105 00:03:50,630 --> 00:03:52,530 ‫so you cannot deploy an application there, 106 00:03:52,530 --> 00:03:54,470 ‫but something like CloudFront will be using it, 107 00:03:54,470 --> 00:03:57,060 ‫and we'll look at CloudFront in this section. 108 00:03:57,060 --> 00:03:58,760 ‫So as we can see, if we look at California, 109 00:03:58,760 --> 00:04:00,860 ‫we have the pink dots right here, 110 00:04:00,860 --> 00:04:01,730 ‫all around the US, 111 00:04:01,730 --> 00:04:04,880 ‫so that even your users that are close to the Mexico border 112 00:04:04,880 --> 00:04:06,490 ‫or even are in Mexico, 113 00:04:06,490 --> 00:04:09,810 ‫get some fast connection to AWS, okay? 114 00:04:09,810 --> 00:04:12,070 ‫And finally, obviously the network. 115 00:04:12,070 --> 00:04:14,700 ‫So these are the actual links between all the regions 116 00:04:14,700 --> 00:04:17,210 ‫and all the AZs and all the Points of Presence. 117 00:04:17,210 --> 00:04:19,140 ‫And the network is really, really stable. 118 00:04:19,140 --> 00:04:21,410 ‫This is actually a network from AWS. 119 00:04:21,410 --> 00:04:22,300 ‫So all of this is private. 120 00:04:22,300 --> 00:04:24,210 ‫So AWS went above and beyond 121 00:04:24,210 --> 00:04:26,650 ‫and actually installed cables under the water 122 00:04:26,650 --> 00:04:29,130 ‫to link for example, between Europe and the US 123 00:04:29,130 --> 00:04:31,700 ‫or to link between Europe and Africa and so on. 124 00:04:31,700 --> 00:04:33,570 ‫So this is a really cool map, I really like it. 125 00:04:33,570 --> 00:04:36,440 ‫But as you can see, the extent of network is huge, 126 00:04:36,440 --> 00:04:38,400 ‫and this is a private network, 127 00:04:38,400 --> 00:04:41,330 ‫which helps AWS have some fast and reliable connection 128 00:04:41,330 --> 00:04:44,610 ‫between all their different zones and regions. 129 00:04:44,610 --> 00:04:46,370 ‫So that's it, that's what I went through with this website, 130 00:04:46,370 --> 00:04:49,350 ‫have a look, I think it's really cool to get an idea of how 131 00:04:49,350 --> 00:04:52,160 ‫the cloud really can help you have a global presence. 132 00:04:52,160 --> 00:04:54,020 ‫So to summarize on AWS, 133 00:04:54,020 --> 00:04:57,880 ‫for the Global DNS, we're going to learn about Route 53. 134 00:04:57,880 --> 00:04:59,920 ‫It is going to help us route the users 135 00:04:59,920 --> 00:05:02,560 ‫to the closest deployment with the least latency. 136 00:05:02,560 --> 00:05:05,720 ‫And it's going to be great for disaster recovery strategies. 137 00:05:05,720 --> 00:05:07,810 ‫Then for Global Content Delivery Network, 138 00:05:07,810 --> 00:05:09,570 ‫a CDN will be using CloudFront, 139 00:05:09,570 --> 00:05:11,230 ‫and it's going to be able to replicate 140 00:05:11,230 --> 00:05:14,270 ‫parts of our applications into these Edge Locations 141 00:05:14,270 --> 00:05:16,250 ‫to again, decrease the latency for our users 142 00:05:16,250 --> 00:05:18,630 ‫and also cache the common request 143 00:05:18,630 --> 00:05:20,280 ‫to give an improved user experience 144 00:05:20,280 --> 00:05:21,960 ‫and a decreased latency. 145 00:05:21,960 --> 00:05:25,080 ‫Then we'll see about S3 Transfer Acceleration 146 00:05:25,080 --> 00:05:27,220 ‫to accelerate the global uploads and downloads 147 00:05:27,220 --> 00:05:28,690 ‫into Amazon S3. 148 00:05:28,690 --> 00:05:31,550 ‫And finally, the AWS Global Accelerator, 149 00:05:31,550 --> 00:05:32,720 ‫which is going to improve 150 00:05:32,720 --> 00:05:34,970 ‫the global application availability and performance 151 00:05:34,970 --> 00:05:37,030 ‫using the AWS global network. 152 00:05:37,030 --> 00:05:39,160 ‫So we have a busy section, I hope you're excited, 153 00:05:39,160 --> 00:05:41,110 ‫and I will see you in the next lecture.