The Keyring and the Gauntlet: Two Short Films on Who Gets In
The security wing of Learning Maps opens. The Keyring is how you stop handing out master keys. The Gauntlet is why one lock is never enough, and how to stack locks that fail for different reasons.
The night janitor carries one key, and it opens everything. The front door, the offices, the cash box, the vault. It is convenient right up until the moment that ring goes missing, and then a single lost key is the whole building. That is where the security wing of Learning Maps begins, because almost every real breach is some version of one key that opened far too much.
The systems-talking wing was about how the parts of a system cooperate without dragging each other down. This wing is a different question: how does the system stay safe when someone hostile is in the mix? These two rooms are the first answer, and they are about access. Who is allowed in, and how many independent doors stand between an attacker and the thing that matters. Same series, same rules: the story carries the lesson, the napkin map rewards watching, and every room splits the durable principle from the rented AWS label.
Episode 14. The Keyring
Watch The Keyring on YouTube (7:44).
The fix for the janitor is to flip the default. Instead of handing out a master key and taking doors away when something goes wrong, you start from zero, no access at all, and add back only the specific doors this exact job needs. That is least privilege, and its rule is deny by default, then grant the narrow exception on purpose. A leaked key should open a closet, not the whole library.
Two things make it real. First, for a workload, the strong move is not a long-lived key pasted into the code, it is a role the service assumes, which hands it temporary, scoped credentials that expire on their own. On AWS that is identity and access management, IAM, and its pieces are identities, policies, and roles. Second, and this is the part beginners almost never learn, access is not purely additive. A written deny always wins, no matter how many allows sit beside it, and a ceiling set above you, a service control policy or a permission boundary, can only ever narrow what you may do, never widen it. That is why a request can come back denied while an allow is sitting right there in plain view. Least privilege is where you start, and those two rules are why you cannot accidentally grant your way past the fence.
Episode 15. The Gauntlet
Watch The Gauntlet on YouTube (7:26).
One lock is a single point of failure. A second identical lock barely helps, because the same skill that beats the first beats the second. The trick is not more locks, it is locks that fail for different reasons. A lock, then a guard who checks who you are, then a sealed safe, then contents that are encrypted anyway: beating any one of them teaches the attacker nothing about the next. That is defense in depth, layered independent controls, so a breach has to defeat all of them and no single failure is fatal.
On AWS the layers are concrete, and they stack from the outside in. A web firewall at the edge, security groups at the instance, network ACLs at the subnet, IAM checked on every single call, and encryption sitting underneath all of it. The exam loves to punish the single-wall answer: asked to secure a multi-tier application, the weak reply names one control, and the strong one combines controls at different layers and puts the database in a private tier that the internet cannot reach at all. It is the same instinct the resilience wing taught with the bulkhead, pointed at an attacker instead of a failure.
What the pair adds up to
The Keyring shrinks how much any one key can open. The Gauntlet makes sure that even a key that works still has more walls to cross. One is about the size of a grant, the other about the number of independent barriers, and together they are the whole posture of least-access security: give the minimum, and back it with layers that do not share a weakness. A leaked credential should be a closet and a locked room and an encrypted file, not the building.
The wing continues from here: the Lobby and the Cipher, which ask what should even be reachable in the first place, and how to protect the data itself once everything else has failed. If you are just arriving, the map runs in order through the Data Wing, the coordination pair, and the systems-talking wing that ends at the Outpost. And if you want the frame the whole series sits on, there is AWS is math and Kubernetes is physics.