-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
372 lines (210 loc) · 13 KB
/
atom.xml
File metadata and controls
372 lines (210 loc) · 13 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
<channel>
<title type="text">Edge Cloud</title>
<subtitle type="html">On the edge of cloud computing</subtitle>
<updated>2024-09-03T13:08:21-07:00</updated>
<id>https://www.edge-cloud.net/atom.xml</id>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<description>On the edge to cloud computing</description>
<icon>/assets/images/favicon-32x32.png</icon>
<logo>/assets/images/edgecloud.png</logo>
<webfeeds:cover image="https://www.edge-cloud.net/assets/images/unsplash-image-1.jpg" />
<webfeeds:icon>/assets/images/favicon-32x32.png</webfeeds:icon>
<webfeeds:logo>/assets/images/edgecloud.svg</webfeeds:logo>
<webfeeds:accentColor>5197ad</webfeeds:accentColor>
<webfeeds:related layout="card" target="browser" />
<webfeeds:analytics id="UA-39076327-2" engine="GoogleAnalytics" />
<link rel="self" type="application/atom+xml" href="https://www.edge-cloud.net/atom.xml" />
<link rel="alternate" type="text/html" href="https://www.edge-cloud.net" />
<entry>
<title>Cost considerations for centralized NAT with Transit Gateway</title>
<id>https://www.edge-cloud.net/2021/01/01/tgw-ngw-cost-breakeven/</id>
<updated>2024-09-03T13:07:49-07:00</updated>
<published>2024-09-03T13:07:49-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2021/01/01/tgw-ngw-cost-breakeven/" />
<summary type="html">Determining the break-even point when a centralized NAT approach via Transit Gateway outperforms a decentralized NAT approach.</summary>
<content type="html">Intro of what to accomplish Heading 1 Heading 1.1 Bold Note: This is a notice box # # Code # Figure 1: Setup Overview of EC2-based VPN endpoint for Site-to-Site VPN with AWS \[Price_{NGW}=( 720 hr / month \cdot Num_{VPC} \cdot Cost_{NGW-Attachment} ) + (traffic \cdot Cost_{NGW-Traffic})\] \[Price_{TGW+NGW}= ( 720 hr / month \cdot Num_{VPC} \cdot Cost_{TGW-Attachment} ) + \\ ( 720 hr / month \cdot Num_{AZ} \cdot Cost_{NGW-Attachment} ) + \\ (traffic \cdot (...</content>
<category term="AWS" />
<category term="Network" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>Title goes here</title>
<id>https://www.edge-cloud.net/2022/01/01/template/</id>
<updated>2024-09-03T13:07:49-07:00</updated>
<published>2024-09-03T13:07:49-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2022/01/01/template/" />
<summary type="html">Brief description goes here</summary>
<content type="html">Intro of what to accomplish
Heading 1
Heading 1.1
Bold
Note: This is a notice box
#
# Code
#
Font Awesome Examples
Picture
Figure 1: Setup Overview of EC2-based VPN endpoint for Site-to-Site VPN with AWS
Math
\(Buffer (Mbit) = bandwidth (Mbit/s) × delay (s)\)
</content>
<category term="AWS" />
<category term="Network" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>Securing your AWS networks</title>
<id>https://www.edge-cloud.net/2020/01/03/securing-your-aws-network/</id>
<updated>2024-09-03T13:07:49-07:00</updated>
<published>2024-09-03T13:07:49-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2020/01/03/securing-your-aws-network/" />
<summary type="html">Brief description goes here</summary>
<content type="html">Intro of what to accomplish Scope AWS Well Architected - Security Pillar Figure 1: Protecting network and host-level boundaries Toolbox for securing AWS networks Amazon VPC Security Groups Figure 2: Security Groups Amazon VPC Network ACLs (Access Control Lists) Figure 3: Network Access Control Lists (ACLs) AWS WAF (Web Application Firewall) Figure 4: Web Application Firewalls (WAF) AWS Firewall Manager Figure 5: Firewall Manager AWS Shield Figure 6: AWS Shield AWS Transit Gateway with 3rd...</content>
<category term="AWS" />
<category term="Network" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>Direct Connect Public VIF for S3 traffic only</title>
<id>https://www.edge-cloud.net/2022/07/15/aws-dx-public-vid-for-s3-only/</id>
<updated>2024-09-03T13:07:49-07:00</updated>
<published>2024-09-03T13:07:49-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2022/07/15/aws-dx-public-vid-for-s3-only/" />
<summary type="html">How to use a Direct Connect Public VIF solely for S3 traffic only</summary>
<content type="html">Intro of what to accomplish
Heading 1
Heading 1.1
Bold
Note: This is a notice box
#
# Code
#
Figure 1: Setup Overview of EC2-based VPN endpoint for Site-to-Site VPN with AWS
\[Buffer (Mbit) = bandwidth (Mbit/s) × delay (s)\]
</content>
<category term="AWS" />
<category term="Network" />
<category term="Direct-Connect" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>\"Bring your own IP addresses\" (BYOIP) for Amazon EC2 [Video]</title>
<id>https://www.edge-cloud.net/2023/08/20/video-bring-your-own-ip-for-amazon-vpc/</id>
<updated>2023-08-20T00:00:00-07:00</updated>
<published>2023-08-20T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2023/08/20/video-bring-your-own-ip-for-amazon-vpc/" />
<summary type="html">YouTube Videos with step-by-step guide for moving IP prefixes to AWS with "Bring your own IP addresses" (BYOIP) for Amazon EC2</summary>
<content type="html"> YouTube Videos accompanying the previous blog post Hands-on with AWS Bring your own IP addresses (BYOIP) in Amazon EC2.
Step-by-step guide for moving IP prefixes to AWS with “Bring your own IP addresses” (BYOIP) for Amazon EC2. Steps with the RIRs ARIN and RIPE are shown, including prepartion of address space.
</content>
<category term="AWS" />
<category term="Network" />
<category term="Video" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>How to move your DNS to Amazon Route 53 [Video]</title>
<id>https://www.edge-cloud.net/2023/07/27/move-your-dns-to-route53/</id>
<updated>2023-07-25T00:00:00-07:00</updated>
<published>2023-07-25T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2023/07/27/move-your-dns-to-route53/" />
<summary type="html">YouTube Videos with step-by-step guide to move your DNS - both registration services and zone file - to Amazon Route 53</summary>
<content type="html"> YouTube Videos accompanying the previous blog post “How to move your DNS to Amazon Route 53”.
Part 1: Zone Services
Part 2: Registration Services
</content>
<category term="AWS" />
<category term="Network" />
<category term="Route-53" />
<category term="Video" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>How to move your DNS to Amazon Route 53</title>
<id>https://www.edge-cloud.net/2023/06/25/move-your-dns-to-route53/</id>
<updated>2023-06-25T00:00:00-07:00</updated>
<published>2023-06-25T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2023/06/25/move-your-dns-to-route53/" />
<summary type="html">Step-by-step guide to move your DNS - both registration services and zone file - to Amazon Route 53</summary>
<content type="html">This blog post will walk through the migration steps of the DNS setup for a public zone to Amazon Route 53. It will include steps for both making Route 53 the DNS service for an existing domain, but also transferring the DNS registration for this domain to Route 53. While it will use Google Domains as the DNS service initially providing the zone and registration service, the steps should be easily transferable to any other...</content>
<category term="AWS" />
<category term="Network" />
<category term="Route-53" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>Random prefix attack mitigation with Amazon Route 53</title>
<id>https://www.edge-cloud.net/2023/06/18/r53-random-prefix-attack-mitigation/</id>
<updated>2023-06-18T00:00:00-07:00</updated>
<published>2023-06-18T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2023/06/18/r53-random-prefix-attack-mitigation/" />
<summary type="html">How to mitigate random prefix attacks - when someone send a lot of traffic to subdomains of your main domain - with Amazon Route 53</summary>
<content type="html">This blog post shows how to mitigate a random prefix attack with Amazon Route 53. While such an attack will not have an impact on performance or availability, owners of the corresponding public hosted zone will incur charges for queries to non-existing subdomains or prefixes. These charges can be prevented via the mitigation presented here. Background What is a random prefix attack With a random prefix attack someone sends large amounts of DNS queries to...</content>
<category term="AWS" />
<category term="Network" />
<category term="Route-53" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>URL Redirect with Amazon CloudFront and Amazon Route 53</title>
<id>https://www.edge-cloud.net/2023/03/20/http-redirect-with-cloudfront/</id>
<updated>2023-03-20T00:00:00-07:00</updated>
<published>2023-03-20T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2023/03/20/http-redirect-with-cloudfront/" />
<summary type="html">How to use Amazon CloudFront and Amazon Route 53 to perform a URL redirect, e.g. from http://about.example.com to http://www.example.com/about.</summary>
<content type="html">A URL redirect, also called URL forwarding, allows you to make a web page available under more than one URL. When a web browser attempts to open a URL that has been redirected, a page with a different URL is opened. This is also indicated in the web browser itself by showing the new URL in the navigation bar. As an example: You might enter the URL https://about.example.com into the browser and be redirected to...</content>
<category term="AWS" />
<category term="Network" />
<category term="CloudFront" />
<category term="Web" />
<category term="EdgeCloud" />
</entry>
<entry>
<title>Hands-on with AWS Bring your own IP addresses (BYOIP) in Amazon EC2</title>
<id>https://www.edge-cloud.net/2022/07/19/hands-on-with-aws-byoip/</id>
<updated>2022-07-19T00:00:00-07:00</updated>
<published>2022-07-19T00:00:00-07:00</published>
<author>
<name>Christian Elsen</name><uri>https://www.edge-cloud.net/about/</uri>
</author>
<link href="https://www.edge-cloud.net/2022/07/19/hands-on-with-aws-byoip/" />
<summary type="html">Using AWS Bring your own IP addresses (BYOIP) in Amazon EC2 capability with a real life example of an IPv6 prefix, showing provisioning and troubleshooting steps.</summary>
<content type="html">This blog post will walk you through the Bring your own IP addresses (BYOIP) for Amazon EC2 feature, using a real-life example. With BYOIP you can bring part or all of your publicly routable IPv4 or IPv6 address ranges to your AWS account. While you continue to own the address range, AWS advertises it on the internet for you under the Amazon Autonomous System Numbers (ASNs). Within your AWS account, these BYOIP address ranges appear...</content>
<category term="AWS" />
<category term="Network" />
<category term="IPv6" />
<category term="EdgeCloud" />
</entry>
</channel>
</feed>