WEBVTT

1
00:03.420 --> 00:06.120
So let's go ahead and work through our solution.

2
00:06.120 --> 00:09.720
We'll start here in the AWS console.

3
00:09.720 --> 00:12.540
For our first task, we're supposed to add

4
00:12.540 --> 00:14.910
an additional Amazon Linux host

5
00:14.910 --> 00:18.780
called SRV2 in subnet 20.

6
00:18.780 --> 00:21.030
So the easiest way to start this

7
00:21.030 --> 00:23.160
is right from the VPC dashboard,

8
00:23.160 --> 00:26.310
we'll just launch an EC2 instance.

9
00:26.310 --> 00:28.173
This is to be called SRV2.

10
00:29.160 --> 00:31.020
If we scroll down,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.160 --> 00:31.020
If we scroll down,

11
00:31.020 --> 00:34.140
the default image actually is Amazon Linux.

12
00:34.140 --> 00:36.780
So we can just leave this at its default.

13
00:36.780 --> 00:38.910
Let's scroll down further.

14
00:38.910 --> 00:42.030
The instance type, once again, is going to be fine.

15
00:42.030 --> 00:44.253
We do have to apply our key pair.

16
00:47.790 --> 00:50.340
So we'll scroll down to network settings.

17
00:50.340 --> 00:52.140
Here, we'll hit edit.

18
00:52.140 --> 00:55.350
Now, in this case, it defaulted to subnet 20,

19
00:55.350 --> 00:57.420
as it did previously.

20
00:57.420 --> 01:00.600
So, really, all we have to do in here is,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:57.420 --> 01:00.600
So, really, all we have to do in here is,

21
01:00.600 --> 01:04.230
A, decide if we want to give it a public IP address.

22
01:04.230 --> 01:06.150
We're not really gonna use it in this example,

23
01:06.150 --> 01:07.440
but we can go ahead and give it one

24
01:07.440 --> 01:09.600
just in case we decide to use it.

25
01:09.600 --> 01:13.380
And we're gonna choose our existing security group.

26
01:13.380 --> 01:17.460
And once again, we'll choose our SG1 security group.

27
01:17.460 --> 01:20.160
Then we'll go ahead and launch the instance.

28
01:20.160 --> 01:23.160
In this particular case, we don't even have to worry about

29
01:23.160 --> 01:26.490
the connects to instance, we'll just go right to instances

30
01:26.490 --> 01:29.250
and make sure this fires up correctly.

31
01:29.250 --> 01:31.560
As we can see, it's currently pending,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:29.250 --> 01:31.560
As we can see, it's currently pending,

32
01:31.560 --> 01:33.210
so let's wait till it starts up,

33
01:33.210 --> 01:36.570
because we will need its private IP address

34
01:36.570 --> 01:40.380
so that we can connect to it and verify connectivity.

35
01:40.380 --> 01:42.120
So now it's been a few minutes,

36
01:42.120 --> 01:45.750
and it has now passed both of the status checks.

37
01:45.750 --> 01:49.170
So now let's go ahead and click on server two.

38
01:49.170 --> 01:54.170
What we're looking for here is its private IPV4 address.

39
01:54.690 --> 01:56.760
We can see here that it's been given an address

40
01:56.760 --> 02:00.930
of 10.20.20.32.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:56.760 --> 02:00.930
of 10.20.20.32.

41
02:00.930 --> 02:04.110
So what we wanna do next, for our second requirement

42
02:04.110 --> 02:05.940
in our challenge, is make sure

43
02:05.940 --> 02:09.450
that we can ping that host from workstation one.

44
02:09.450 --> 02:12.240
So let's jump over to workstation one.

45
02:12.240 --> 02:15.870
In my environment, I don't have direct management access

46
02:15.870 --> 02:17.760
to my workstation one.

47
02:17.760 --> 02:20.820
So I'm simply using my router one to SSH

48
02:20.820 --> 02:23.220
over to that Linux workstation.

49
02:23.220 --> 02:25.830
So now I'm logged into workstation one,

50
02:25.830 --> 02:28.260
and we can verify our connectivity

51
02:28.260 --> 02:33.260
by pinging 10.20.20.32.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:28.260 --> 02:33.260
by pinging 10.20.20.32.

52
02:33.300 --> 02:36.150
As we can see, this is successful.

53
02:36.150 --> 02:39.120
All of our pings are going through fine.

54
02:39.120 --> 02:41.430
For step three of our challenge,

55
02:41.430 --> 02:44.730
we're now supposed to modify our security group

56
02:44.730 --> 02:47.580
to allow SSH through.

57
02:47.580 --> 02:50.010
Well, before we do that, let's see what happens

58
02:50.010 --> 02:52.170
if we currently try to SSH

59
02:52.170 --> 02:55.530
to 10.20.20.32.

60
02:55.530 --> 02:59.730
What we see is it's essentially sitting here timing out.

61
02:59.730 --> 03:01.710
So we'll just break out of this,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:59.730 --> 03:01.710
So we'll just break out of this,

62
03:01.710 --> 03:04.710
and let's go over and modify our security group.

63
03:04.710 --> 03:07.860
So back over to the AWS console,

64
03:07.860 --> 03:10.860
so let's go back to our VPC console.

65
03:10.860 --> 03:13.170
Let's go to our security groups,

66
03:13.170 --> 03:15.930
we'll click on our security group one.

67
03:15.930 --> 03:18.180
We'll go to inbound rules,

68
03:18.180 --> 03:21.390
and we're gonna wanna edit our inbound rules.

69
03:21.390 --> 03:24.360
What we wanna do is we wanna add a rule.

70
03:24.360 --> 03:27.630
In our type, there's a setting here for SSH,

71
03:27.630 --> 03:29.460
so we'll click on that.

72
03:29.460 --> 03:32.970
And once again, we'll just allow this from everywhere,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:29.460 --> 03:32.970
And once again, we'll just allow this from everywhere,

73
03:32.970 --> 03:35.280
or anywhere as they call it.

74
03:35.280 --> 03:37.380
We'll then save the rule.

75
03:37.380 --> 03:39.780
And for our final step in our challenge,

76
03:39.780 --> 03:42.120
let's go back over to our workstation

77
03:42.120 --> 03:47.120
and see if we can now SSH into this new Linux server.

78
03:47.400 --> 03:50.610
So we can simply hit up to repeat the last command,

79
03:50.610 --> 03:53.070
hit Enter, and notice,

80
03:53.070 --> 03:57.930
it's now challenging us with the RSA fingerprint.

81
03:57.930 --> 04:00.720
Now we can say, yes, we want to continue connecting.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:57.930 --> 04:00.720
Now we can say, yes, we want to continue connecting.

82
04:00.720 --> 04:03.720
The fact of the matter is we're not gonna be able to do this

83
04:03.720 --> 04:08.340
because of the way AWS sets up their authentication

84
04:08.340 --> 04:11.340
for their Linux servers by default.

85
04:11.340 --> 04:15.330
But all we really needed to see here is that our SSH

86
04:15.330 --> 04:19.140
is actually getting through to that server now.

87
04:19.140 --> 04:21.390
So this is now working successfully,

88
04:21.390 --> 04:24.120
and we have completed the challenge.

89
04:24.120 --> 04:27.120
That also means that we've covered everything

90
04:27.120 --> 04:29.970
that we need to cover in this skill.

91
04:29.970 --> 04:34.290
So congratulations on completing Configure IOS XE
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:29.970 --> 04:34.290
So congratulations on completing Configure IOS XE

92
04:34.290 --> 04:38.940
for IPSec VPN to AWS VPC.

93
04:38.940 --> 04:41.400
I hope this has been informative for you,

94
04:41.400 --> 04:43.443
and I'd like to thank you for viewing.