1
00:00:00,900 --> 00:00:02,420
Alone will come back.

2
00:00:02,420 --> 00:00:04,560
So let's cover now the APCP.

3
00:00:04,730 --> 00:00:10,190
Basically the reason being is when you need to connect to the.

4
00:00:10,200 --> 00:00:17,640
Remember we said that the VPC is a virtual data center or a virtual containment of your services servers

5
00:00:18,260 --> 00:00:22,210
and in databases inside us.

6
00:00:22,280 --> 00:00:30,170
What if I have multiple PCs for instance a company could have at this PC development the PC and the

7
00:00:30,170 --> 00:00:31,550
production VBC.

8
00:00:31,640 --> 00:00:32,320
Right.

9
00:00:32,630 --> 00:00:37,580
If there is a file between them that I need to share their files between them that I need to share what

10
00:00:37,580 --> 00:00:43,340
can I do if they are completely separate then it always has a feature called VCP.

11
00:00:43,370 --> 00:00:50,990
Basically you can have one or more subnets from VPC that need to communicate with one or more subnets

12
00:00:51,020 --> 00:00:52,140
in the PC.

13
00:00:52,250 --> 00:00:56,180
So they do peering between the two PCs and that peering.

14
00:00:56,240 --> 00:01:02,230
And then you edit your security groups and security in order to allow these subnets on the on the PC

15
00:01:02,240 --> 00:01:05,080
to talk to the subnets on the CPB.

16
00:01:05,090 --> 00:01:13,710
The question I have is now can we have the PCs from the same account talk to each other.

17
00:01:13,760 --> 00:01:18,170
Yes you can have the PC from account a.

18
00:01:18,260 --> 00:01:25,630
So that's a completely like a separate company for corporate talk to the PC from a different corporate.

19
00:01:25,700 --> 00:01:26,560
Yes.

20
00:01:26,930 --> 00:01:31,340
Are there any conditions going to have the PCs in the same region to appear with each other.

21
00:01:31,340 --> 00:01:32,200
Yes.

22
00:01:32,510 --> 00:01:36,620
Can I have the PCs from different regions paired with each other.

23
00:01:36,620 --> 00:01:37,240
No.

24
00:01:37,550 --> 00:01:44,840
So the VBC pairing can only be done between the PCs in the same region that belong to the same or different

25
00:01:44,840 --> 00:01:46,300
accounts.

26
00:01:46,590 --> 00:01:48,540
And the VPC is a one to one.

27
00:01:48,580 --> 00:01:53,720
The peering is one to one relationship so you cannot have them as you will see later on.

28
00:01:53,730 --> 00:01:57,320
You cannot have VTC peer with another one.

29
00:01:57,600 --> 00:02:02,610
And then the other one peer with the third one and then you assume that the first and third appeared

30
00:02:02,810 --> 00:02:03,720
anywhere anyway.

31
00:02:03,870 --> 00:02:05,400
This is just a quick introduction.

32
00:02:05,400 --> 00:02:11,970
Let's dig into the details.

33
00:02:12,220 --> 00:02:13,530
So here is how it looks like.

34
00:02:13,640 --> 00:02:23,230
So I have here an example a VPC A and B PCB and I want to have this specific instance so it can be as

35
00:02:23,230 --> 00:02:25,660
granular as one instance.

36
00:02:25,660 --> 00:02:30,910
Talk to one instance or instance talk to subnet or Cybernetica subnet or multiple subnets talk to multiple

37
00:02:30,910 --> 00:02:31,760
subnets.

38
00:02:32,140 --> 00:02:39,060
So here I have when you see that there is an IP address and a slash 32 That means its a host address

39
00:02:39,080 --> 00:02:44,830
with a single computer or a single server or a single PC or a single.

40
00:02:44,830 --> 00:02:46,950
In our case is a single instance.

41
00:02:46,990 --> 00:02:52,410
So its like 32 means a single instance to get a single IP address a host IP address.

42
00:02:52,600 --> 00:02:57,250
So this instance would like to talk to this instance and also its a host on the other side.

43
00:02:57,250 --> 00:02:58,520
Host IP address.

44
00:02:58,700 --> 00:02:59,210
OK.

45
00:02:59,440 --> 00:03:01,270
This one is secured on the submit.

46
00:03:01,270 --> 00:03:07,540
This one is secured and the Submit can establish VBC being between VBC a and b to allow them to talk.

47
00:03:07,570 --> 00:03:13,270
Yes there is one condition that has to be satisfied in order for the two to be able to communicate with

48
00:03:13,270 --> 00:03:13,890
each other.

49
00:03:14,230 --> 00:03:16,610
And the main one or the the

50
00:03:19,880 --> 00:03:29,610
and the condition is decide that blocks from the PC and the center blocks from VPC they should not overlap.

51
00:03:29,630 --> 00:03:34,850
So if you're trying to do that if you are even on the console and trying to configure it disappearing

52
00:03:34,850 --> 00:03:41,030
between to the PCs where they have overlapping solder blocks it will not go through to not be accepted

53
00:03:41,150 --> 00:03:43,030
and the connection will not be established.

54
00:03:43,310 --> 00:03:48,310
There is to be another condition that the two PCs must be in a single region in the same region.

55
00:03:48,320 --> 00:03:57,790
But this doesn't exist anymore as of November 2017 when it has allowed entire region.

56
00:03:57,850 --> 00:04:03,360
So you can peer between two PCs one could be in Ohio and that could be and talk to you.

57
00:04:03,440 --> 00:04:04,620
So that is allowed.

58
00:04:04,640 --> 00:04:11,390
And the good news is the traffic in that case crosses the database backbone and doesn't go on the internet

59
00:04:11,390 --> 00:04:15,710
between the BBC's entire region and it is encrypted as well.

60
00:04:15,800 --> 00:04:22,130
So any company that would like to expand or have the PC peering traffic between TV PCs in two different

61
00:04:22,130 --> 00:04:24,140
region is now supported.

62
00:04:24,500 --> 00:04:31,340
Now can I just initiate from VPC a request to appear with the PCB and it so happens no.

63
00:04:31,880 --> 00:04:38,350
The question from the site that someone has to initiate the request so let's say BBCA account owner

64
00:04:38,510 --> 00:04:46,790
were issued the request to appear with the PCB the Ribisi owner will be notified and he has to accept

65
00:04:46,850 --> 00:04:51,360
the request in order for the Pyrenean connection to happen between them.

66
00:04:55,680 --> 00:05:03,330
So we disappearing is appearing connection is a networking connection between two PCs and it can do

67
00:05:03,790 --> 00:05:06,340
for NITV sex on top of it.

68
00:05:08,790 --> 00:05:12,390
Instance in an instance in either VBC can communicate with each other.

69
00:05:12,390 --> 00:05:18,850
So once you allow it by security and you're routing and the disappearing connection is initiated from

70
00:05:18,850 --> 00:05:25,230
one side and accept it from the other side and is up then you can do the communication between the incenses

71
00:05:25,230 --> 00:05:26,570
on both sides.

72
00:05:26,970 --> 00:05:33,420
You can create a VPN connection between your own devices or the in the same account or a PC from your

73
00:05:33,420 --> 00:05:36,090
account with another account could be in the same region.

74
00:05:36,090 --> 00:05:39,560
Or they could be in separate regions within it.

75
00:05:39,720 --> 00:05:44,110
Maybe an example would be faced with a scenario that they will tell you you have it disappearing which

76
00:05:44,230 --> 00:05:47,160
we see in the BCB and you want to make it fault tolerant.

77
00:05:47,160 --> 00:05:48,110
What do you do.

78
00:05:48,360 --> 00:05:52,360
So one of the choices might be do another week disappear.

79
00:05:52,500 --> 00:05:53,770
You can't.

80
00:05:53,800 --> 00:05:54,710
It's not allowed.

81
00:05:54,780 --> 00:06:01,010
And this is as all the other E.W. are services it's a service provided by us.

82
00:06:01,040 --> 00:06:07,140
We don't know the details of which but I assure you that this is faultline highly available and there

83
00:06:07,140 --> 00:06:09,390
is no congestion or bottleneck.

84
00:06:09,390 --> 00:06:14,860
So basically you can push as much traffic as you wish across and it will handle that.

85
00:06:15,120 --> 00:06:18,910
And there is no single point of failure so you don't need to worry about establishing a second one.

86
00:06:18,910 --> 00:06:27,960
This is your job to make sure that there is always a routing path between your two PCs in the same region.

87
00:06:27,960 --> 00:06:33,330
So either use the existing infrastructure of a VPC to create the APCP.

88
00:06:33,540 --> 00:06:34,200
What does it mean.

89
00:06:34,200 --> 00:06:35,920
It means it's not a gateway.

90
00:06:35,940 --> 00:06:37,060
They don't get to it.

91
00:06:37,110 --> 00:06:41,710
They don't add any physical hardware and it's not a VPN connection between the PCs.

92
00:06:41,730 --> 00:06:42,750
So what is it.

93
00:06:42,810 --> 00:06:43,760
It's not your business.

94
00:06:43,770 --> 00:06:45,250
It really takes care of that.

95
00:06:45,270 --> 00:06:50,550
But they assure you that this is not an extra piece of hardware that they are adding or a gateway or

96
00:06:50,550 --> 00:06:53,460
a VPN or anything in order to allow that.

97
00:06:53,490 --> 00:06:57,030
So it uses the existing areas infrastructure.

98
00:06:57,030 --> 00:07:00,510
The second thing is as I just mentioned it's not.

99
00:07:00,510 --> 00:07:07,020
There is no single point of failure in the VPC and it can never be your bottleneck in terms of bandwidth

100
00:07:07,050 --> 00:07:08,230
and performance.

101
00:07:08,410 --> 00:07:09,540
What why would I use it.

102
00:07:09,540 --> 00:07:11,640
For example use cases.

103
00:07:11,640 --> 00:07:17,370
The first one is if you have files that you would like to share between multiple The PCs appear between

104
00:07:17,370 --> 00:07:24,650
the PCs allow the subnets the routing from the side to that side and the other way around open the.

105
00:07:24,810 --> 00:07:30,690
Adjust your security groups for the instances that need to communicate with each other to make sure

106
00:07:30,690 --> 00:07:37,030
that they can communicate with one another and boom their request.

107
00:07:37,120 --> 00:07:38,740
The other side will accept the request.

108
00:07:38,780 --> 00:07:41,990
The BBC period comes up and you are ready to go.

109
00:07:42,310 --> 00:07:47,950
And also you can use it to allow other PCs to access the resources you have in one of your VIPs.

110
00:07:47,950 --> 00:07:56,440
So let's say for instance on E.W. as a company hosts just hypothetically saying that let's say a payment

111
00:07:56,440 --> 00:08:04,860
gateway so basically a gateway that can process online online transactions credit cards or whatever.

112
00:08:05,030 --> 00:08:09,940
And the other Ribisi is they like the service and they would like to put it to subscribe to it.

113
00:08:10,070 --> 00:08:13,990
So they need to peer they payment servers or applications.

114
00:08:14,940 --> 00:08:21,690
That Have there been activities they need to build these with the payment gateway servers that will

115
00:08:21,690 --> 00:08:28,470
process that the transaction and then will send a confirmation back or a decline message.

116
00:08:28,470 --> 00:08:31,790
So the transaction is carried on the site.

117
00:08:31,890 --> 00:08:37,800
So that's one example where you will need to have resources in one we do that the other VCs are interested

118
00:08:37,800 --> 00:08:38,160
in.

119
00:08:38,160 --> 00:08:40,440
And they like to reach out to.

120
00:08:40,520 --> 00:08:42,870
And you mentioned to establish with disappearing.

121
00:08:42,890 --> 00:08:50,650
Then there is a request for the PC or local PC that they will initiate a request to the owner of the

122
00:08:50,650 --> 00:08:53,130
other PC that I would like to appear with.

123
00:08:53,590 --> 00:08:59,860
And we VBC the PC can be owned by you or can be owned by another account.

124
00:09:00,040 --> 00:09:05,400
The very important thing to remember is that blocks the size of blocks cannot overlap and they cannot

125
00:09:05,410 --> 00:09:13,970
be the same between the peering with PCs and the owner of the PC will accept the BBC connection and

126
00:09:13,970 --> 00:09:22,050
activate the peering connection now after the connection is initiated the request is initiated and is

127
00:09:22,050 --> 00:09:23,960
accepted and the connection is up.

128
00:09:24,120 --> 00:09:31,500
You need to do two things you need to update your routing tables in either side on both sides in order

129
00:09:31,500 --> 00:09:38,050
to make sure that BBCA can't access the Submit or the specific IP addresses on the PCB.

130
00:09:38,250 --> 00:09:40,180
So what you need to get to in this case.

131
00:09:40,290 --> 00:09:46,890
Now when we go to our table we right destination and then I have a target that I need to specify right.

132
00:09:46,950 --> 00:09:52,570
So in the internet I used to say AGW and the VPN I use to say VZW.

133
00:09:52,570 --> 00:09:54,730
How about in peering.

134
00:09:54,810 --> 00:10:04,260
You have PC X and then the ID of the peering connection case of the VPC peering is acronym PCI-X and

135
00:10:04,260 --> 00:10:07,130
then the ID of the specific connection.

136
00:10:07,230 --> 00:10:12,010
And of course when you created you will find that new appearing connections under the VPC

137
00:10:15,410 --> 00:10:20,210
method you mentioned them are easy to adjust the security groups in order to allow that.

138
00:10:20,250 --> 00:10:26,220
One important thing you can do here then if you have the PC and the PCB and I have here an instance

139
00:10:26,550 --> 00:10:36,140
with security grew sick b and here with security groups like a for instance or Sigsbee you can once

140
00:10:36,140 --> 00:10:46,130
the peering is up you can hear different rules that the source is Security Group A and then allow all

141
00:10:46,130 --> 00:10:48,290
the protocols you want.

142
00:10:48,390 --> 00:10:55,890
So can a reference in the in-bound rules on the on the side that the source is the security group on

143
00:10:55,890 --> 00:10:56,490
the other side.

144
00:10:56,490 --> 00:10:57,740
Yes you can.

145
00:10:57,900 --> 00:11:02,590
Now for my outbound you can specify the destination in a security group.

146
00:11:02,640 --> 00:11:03,510
Yes you can.

147
00:11:03,750 --> 00:11:07,010
You can now start referencing across the peering connection.

148
00:11:07,110 --> 00:11:10,290
Security Groups as a source of information from either side.

149
00:11:10,290 --> 00:11:12,960
One important thing to note about that.

150
00:11:12,960 --> 00:11:20,720
So now in this case we have a peering a VPC being a connection between the PC and the PCC.

151
00:11:21,270 --> 00:11:28,340
And also I have a different and connection between the PC and the PC game here is the PC ID PCX ID they

152
00:11:28,350 --> 00:11:29,440
are different.

153
00:11:29,640 --> 00:11:35,490
You need to know that the VBC building is a one to one relationship so basically ate with C and the

154
00:11:35,490 --> 00:11:37,900
other one is a with B.

155
00:11:37,950 --> 00:11:38,700
The second one.

156
00:11:38,700 --> 00:11:46,260
And very very important thing to note here is if I have this set up can subnets from VBC communicate

157
00:11:46,260 --> 00:11:54,210
with subnets from within B B given that they are both connected to the PPC and the traffic flow this

158
00:11:54,210 --> 00:11:57,210
way the answer is no.

159
00:11:57,540 --> 00:11:58,280
Why.

160
00:11:58,290 --> 00:12:02,370
Because VBC peering does not allow what we call edge to edge routing.

161
00:12:02,370 --> 00:12:11,180
So basically the PCB and a route exchanged between these two sides what ever I learn at a root from

162
00:12:11,180 --> 00:12:11,570
B.

163
00:12:11,640 --> 00:12:20,390
I will never exchange with C so C will never know that that is connected to B and A knows about B it

164
00:12:20,430 --> 00:12:27,450
will never find out that because the prerequisite for C communicating with B is C has to know Rood's

165
00:12:27,630 --> 00:12:36,120
about B and B has to know Root about C so it will never ever receive or know something about B and share

166
00:12:36,120 --> 00:12:41,560
it with C in terms of routing or subnets or prefixes and vice versa.

167
00:12:41,580 --> 00:12:48,850
The PCA will never share with the pc be what it learns about the PC C K.

168
00:12:49,010 --> 00:12:56,250
So transitive feeling is not there or this is code also edge to edge routing so what I exchanged across

169
00:12:56,250 --> 00:12:59,970
the VPC Pierian connection will never be shared with anyone else.

170
00:13:00,090 --> 00:13:08,960
Even if C B here was paired with VPC the I cannot it cannot communicate with the through B.

171
00:13:09,360 --> 00:13:13,480
So what if i want see and B to share some files directly.

172
00:13:13,560 --> 00:13:17,430
Then you have to create another connection between them direct.

173
00:13:17,600 --> 00:13:20,750
So you have to see them to exchange information.

174
00:13:21,030 --> 00:13:25,160
Then they have to be a Darity that say we have a scenario like this one.

175
00:13:25,380 --> 00:13:32,770
So I have a corporate data center or a headquarter connected to its own VBC VBC in this case.

176
00:13:33,090 --> 00:13:38,700
Connected How to be through a VPN connection could be through a direct connection of two means to connect

177
00:13:38,700 --> 00:13:45,910
from a remote location to repeat to your PC and in the various.

178
00:13:46,050 --> 00:13:47,390
One is the VPN connection.

179
00:13:47,400 --> 00:13:53,780
I'd be sick of connecting over the Internet or over the next and the other one is the high speed low

180
00:13:53,790 --> 00:13:59,690
latency performance that the connection is good.

181
00:13:59,920 --> 00:14:06,370
Now the PC ate my PC has appeared in connection with a different VPC in the same account or in a different

182
00:14:06,370 --> 00:14:09,030
account.

183
00:14:09,050 --> 00:14:16,600
Now I am concerned about that fault tolerant of this connection so I have this connection only and I

184
00:14:16,600 --> 00:14:19,960
want to harden the set of the set up.

185
00:14:19,960 --> 00:14:21,130
What do I do.

186
00:14:21,640 --> 00:14:29,470
So one idea might be why don't you have a direct connection this way and this means if this connection

187
00:14:29,470 --> 00:14:36,100
fails the the dissenter will route to a through B doesn't work.

188
00:14:36,120 --> 00:14:43,300
Not really option why because it's true that the BCB will know root about vitiate but it will never

189
00:14:43,360 --> 00:14:49,620
ever share it with the datacenter or headquarter through the connect or VPN.

190
00:14:49,660 --> 00:14:57,980
It will never hear and this is called that the disappearing does not support edge to edge routing.

191
00:14:58,570 --> 00:15:05,980
So here I have VPC as an edge sharing route with B but this age B will never share it with the third

192
00:15:05,980 --> 00:15:07,890
one or the third Eduljee that isn't

193
00:15:11,160 --> 00:15:17,200
to what I do in this case one might say if you want to harden the set up then you need to have a second

194
00:15:17,200 --> 00:15:18,580
opinion connection here.

195
00:15:18,630 --> 00:15:20,200
Again this is not a sport.

196
00:15:20,220 --> 00:15:25,820
You cannot have two peering connections between the same two pieces at the same time.

197
00:15:26,190 --> 00:15:27,020
And why is that.

198
00:15:27,030 --> 00:15:34,560
Because it has promised that they have the period connection as a redundant faltering highly available

199
00:15:34,560 --> 00:15:37,310
high performance bottleneck.

200
00:15:38,010 --> 00:15:40,500
So what can I do in the set up if I want to harden.

201
00:15:40,530 --> 00:15:45,640
All you need to harden is you need to harden the connection from the data center to VTC.

202
00:15:45,930 --> 00:15:55,080
What if I need to communicate with the B C B then you need to establish that connection with the PCB.

203
00:15:55,110 --> 00:16:01,790
Can I add any condition or at any cost route to a through B.

204
00:16:01,800 --> 00:16:02,130
No.

205
00:16:02,130 --> 00:16:04,200
Can I get it out to be through a.

206
00:16:04,260 --> 00:16:05,090
No.

207
00:16:05,580 --> 00:16:11,140
So all you need to be concerned about is the connection ribbon connection which you can make it's redundant

208
00:16:11,190 --> 00:16:14,400
and that means you have a highly available fault alone.

209
00:16:14,580 --> 00:16:22,860
In this case limitations of disappearing the connection between the PCs that have matching or overlapping

210
00:16:22,860 --> 00:16:24,470
ID before Id resets.

211
00:16:24,630 --> 00:16:28,730
So the Roeske is not supported and this is a simple display period.

212
00:16:29,280 --> 00:16:36,060
Your software or your kernel if your IP is one that 1.1 that one and my IP on the other side is on that

213
00:16:36,060 --> 00:16:44,760
one that one that one if you do a ping S-sh or anything here and your intent is to send it to one of

214
00:16:45,000 --> 00:16:46,710
the two on that one.

215
00:16:46,740 --> 00:16:52,870
What would force the kernel here to send it outside if they can already know that what the grounded

216
00:16:52,870 --> 00:16:54,560
one is myself.

217
00:16:54,570 --> 00:16:57,540
Is this easy to install.

218
00:16:57,550 --> 00:16:59,530
Or is this computer or was the.

219
00:16:59,840 --> 00:17:00,280
OK.

220
00:17:00,400 --> 00:17:02,280
So these are overlapping IPs.

221
00:17:02,280 --> 00:17:06,600
Similarly when you do peering between two PCs What's your intent.

222
00:17:06,600 --> 00:17:11,910
The intent is you would like to have some easy to instances from here to communicate in some instances

223
00:17:11,910 --> 00:17:12,830
from the other side.

224
00:17:13,110 --> 00:17:18,770
If they have the same IP addresses your implied router will never send that outside.

225
00:17:18,770 --> 00:17:21,860
You will always think that belongs to my side or block.

226
00:17:21,990 --> 00:17:27,260
So it has to stay with them so the traffic will never leave they see two instance to the router and

227
00:17:27,300 --> 00:17:31,330
if for any reason it happened then the router will send it back.

228
00:17:31,440 --> 00:17:34,140
It will never send it outside.

229
00:17:34,140 --> 00:17:38,890
Second one is you can have the disappearing between the PCs in different regions.

230
00:17:38,910 --> 00:17:46,210
There is a limit of how many PCs you can have per VPC and the active is 50 and the spending is 25 pending

231
00:17:46,230 --> 00:17:47,720
here means you have requests.

232
00:17:47,730 --> 00:17:51,110
But the other side or the other party did not respond yet.

233
00:17:51,170 --> 00:17:55,710
So you could have up to 50 50 VPC disappearing spare VBC.

234
00:17:55,830 --> 00:18:01,500
And remember that it does not support transitive peering relationships so if you have that shape that

235
00:18:01,500 --> 00:18:08,400
we talked about before in the exam and they tell you that B would like to communicate we'll see them.

236
00:18:08,550 --> 00:18:10,530
Can they do it through Of course not.

237
00:18:10,530 --> 00:18:12,610
They have to appear directly with each other.

238
00:18:12,810 --> 00:18:20,280
And also you cannot have if you have VBC peering between two PCs you cannot have a second one established

239
00:18:20,280 --> 00:18:20,910
between them.

240
00:18:20,910 --> 00:18:22,340
At the same time.

241
00:18:22,500 --> 00:18:23,190
Now what.

242
00:18:23,220 --> 00:18:23,860
Good thing.

243
00:18:23,890 --> 00:18:28,660
And we will talk about placement groups later on when we talk about easy two instances.

244
00:18:28,680 --> 00:18:36,840
But the placement group is basically a cluster of two instances in the vicinity of each other so basically

245
00:18:36,840 --> 00:18:39,310
in that they are in the same availability zone.

246
00:18:39,570 --> 00:18:43,670
And the reason why you have that is you want to do high performance computing and you like to ensure

247
00:18:43,910 --> 00:18:49,060
low latency and high performance as the incenses communicate with one another.

248
00:18:49,300 --> 00:18:49,850
OK.

249
00:18:50,040 --> 00:18:57,480
So here are what we are saying is if you have two PCs peered together you can have a cluster across

250
00:18:57,480 --> 00:19:03,360
them you can have members of the cluster here in the cluster here and you can have all of these in a

251
00:19:03,360 --> 00:19:04,180
placement group

252
00:19:07,190 --> 00:19:11,170
unicast reverse path forwarding in a BBC BNN connection is not supported.

253
00:19:11,260 --> 00:19:13,630
You don't need to worry much about about this one.

254
00:19:13,630 --> 00:19:21,860
Basically this is to ensure in multicast and similar applications that if the traffic comes to me I

255
00:19:21,860 --> 00:19:29,630
want to make sure that the reverse path is the IGP or the routing protocol path or the path back to

256
00:19:29,810 --> 00:19:30,940
the source.

257
00:19:30,950 --> 00:19:37,790
So in the next lecture we're going to cover the virtual private network option in the PC.

258
00:19:37,910 --> 00:19:44,370
And for this one we learned that I can peer two pieces together they can be in the same account or different

259
00:19:44,720 --> 00:19:50,930
between different accounts provided they are in the same region overlapping IPS is not supported transitive

260
00:19:51,080 --> 00:19:57,330
peering is not supported and you need to update your routing on either side on both sides.

261
00:19:57,440 --> 00:20:03,050
And your security groups on both sides in order to be able to peer between them whereas if it is not

262
00:20:03,070 --> 00:20:09,860
supported over if I have a hearing with B and peering with C does not mean B and C can't talk to each

263
00:20:09,860 --> 00:20:10,810
other through a.

264
00:20:10,920 --> 00:20:15,300
So they have to peer with each other if they need to communicate or share files.

265
00:20:15,470 --> 00:20:20,330
So I'll see you in the next lecture and we talk about the VPC virtual private networks.