The Nitro Enclave Gotcha That Cost Me 90 Minutes: vsock and a Port That Lied

When you are building inside AWS Nitro Enclaves for the first time, the documentation gives you a clean mental model: parent EC2 instance communicates with the enclave over vsock, the enclave runs your application, everything is isolated and tidy. What the documentation does not tell you is that "connected" and "live" are two different things, and conflating them will cost you time. This is the story of a silent failure I hit while building Mizan, a legal AI platform running inside Nitro Enclave