Bret and Matt are joined by Corey Quinn to talk about AWS and containers.-------------------------------------★ Enroll now for my next Live course, GitHub Actions + Argo CD, scheduled for July 10-21. Go to bret.courses/autodeploy to sign up. ★------------------------------------Corey Quinn is the Chief Cloud Economist at the Duckbill Group. You may have seen or heard some of his in-depth AWS content, including his Last Week in AWS newsletter and blog, Corey's podcast Screaming in the Cloud and the AWS Morning Brief, or his highly produced YouTube videos on the Last Week in AWS channel. Corey runs the Duckbill Group, a company of people focused on helping clients understand and manage their cloud spend. If I had to describe Corey in a sentence, he's a quick thinking AWS expert who is one part cloud strategist, and one part sarcasm. The inspiration for this show came from his blog series, focused on all the ways to run containers on AWS, which is to say there's a lot. Dozens of ways, in fact, which I took a
Since I keep seeing developers use ‘pretty’ IP addresses like ’1.2.3.4’ in example configurations; a reminder that you MUST NOT use publicly routable addresses that you do not control in your code.
Instead, use one of the available 'TEST-NET' IPv4 or IPv6 ranges documented in RFC 6890;
192.0.2.0/24
198.51.100.0/24
203.0.113.0/24
❌ 1.2.3.4
✅ 192.0.2.4
and for IPv6;
✅ 2001:db8::/32
Pass it on to all of your fellow developers, documentation writers, and so forth.
Full RFC for special purpose addresses;
https://datatracker.ietf.org/doc/rfc6890/
Reserved for documentation, IPv4 and IPv6;
https://datatracker.ietf.org/doc/rfc5737/
https://datatracker.ietf.org/doc/rfc3849/
1/ 🧵
This memo reiterates the assignment of an IPv4 address block (192.0.0.0/24) to IANA. It also instructs IANA to restructure its IPv4 and IPv6 Special-Purpose Address Registries. Upon restructuring, the aforementioned registries will record all special-purpose address blocks, maintaining a common set of information regarding each address block.