I went to a talk at Re:invent that covered Nitro Enclaves and I didn’t get the sense they were like SGX at all except for the name. The way they were described

I went to a talk at Re:invent that covered Nitro Enclaves and I didn’t get the sense they were like SGX at all except for the name. The way they were described was as a secondary EC2 instance that inherited however much CPU and RAM from a primary instance that you wanted to assign it. He actually mentioned being able to run a full OS in the enclave. The secondary instance would be associated with a primary EC2 instance with strong constraints on connectivity, being only able to communicate with the primary EC2 instance via vsock and with KMS (maybe other AWS services as well). Another session mentioned the code was cryptographically signed and potentially couldn’t be changed.