aws-nitro-enclaves-sdk-c
aws-nitro-enclaves-cli
| aws-nitro-enclaves-sdk-c | aws-nitro-enclaves-cli | |
|---|---|---|
| 1 | 1 | |
| 92 | 115 | |
| - | 1.7% | |
| 5.9 | 8.5 | |
| 2 months ago | 3 days ago | |
| C | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aws-nitro-enclaves-sdk-c
-
Engineering with Enclaves
Enclaves are really useful, but I wish AWS would support an SDK in Go or another language. The current one is written in C: https://github.com/aws/aws-nitro-enclaves-sdk-c
There are some third party implementations available, but we'd worry too much about maintenance of those to use them. Something officially supported would really be helpful.
aws-nitro-enclaves-cli
-
BlindAI API: An open-source and privacy-first OpenAI alternative
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 model, how do you protect your models? (because I did, to access the base image)
If you build the model, 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/aws-nitro-enclaves-cli/blob/main/exam...
What are some alternatives?
nitriding - Tool kit for building networked services on top of AWS Nitro Enclaves.
ego - EGo is an open-source SDK that enables you to develop your own confidential apps in the Go programming language.
nitrogen - Nitrogen is a tool for deploying web services to AWS Nitro Enclaves.
pycape - The Cape Privacy Python SDK
CCF - Confidential Consortium Framework
veracruz - Main repository for the Veracruz privacy-preserving compute project, an adopted project of the Confidential Compute Consortium (CCC).
cape-js - The Cape Privacy JavaScript SDK