WEBVTT 1 00:00.000 --> 00:10.000 So next up here, let's go ahead and deploy an EC2 VM into our VDC. 2 00:10.000 --> 00:13.650 Now, again, the main purpose of this, we're just going to do a simple Linux 3 00:13.650 --> 00:16.000 server, put it on our subnet, 4 00:16.000 --> 00:21.040 and this is just to give us something to try to test connectivity with once we 5 00:21.040 --> 00:24.000 get Cloud on-ramp built up and functional. 6 00:24.000 --> 00:30.000 So let's go ahead and just deploy a real simple Linux VM into our VPC. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:30.000 --> 00:35.400 So here we're going to start off on the EC2 dashboard, and once again, we can 8 00:35.400 --> 00:38.000 see that we have a launch instance button right here. 9 00:38.000 --> 00:40.000 So we'll go ahead and click on that. 10 00:40.000 --> 00:43.000 We'll start off by giving our instance a name. 11 00:43.000 --> 00:48.000 We'll simply call it AWS-WS1 for Workstation 1. 12 00:48.000 --> 00:53.570 For the image, we'll just leave the default here. Again, we just need something 13 00:53.570 --> 00:54.000 that's pingable. 14 00:54.000 --> 00:57.940 If you would rather choose some other operating system or use something 15 00:57.940 --> 01:01.000 different here, you're more than welcome to. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:57.940 --> 01:01.000 different here, you're more than welcome to. 16 01:01.000 --> 01:04.000 I'm just going to stick with the Amazon Linux. 17 01:04.000 --> 01:06.000 We'll scroll down here a bit. 18 01:06.000 --> 01:11.240 Again, based on the fact that all we want to do is have something we can ping, 19 01:11.240 --> 01:16.000 having an instance type of T2 micro is perfectly fine. 20 01:16.000 --> 01:20.000 I will go ahead and configure this key pair. 21 01:20.000 --> 01:26.000 I already have a key created in AWS that I use for logging into AWS devices. 22 01:26.000 --> 01:32.000 This is just in case we want to SSH into this server once it's up and running. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:26.000 --> 01:32.000 This is just in case we want to SSH into this server once it's up and running. 23 01:32.000 --> 01:36.840 The big thing we want to make sure we do here is under network settings, we 24 01:36.840 --> 01:38.000 want to hit edit. 25 01:38.000 --> 01:41.000 Now a couple of things here under edit that we want to verify. 26 01:41.000 --> 01:45.000 First, we want to make sure that we are in the correct VPC. 27 01:45.000 --> 01:49.000 Of course, we only have one, so that's going to be the one selected by default. 28 01:49.000 --> 01:51.000 Same thing with the subnet. 29 01:51.000 --> 01:54.690 We want to make sure we're in the correct subnet, but of course, given that we 30 01:54.690 --> 01:59.010 only have the one subnet we created, this is going to be correctly selected by 31 01:59.010 --> 02:00.000 default as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 02:00.000 --> 02:04.040 If you add more than one, of course, you would have to choose the appropriate 33 02:04.040 --> 02:05.000 choices here. 34 02:05.000 --> 02:07.000 Next is the security group. 35 02:07.000 --> 02:10.430 We're going to let this go ahead and create a security group since we don't 36 02:10.430 --> 02:13.000 have any existing security groups at the moment. 37 02:13.000 --> 02:15.000 And if you want, you can give it a name. 38 02:15.000 --> 02:18.000 It defaults to just launch lizard one. 39 02:18.000 --> 02:20.000 I'm just going to rename it. 40 02:20.000 --> 02:22.000 We're not going to make it anything super fancy. 41 02:22.000 --> 02:25.000 I'll just make it like SG dash one for security group one. 42 02:25.000 --> 02:28.000 If you want, you can put a description on it. 43 02:28.000 --> 02:33.200 We could maybe call this something like host security group, something along WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:28.000 --> 02:33.200 We could maybe call this something like host security group, something along 44 02:33.200 --> 02:34.000 those lines. 45 02:34.000 --> 02:39.000 The main thing we want to do here, though, is we continue scrolling down. 46 02:39.000 --> 02:44.370 And we see that there's going to be a default inbound security group rule for 47 02:44.370 --> 02:46.000 SSH from anywhere. 48 02:46.000 --> 02:51.780 And that's fine because we may want to SSH into this server, but we also want 49 02:51.780 --> 02:53.000 to be able to ping it. 50 02:53.000 --> 02:58.000 So what we want to do is come down here to add a security group rule. 51 02:58.000 --> 03:06.000 For this rule, we'll simply set this to all ICMP for IPV four. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 02:58.000 --> 03:06.000 For this rule, we'll simply set this to all ICMP for IPV four. 52 03:06.000 --> 03:11.000 And for the source type, we'll set this to anywhere. 53 03:11.000 --> 03:15.700 So this way, we'll actually be able to ping our server once we get cloud on 54 03:15.700 --> 03:17.000 ramp deployed. 55 03:17.000 --> 03:21.000 We can scroll down, make sure the rest of these settings look appropriate. 56 03:21.000 --> 03:22.000 Again, things like storage. 57 03:22.000 --> 03:25.000 We're not going to be too concerned with right now. 58 03:25.000 --> 03:30.000 Again, we just need a pingable server of some sort. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:30.000 --> 03:32.000 This is just for testing. 60 03:32.000 --> 03:35.000 So everything here looks fine. Let's go ahead and hit launch instance. 61 03:35.000 --> 03:37.000 Notice here we get a failure. 62 03:37.000 --> 03:42.540 Apparently, it doesn't like my incredibly simple name of SG dash one for the 63 03:42.540 --> 03:44.000 security group. 64 03:44.000 --> 03:48.000 It says the group names may not be in the format of SG dash. 65 03:48.000 --> 03:51.000 I guess that just makes too much sense. 66 03:51.000 --> 03:54.000 So let's go ahead and edit the instance config. 67 03:54.000 --> 03:57.000 We'll scroll down to our security group name. 68 03:57.000 --> 04:01.000 Let's make it sec group security group. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 03:57.000 --> 04:01.000 Let's make it sec group security group. 69 04:01.000 --> 04:04.000 So we'll make it essentially still security group one. 70 04:04.000 --> 04:06.000 Let's try that again. 71 04:06.000 --> 04:08.000 Little happier this time. 72 04:08.000 --> 04:11.000 Now our instance has successfully launched. 73 04:11.000 --> 04:14.000 Let's go back to our overall instance page. 74 04:14.000 --> 04:16.000 We can see that it's currently being deployed. 75 04:16.000 --> 04:20.000 Let's give this just a moment and let it complete properly. 76 04:20.000 --> 04:22.000 So we jumped ahead just a couple minutes. 77 04:22.000 --> 04:25.470 This doesn't take long, but we see now that our instant state is in fact 78 04:25.470 --> 04:30.000 running and it has passed both status checks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 04:30.000 --> 04:37.620 So in this video, we just deployed a Linux VM into our subnet in our VPC so 80 04:37.620 --> 04:41.910 that when we get cloud on ramp up and running, we'll have something to actually 81 04:41.910 --> 04:43.000 test our connectivity. 82 04:43.000 --> 04:49.290 Next, we have to make sure that we have a subscription for the catalyst 8000 V 83 04:49.290 --> 04:53.000 before we can deploy this using cloud on ramp. 84 04:53.000 --> 04:56.000 So we'll take a look at that in the next video.