Uploaded February 2021 | Updated September 2026, 2 weeks ago
"Software supply chain" is a relatively new term but not a new idea. Most software is built using a lot of other components. These components should be checked to make sure they are what you think they are BEFORE being packaged up and sent out to users.
Not shockingly, that's usually not the case and new research shows yet again why this practice hurts your cybersecurity by letting hackers easily compromise your software.
Learn more in this short...
...and you can read the original report by Ax Sharma for Bleeping Computer at bleepingcomputer.com/news/security/researcher-hacks-over-35-tech-firms-in-novel-supply-chain-attack
Index:
- The question [0:00]
- A new technique [0:07]
- How software is built [0:12]
- What should happen [0:28]
- Security is fundamental [0:44]
#shorts
"Software supply chain" is a relatively new term but not a new idea. Most software is built using a lot of other components. These components should be checked to make sure they are what you think they are BEFORE being packaged up and sent out to users.
Not shockingly, that's usually not the case and new research shows yet again why this practice hurts your cybersecurity by letting hackers easily compromise your software.
Learn more in this short...
...and you can read the original report by Ax Sharma for Bleeping Computer at bleepingcomputer.com/news/security/researcher-hacks-over-35-tech-firms-in-novel-supply-chain-attack
Index:
- The question [0:00]
- A new technique [0:07]
- How software is built [0:12]
- What should happen [0:28]
- Security is fundamental [0:44]
#shorts









![Can We Improve How Netflix Handled Failover Using DNS In 2017? (Reaction)
In late 2017, Netflix did an AWS This is My Architecture video. It was one of the first. In the video they explained how they tackled the problem of failing over when disaster struck.
Specifically, they drilled down on a clever use of DNS records to create a very flexible system that allows services to continue in the event of some pretty significant disaster.
Few companies operate at Netflixs scale (even their scale back then) but this technique is broadly applicable for any team that needs to failover in the event of either disaster or even a simple failure.
Now, a few years later, I react to that video and see whats stood the test of time, what could be done simpler given todays technology, and generally critique the design against the AWS Well-Architected Framework in a mini AWS Well-Architected Review.
The original video: https://youtu.be/WDDkLOT8SCk
More on the AWS Well-Architected Framework is at https://aws.amazon.com/architecture/well-architected/
Follow me on Twitter at https://twitter.com/marknca
Read my AWS Hero bio at https://aws.amazon.com/developer/community/heroes/mark-nunnikhoven/
Learn more about the AWS Well-Architected Framework in my course on A Cloud Guru at https://markn.ca/courses/#mastering-the-well-architected-framework
Index:
- [00:00] Intro
- [00:24] Problem statement
- [02:10] Evacuating a region
- [03:10] Geo-routing
- [04:39] Intelligent failover
- [06:11] How a failover works
- [07:26] Record choice
- [08:13] Restoration
- [09:10] Tracking state
- [10:03] Can we improve? Can We Improve How Netflix Handled Failover Using DNS In 2017? (Reaction)](https://i.ytimg.com/vi/OJbOcYVy1wk/mqdefault.jpg)
