aws-nitro-enclaves-cli

Ok, I'll bite. I'm happy to be wrong if I am wrong... This document [1] defines a Nitro Enclave as an application image that runs in a secure runtime with no external networking. This document [2] shows how you build a secure image. You basically take an image (like [3]) and run `nitro-cli build-enclave ...`. Ok... so explain to me: - Given that the image you build has to contain 1) private data (mine) and 2) private models (yours). If I build the container image, how do you protect your models? (because I did, to access the base image) If you build the container image, how do I know you didn't access my data? (because you did, to build the image) What am I not getting? [1] - https://docs.aws.amazon.com/enclaves/latest/user/nitro-encla... [2] - https://docs.aws.amazon.com/enclaves/latest/user/getting-sta... [3] - https://github.com/aws/aw

Disclosure: I work at AWS, and I played a part in the design of this feature. But not sadly not any coding for this one. Since this is HN, I thought additional links to the open-source licensed software that we released today might be helpful. A lot of it is written in Rust. Nitro Enclaves CLI - https://github.com/aws/aws-nitro-enclaves-cli Application that uses ACM managed certificates to do TLS termination inside a Nitro Enclave - https://github.com/aws/aws-nitro-enclaves-acm A library for interacting with the TPM-like device called the Nitro Security Module (used to measure code for attestation purposes) - https://github.com/aws/aws-nitro-enclaves-nsm-api Some sample C code for use with Nitro Enclaves - https://github.com/aws/aws-nitro-enclaves-sdk-c And a sample application showing how to use vsock to communicate - https://github.com/