1 00:00:09,570 --> 00:00:13,750 Welcome back to Backspace Academy. In this lecture we'll have a look at the 2 00:00:13,750 --> 00:00:19,570 different options that are available for running databases on AWS. We will then have 3 00:00:19,570 --> 00:00:24,250 a look at a database example and finally we'll finish up with a hands-on lab 4 00:00:24,250 --> 00:00:29,980 where we'll be creating a database server on AWS and then remotely 5 00:00:29,980 --> 00:00:38,739 connecting in to that database. The relational database service or RDS for 6 00:00:38,739 --> 00:00:43,600 short is a fully managed database service that makes it easy to launch 7 00:00:43,600 --> 00:00:50,530 database servers in the AWS cloud and scale them when required. The RDS service 8 00:00:50,530 --> 00:00:55,329 can launch servers for mySQL including variations of the mySQL 9 00:00:55,329 --> 00:01:00,879 database engine with MariaDB and Amazon's own enterprise version of mySQL 10 00:01:00,879 --> 00:01:07,540 Amazon Aurora. Standard Postgre SQL is also available and also available 11 00:01:07,540 --> 00:01:15,310 as Amazon's Enterprise Aurora Postgre SQL. Microsoft SQL server and Oracle 12 00:01:15,310 --> 00:01:24,430 are also available. Amazon DynamoDB is AWS's NoSQL database as a 13 00:01:24,430 --> 00:01:30,850 service. It's a serverless service like Amazon S3 and as such you don't need to 14 00:01:30,850 --> 00:01:34,180 worry about the underlying infrastructure behind it. 15 00:01:34,180 --> 00:01:40,210 AWS takes care of everything for you and it provides high speed extremely low 16 00:01:40,210 --> 00:01:48,550 latency performance. Amazon Redshift is a fast fully managed petabyte scale data 17 00:01:48,550 --> 00:01:53,980 warehouse that is based upon the postgre SQL database engine. If you're 18 00:01:53,980 --> 00:02:01,240 looking for a big data storage solution Redshift is perfect for this. Amazon 19 00:02:01,240 --> 00:02:07,930 ElastiCache is an in-memory data store or cache in the cloud. It allows you to 20 00:02:07,930 --> 00:02:14,230 retrieve information from fast fully managed in-memory caches instead of 21 00:02:14,230 --> 00:02:22,270 relying on slower disk based databases. The AWS database migration service or DMS 22 00:02:22,270 --> 00:02:28,210 orchestrates a migration of databases over to AWS easily and securely. 23 00:02:28,210 --> 00:02:34,630 It can also migrate data from one database engine type to another totally 24 00:02:34,630 --> 00:02:39,340 different database engine type, for example you can use it to migrate from 25 00:02:39,340 --> 00:02:48,490 Oracle over to Amazon Aurora. Amazon Neptune is a fast reliable fully managed 26 00:02:48,490 --> 00:02:52,480 graph database service it has a purpose-built 27 00:02:52,480 --> 00:02:57,970 high performance graph database engine optimized for storing billions of 28 00:02:57,970 --> 00:03:05,350 relationships and clearing the graph with millisecond latency. 29 00:03:06,560 --> 00:03:10,000 Now let's have a look at how you might 30 00:03:10,000 --> 00:03:14,800 use some of these database services in a real-life example. 31 00:03:14,800 --> 00:03:18,000 On the right there, we've got our corporate data center and 32 00:03:18,000 --> 00:03:21,680 inside of our corporate data center we've got an on-site 33 00:03:21,680 --> 00:03:26,239 Oracle database. Now let's just say that Oracle database, 34 00:03:26,239 --> 00:03:30,000 it's old, it's worn out, it's outgrown its capacity 35 00:03:30,000 --> 00:03:33,840 and it needs to be replaced. Now you've done 36 00:03:33,840 --> 00:03:38,480 a total cost of ownership analysis on the situation 37 00:03:38,480 --> 00:03:42,959 and you've identified that it is far more cost effective 38 00:03:42,959 --> 00:03:49,040 to host that database on the aws cloud. So the first thing that you are 39 00:03:49,040 --> 00:03:53,760 going to want to do is to launch an RDS database 40 00:03:53,760 --> 00:03:58,480 instance. Now let's say you want to further reduce your cost 41 00:03:58,480 --> 00:04:02,959 by not having to pay for the Oracle licensing fee 42 00:04:02,959 --> 00:04:06,080 and what you can do is that you can launch an Amazon 43 00:04:06,080 --> 00:04:09,760 Aurora database instance and that will be running 44 00:04:09,760 --> 00:04:17,359 either the Mysql or the Postgresql open source database engines and by doing 45 00:04:17,359 --> 00:04:23,120 that you're not going to be paying for a licensing fee. The disadvantage of 46 00:04:23,120 --> 00:04:26,320 that is that some of the fields of data that are 47 00:04:26,320 --> 00:04:31,759 located in that Oracle database may not be compatible with the Amazon 48 00:04:31,759 --> 00:04:37,440 Aurora Mysql or Postgresql fields and what you're going to need to 49 00:04:37,440 --> 00:04:40,320 do is that when you take that data out of your 50 00:04:40,320 --> 00:04:43,520 Oracle database, you're going to have to change it and 51 00:04:43,520 --> 00:04:49,040 manipulate it to suit the amazon aurora database, 52 00:04:49,040 --> 00:04:56,320 and that is where the aws database migration service comes in. 53 00:04:56,320 --> 00:05:02,800 You can define a database migration workflow by specifying 54 00:05:02,800 --> 00:05:09,360 the source database, the target database and any operations on that data that 55 00:05:09,360 --> 00:05:14,160 need to occur during that migration of that data. 56 00:05:14,160 --> 00:05:18,000 Once you've done that you can then run the database migration 57 00:05:18,000 --> 00:05:21,680 job and that will look after everything for you. 58 00:05:21,680 --> 00:05:26,000 It will migrate that data from that on-site oracle database 59 00:05:26,000 --> 00:05:30,560 to your amazon aurora database and at the same time it will be giving you 60 00:05:30,560 --> 00:05:34,240 feedback through the aws management console, 61 00:05:34,240 --> 00:05:38,000 as a dashboard, on the performance of how that job is 62 00:05:38,000 --> 00:05:41,759 actually going, because that job could take hours, it could take 63 00:05:41,759 --> 00:05:46,000 days, it could take weeks, depending on how big your oracle database 64 00:05:46,000 --> 00:05:49,680 is and how fast your connection to the aws 65 00:05:49,680 --> 00:05:54,880 cloud is, and it will also give you feedback of any errors and alert you to 66 00:05:54,880 --> 00:06:00,319 any problems that may occur. Once our RDS instance is up and running 67 00:06:00,319 --> 00:06:05,199 and the data has been migrated over, then we can look at launching a web 68 00:06:05,199 --> 00:06:09,199 server that can receive traffic and requests from the outside 69 00:06:09,199 --> 00:06:13,440 world over the internet and then get that data that is required 70 00:06:13,440 --> 00:06:17,199 from the RDS database and then return that back to the 71 00:06:17,199 --> 00:06:20,880 requester. Now let's just say we're getting a lot 72 00:06:20,880 --> 00:06:24,160 of requests from the outside world and a lot of that 73 00:06:24,160 --> 00:06:29,360 is for the same data. What we can look at doing is getting all 74 00:06:29,360 --> 00:06:35,120 of our regularly accessed content and putting it into an Elasticache 75 00:06:35,120 --> 00:06:42,479 node and, because the Elasticache node is serving those requests from its 76 00:06:42,479 --> 00:06:47,919 memory, not from a solid-state drive, as is the case of the rds service, it 77 00:06:47,919 --> 00:06:51,599 will be returning that very quickly and it will be at a lower 78 00:06:51,599 --> 00:06:54,960 cost. Now we need to take into consideration 79 00:06:54,960 --> 00:07:00,720 that the costs of storing data in memory is more expensive 80 00:07:00,720 --> 00:07:05,520 than storing that data on a solid state drive and so we need to 81 00:07:05,520 --> 00:07:10,400 make sure that Elasticache node only contains 82 00:07:10,400 --> 00:07:16,080 regularly accessed data. So the way that we would do that is that requests would 83 00:07:16,080 --> 00:07:19,440 come in from the outside world to the web server, 84 00:07:19,440 --> 00:07:22,960 the web server could then check to see whether that data 85 00:07:22,960 --> 00:07:28,319 is in the Elasticache node. If it is or if it is in the Elasticache node it 86 00:07:28,319 --> 00:07:32,080 will simply grab that data and then forward it back to that 87 00:07:32,080 --> 00:07:36,560 requester. Let's just say a request comes in and 88 00:07:36,560 --> 00:07:41,199 that data is not in the Elasticache node. So then the web server will go to 89 00:07:41,199 --> 00:07:47,039 the RDS database instance, it will get that data if it's there and 90 00:07:47,039 --> 00:07:52,800 after it has got that data, it will then write that data into the Elasticache 91 00:07:52,800 --> 00:08:00,000 node, and at the same time it will define a time to live or a ttl 92 00:08:00,000 --> 00:08:06,080 for that specific data, and once that ttl has expired, 93 00:08:06,080 --> 00:08:11,840 if there are no further requests for that data within that ttl, 94 00:08:11,840 --> 00:08:15,599 then that data will be removed automatically by the Elasticache 95 00:08:15,599 --> 00:08:21,919 service from the Elasticache node, and by doing that, all of that data 96 00:08:21,919 --> 00:08:25,759 that's in the Elasticache node will be 97 00:08:25,759 --> 00:08:31,440 regularly accessed data that has been accessed within that time to live period. 98 00:08:31,440 --> 00:08:35,440 Now let's just say a request comes into that web server 99 00:08:35,440 --> 00:08:41,839 for either writing to or deleting from that RDS database. So the way that would 100 00:08:41,839 --> 00:08:44,640 work is that the request would come into the web server 101 00:08:44,640 --> 00:08:48,560 the web server would then either delete or write to 102 00:08:48,560 --> 00:08:52,880 the RDS database. If it is deleting from the database 103 00:08:52,880 --> 00:08:57,200 then it would also delete from the Elasticache node as well. 104 00:08:57,200 --> 00:09:00,399 If it's writing to the database then it would also 105 00:09:00,399 --> 00:09:06,720 write to the Elasticache node and again it would define a time to live period, 106 00:09:06,720 --> 00:09:11,360 so that if that data is not requested within that time to live period then it 107 00:09:11,360 --> 00:09:16,320 will automatically be removed from the Elasticache node 108 00:09:16,320 --> 00:09:22,640 by the Elasticache service. Okay let's have a go at doing this 109 00:09:22,640 --> 00:09:26,320 ourselves. In this lab we're going to be launching 110 00:09:26,320 --> 00:09:30,320 an RDS database instance that will be using the 111 00:09:30,320 --> 00:09:35,440 Mysql database engine that will be covered under the AWS free 112 00:09:35,440 --> 00:09:38,959 tier so this lab is not going to cost us anything. 113 00:09:38,959 --> 00:09:42,959 Now because we're launching that within our VPC which is our 114 00:09:42,959 --> 00:09:50,000 own private space within the aws network, no access will be allowed 115 00:09:50,000 --> 00:09:54,320 to that RDS instance unless we allow that to happen. 116 00:09:54,320 --> 00:10:01,040 So that rds instance will have a default security group associated to it 117 00:10:01,040 --> 00:10:06,079 and that security group is a firewall to the outside world 118 00:10:06,079 --> 00:10:10,000 and it will have rules that will prevent access 119 00:10:10,000 --> 00:10:15,839 to that database instance. So to allow access to that RDS database 120 00:10:15,839 --> 00:10:19,600 instance, we are going to need to create a new 121 00:10:19,600 --> 00:10:23,519 security group and within that security group we are 122 00:10:23,519 --> 00:10:28,000 going to define a rule that will allow access 123 00:10:28,000 --> 00:10:32,000 from our remote computer. Then when we are launching 124 00:10:32,000 --> 00:10:37,519 our RDS instance we simply define and associate that security group 125 00:10:37,519 --> 00:10:40,880 with that instance and that database will be launched 126 00:10:40,880 --> 00:10:44,160 with that security group associated to it. 127 00:10:44,160 --> 00:10:50,880 Once we've done that we can then install the Mysql workbench software on our 128 00:10:50,880 --> 00:10:55,200 remote computer and then provided we've got the username 129 00:10:55,200 --> 00:11:00,880 and password that we created for that database, we will be able to connect into 130 00:11:00,880 --> 00:11:05,680 that database instance and manipulate that database. 131 00:11:05,680 --> 00:11:09,920 Now before we start the lab you need to make sure that you 132 00:11:09,920 --> 00:11:15,680 open up these introduction to AWS lab notes and follow along with me. 133 00:11:15,680 --> 00:11:19,440 Very important that you follow the lab notes not the video when you're doing it 134 00:11:19,440 --> 00:11:22,160 yourself. So certainly watch the video now but 135 00:11:22,160 --> 00:11:26,000 when you go and do it yourself, make sure that you follow the lab notes. 136 00:11:26,000 --> 00:11:30,240 The reason being is that the AWS management console, it continuously 137 00:11:30,240 --> 00:11:33,839 changes. I can't remember a week gone by where they haven't 138 00:11:33,839 --> 00:11:39,200 fiddled with this in some shape or form. So if you've got the lab notes you can 139 00:11:39,200 --> 00:11:43,279 follow those and they will be updated whenever I'm aware of any changes to the 140 00:11:43,279 --> 00:11:48,000 management console. With this lab you may run into trouble 141 00:11:48,000 --> 00:11:51,200 when you're trying to connect into your RDS database. 142 00:11:51,200 --> 00:11:55,760 What I've got there is in this creating a SQL database with RDS, that chapter 143 00:11:55,760 --> 00:11:59,279 that we're going to be doing for this lab, there is 144 00:11:59,279 --> 00:12:03,519 a troubleshooting connection issues section. If you click on that 145 00:12:03,519 --> 00:12:08,639 it will go through all of the different scenarios that you may encounter 146 00:12:08,639 --> 00:12:11,680 when you can't connect to this database instance. 147 00:12:11,680 --> 00:12:15,600 So it could be there we see wrong user name password. We could put 148 00:12:15,600 --> 00:12:19,200 the wrong endpoint in there, a whole heap of different things. It's normally 149 00:12:19,200 --> 00:12:22,320 something very simple such as you haven't clicked on 150 00:12:22,320 --> 00:12:26,079 public when you've created the database or, it could be 151 00:12:26,079 --> 00:12:29,519 something a bit more fatal, such as you're trying to connect 152 00:12:29,519 --> 00:12:35,200 in from your work environment and the port 3306 is being blocked by 153 00:12:35,200 --> 00:12:39,040 by your work environment. If you run into those sorts of issues you're just going 154 00:12:39,040 --> 00:12:43,760 to have to run the lab from at home and use your home internet 155 00:12:43,760 --> 00:12:48,160 connection instead. So that will basically detail all of 156 00:12:48,160 --> 00:12:52,880 those issues and how you need to solve those. 157 00:12:52,880 --> 00:12:57,360 Now before we get started with launching our database 158 00:12:57,360 --> 00:13:02,079 instance, we need to make sure that we create this security group that is going 159 00:13:02,079 --> 00:13:06,320 to be or is going to allow inbound access 160 00:13:06,320 --> 00:13:09,360 from the outside world. So we'll just create that. 161 00:13:09,360 --> 00:13:18,000 So we'll go to services and i've just listed this by a to z. We'll go to vpc 162 00:13:19,600 --> 00:13:24,480 we'll scroll down to security and security groups. So click on security 163 00:13:24,480 --> 00:13:29,760 groups and we're going to create security group. 164 00:13:29,760 --> 00:13:34,639 We'll give this security group a name and i've just copied from the lab notes 165 00:13:34,639 --> 00:13:38,959 here and we'll give it a description. 166 00:13:39,839 --> 00:13:43,839 Okay what we need to do now is that we need to add an 167 00:13:43,839 --> 00:13:47,600 inbound rule that is going to allow that access. So we'll add 168 00:13:47,600 --> 00:13:55,279 rule and the type of rule is going to be mysql/aurora 169 00:13:55,360 --> 00:13:59,360 and the source is going to be from anywhere. 170 00:13:59,360 --> 00:14:03,360 So although anyone can access our database, to get anything out of that 171 00:14:03,360 --> 00:14:07,760 database they're going to need to have a username and password. 172 00:14:07,760 --> 00:14:11,839 So we'll just scroll down. We don't need to have an outbound rule 173 00:14:11,839 --> 00:14:17,360 and we'll create that security group. So there our security group has been 174 00:14:17,360 --> 00:14:22,720 created. So when we launch our rds database we can associate this 175 00:14:22,720 --> 00:14:27,199 security group to that database and then that database 176 00:14:27,199 --> 00:14:30,639 will accept inbound traffic from the wider 177 00:14:30,639 --> 00:14:34,560 internet. So we'll go to services now and we'll 178 00:14:34,560 --> 00:14:45,839 now go to the RDS. 179 00:14:48,880 --> 00:14:54,800 Okay so we'll scroll down to databases and then we're going to create a 180 00:14:54,800 --> 00:14:59,839 database. So click on create database. 181 00:15:00,320 --> 00:15:04,160 We're going to do a standard create and we're going to use 182 00:15:04,160 --> 00:15:10,000 mysql and we'll scroll down here and we're going to use the free tier 183 00:15:10,000 --> 00:15:16,240 because it's free why not. Now we need to give our db instance an 184 00:15:16,240 --> 00:15:19,040 identifier. 185 00:15:19,120 --> 00:15:23,920 So just give it a name there for your database or for your database instance. 186 00:15:23,920 --> 00:15:27,839 Now we need to define a username and password. So the username, I'm just going 187 00:15:27,839 --> 00:15:40,000 to use is, going to leave that as admin and put in a password there. 188 00:15:40,000 --> 00:15:44,079 We'll scroll down here and we're just going to leave that as a t2 micro that's 189 00:15:44,079 --> 00:15:48,160 a small instance that we're going to get on the free tier. 190 00:15:48,160 --> 00:15:51,759 I'm not going to have any auto scaling for the storage because we're not going 191 00:15:51,759 --> 00:15:54,000 to be putting anything in this database. We don't 192 00:15:54,000 --> 00:15:57,199 have to worry about that, we're not going to be 193 00:15:57,199 --> 00:16:00,720 launching this into multiple availability zones so that is all grayed 194 00:16:00,720 --> 00:16:04,000 out that is fine. We're going to launch it into our 195 00:16:04,000 --> 00:16:07,839 default vpc. Now we need to click on additional 196 00:16:07,839 --> 00:16:11,600 connectivity configuration. 197 00:16:11,839 --> 00:16:15,759 No we need this to be publicly accessible. We're going to access this 198 00:16:15,759 --> 00:16:23,120 from outside of our virtual private cloud. So click on yes there. 199 00:16:23,120 --> 00:16:28,560 Now we need to select our security group that is going to allow for that outside 200 00:16:28,560 --> 00:16:33,279 access to our vpc. So we'll select that there 201 00:16:33,279 --> 00:16:40,079 and it was called backspace and there it is backspace rds intro lab. 202 00:16:40,079 --> 00:16:43,279 So we'll just click on that to select it and we can see there it's put it down 203 00:16:43,279 --> 00:16:46,000 there. I'll just click outside of this. So there 204 00:16:46,000 --> 00:16:49,759 we've added that, we've associated that backspace rds 205 00:16:49,759 --> 00:16:55,120 intro lab security group to this instance. 206 00:16:55,120 --> 00:16:59,360 We're going to leave it with password authentication so someone who needs to 207 00:16:59,360 --> 00:17:03,600 log into this database will need to have a username and password 208 00:17:03,600 --> 00:17:08,959 that we have defined up here. Which we have defined here is admin and 209 00:17:08,959 --> 00:17:11,919 then our password. 210 00:17:14,160 --> 00:17:17,439 We'll just click on additional configuration. 211 00:17:17,439 --> 00:17:21,360 So we're going to give an initial database name and so when 212 00:17:21,360 --> 00:17:25,039 this database instance or server or whatever has been 213 00:17:25,039 --> 00:17:30,240 launched, that can create a database for us and then we can 214 00:17:30,240 --> 00:17:33,120 automatically can straight away start playing around with that database. So i'm 215 00:17:33,120 --> 00:17:35,840 just going to give it a name there we have test 216 00:17:35,840 --> 00:17:40,559 that will be fine. We don't need to have any backups of this data that's fine. 217 00:17:40,559 --> 00:17:45,120 I'll leave that it's just a lab nothing special. Scroll down a little bit 218 00:17:45,120 --> 00:17:48,320 further. Okay the estimated monthly cost it's 219 00:17:48,320 --> 00:17:51,840 going to be covered under the free tier we don't have to worry about any costs 220 00:17:51,840 --> 00:17:56,160 there and we'll click on create database. 221 00:17:58,000 --> 00:18:02,720 So there it has started to create this database and the status is creating so 222 00:18:02,720 --> 00:18:06,559 after about five, ten minutes or so 223 00:18:06,559 --> 00:18:10,720 this will change to being available. 224 00:18:10,720 --> 00:18:16,880 So we'll just let that chug away. Okay so after a few minutes our status has 225 00:18:16,880 --> 00:18:20,240 changed to available. So what we'll do now is 226 00:18:20,240 --> 00:18:24,240 we'll click on this database 227 00:18:25,039 --> 00:18:28,640 and then we can see some information about it. So we can see that we've got 228 00:18:28,640 --> 00:18:34,720 our vpc security group, our backspace rds intro lab security group has been 229 00:18:34,720 --> 00:18:39,520 associated with it, it has a or it is publicly 230 00:18:39,520 --> 00:18:44,480 accessible and so that means that it's going to have a public ip address 231 00:18:44,480 --> 00:18:47,600 and so we're going to be able to access that and it's going to have this end 232 00:18:47,600 --> 00:18:50,480 point here for us. 233 00:18:51,200 --> 00:18:57,600 Now if we have this endpoint we can now connect into our database 234 00:18:57,600 --> 00:19:03,679 using the mysql workbench. Now the link to download that is in the 235 00:19:03,679 --> 00:19:08,080 lab notes so make sure that you download that and install the MySQL 236 00:19:08,080 --> 00:19:12,480 workbench it runs on on linux, it runs on windows, runs on mac, 237 00:19:12,480 --> 00:19:15,679 it's pretty good and quite well supported. 238 00:19:15,679 --> 00:19:24,400 So i'm just going to drag it into here and i'll just get rid of that connection. 239 00:19:24,400 --> 00:19:27,760 okay so your MySQL workbench should look something like this. 240 00:19:27,760 --> 00:19:30,960 We want to add a connection. So we just click on this plus next to 241 00:19:30,960 --> 00:19:36,960 MySQL connection. Now the connection name, i'm just going to call it test 242 00:19:36,960 --> 00:19:41,440 that can be anything you want. Now this host name is going to be 243 00:19:41,440 --> 00:19:46,000 our endpoint, so we copy our endpoint here 244 00:19:46,480 --> 00:19:49,760 and we'll paste that in here. 245 00:19:50,240 --> 00:19:54,240 There's our port 3306. 246 00:19:54,559 --> 00:19:59,600 Now our username is going to be that username and password that we defined. 247 00:19:59,600 --> 00:20:04,840 So we actually did not use root we used admin 248 00:20:04,840 --> 00:20:08,320 and that should be fine that's all we need. 249 00:20:08,320 --> 00:20:11,600 What we can do now is we can test this connection. So down the bottom here a 250 00:20:11,600 --> 00:20:15,919 test connection button we'll click on that. 251 00:20:18,480 --> 00:20:22,559 Okay so it's started the connection process so it's gone to that 252 00:20:22,559 --> 00:20:25,600 host name that endpoint and that's worked and now it's asking for the 253 00:20:25,600 --> 00:20:30,320 password. So that is the password that we defined 254 00:20:30,320 --> 00:20:35,120 when we created that that instance. We'll click on ok 255 00:20:35,120 --> 00:20:39,919 and if all goes well we should have a success screen. There we go successfully 256 00:20:39,919 --> 00:20:44,400 made the MySQL connection. The host was that 257 00:20:44,400 --> 00:20:48,559 that end point, the port was 3306, our user was 258 00:20:48,559 --> 00:20:52,159 admin. Now if you find that this doesn't work for you 259 00:20:52,159 --> 00:20:55,919 remember there is always the troubleshooting connection 260 00:20:55,919 --> 00:20:59,679 issues section in the lab notes. Make sure you follow those if you run into 261 00:20:59,679 --> 00:21:04,240 problems here. So just click on ok that 262 00:21:04,320 --> 00:21:08,799 and okay. So that has set up that connection so whenever we go into 263 00:21:08,799 --> 00:21:11,360 the MySQL workbench that connection will be there 264 00:21:11,360 --> 00:21:16,320 and all we need to do is double click on it and it will open up the SQL editor 265 00:21:16,320 --> 00:21:18,720 for us. 266 00:21:19,280 --> 00:21:24,240 That will take quite a bit of time, you'll have to connect in. 267 00:21:28,000 --> 00:21:32,080 Okay there we go so we have successfully connected into 268 00:21:32,080 --> 00:21:36,799 our database using that that username and password and we can see here we've 269 00:21:36,799 --> 00:21:40,400 got our test database that has been automatically 270 00:21:40,400 --> 00:21:44,799 created for us by the RDS service and we can click on that and we can see that 271 00:21:44,799 --> 00:21:46,960 we've got no tables or anything in there yet 272 00:21:46,960 --> 00:21:50,559 but we could add those if we wanted to. So that's 273 00:21:50,559 --> 00:21:54,000 pretty well all we need to know about about this 274 00:21:54,000 --> 00:21:59,200 lab we just created a database instance. We've connected into that successfully 275 00:21:59,200 --> 00:22:02,080 and that's pretty good. When we get further into the course 276 00:22:02,080 --> 00:22:05,520 we'll learn a lot more about this sort of stuff and how we can 277 00:22:05,520 --> 00:22:09,200 do a lot more and how we can launch other instances such as Oracle 278 00:22:09,200 --> 00:22:13,280 and microsoft sql server and all that sort of thing 279 00:22:13,280 --> 00:22:17,840 but for now that is all we do for this lab. What we'll do now is it will clean 280 00:22:17,840 --> 00:22:20,559 it all up. I'll just close that out there now 281 00:22:20,559 --> 00:22:28,400 and we'll go to actions and we'll delete. We don't need to create a final snapshot 282 00:22:28,400 --> 00:22:31,039 we just click on acknowledge that once we delete it 283 00:22:31,039 --> 00:22:35,440 everything is gone and we just talked a lot we just type 284 00:22:35,440 --> 00:22:41,840 delete me in here. 285 00:22:43,440 --> 00:22:46,559 Okay so that will be deleting that so you can see up here a note saying 286 00:22:46,559 --> 00:22:49,200 deleting db instance. Now the next thing that we 287 00:22:49,200 --> 00:22:53,840 could do is we could clean up that that security group so we go to services 288 00:22:53,840 --> 00:22:56,799 and then vpc 289 00:22:58,799 --> 00:23:04,559 and if we go to security groups now we can find this so we'll just i just 290 00:23:04,559 --> 00:23:09,200 sort this by security group name. So there we have that security group. Now 291 00:23:09,200 --> 00:23:12,799 if we go to delete that now. If we click on delete security group, it 292 00:23:12,799 --> 00:23:15,600 won't let us do it. So i'll just click on it now 293 00:23:15,600 --> 00:23:19,039 and it won't let us do it because that that RDS 294 00:23:19,039 --> 00:23:23,200 instance hasn't finished being terminated. So you need to wait until 295 00:23:23,200 --> 00:23:26,000 that has terminated. You can come back here and 296 00:23:26,000 --> 00:23:30,720 then you can delete that security group. If you forget about it, it's not a major 297 00:23:30,720 --> 00:23:34,799 deal because you don't get charged for security groups, but 298 00:23:34,799 --> 00:23:38,159 your rds instance you need to make sure you terminate that otherwise yes you 299 00:23:38,159 --> 00:23:41,440 will get billed for that. Although it is under the free tier, if 300 00:23:41,440 --> 00:23:44,720 you go to launch another one and you've got two of them running then you're 301 00:23:44,720 --> 00:23:48,960 going to get billed for one of those. So just cancel that out. So that brings 302 00:23:48,960 --> 00:23:53,120 us to the end of the lab. I hope you enjoyed it. Make sure that you 303 00:23:53,120 --> 00:23:57,120 download the lab notes and do all that yourself and I look 304 00:23:57,120 --> 00:24:00,960 forward to seeing you in the next one.