IaC got people to understand at the idea that your infra code should be treated like your app code. Checked in to source control, deployed via COCD etc. Not defined by clicking buttons and stored in opaque databases somewhere.
"IaS" gets at the idea that it's a continuously running process. It's not a provisioning script you run once, there's a live reconciliation loop running in prod alongside your application code.
Also a big truckers hitch fan, but that animation was hard for me to follow because it doesn't look anything like how it's used in real life. It doesn't really make sense to compare to a bowline, it's basically used like a ratchet strap.
The first part, up to step 6, is just a slip knot. That part could be replaced by a bowline. But the slip knot can be thrown in one-handed in the middle of the line without needing to pull the end through like a bowline. And when you're done you give it a yank and the slip knot pops out.
Step 7 is the real point of the whole thing. You're using the loop and the hook (in this example) to create a pulley system to crank your load down tight. Then the rest of the steps are a hitch to keep it in place.
This is more secure than the version than I typically see used (and would be annoying to untie). I normally don't poke the end through like in step 9, but make another slip knot so the whole thing can be unravelled by pulling on the end of the line like a quick release.