This repository is an implementation of an attested OHTTP server for Azure AI Confidential Inferencing. Together with attested OHTTP client and a transparent key management service, it enables secure communication between clients and Confidential GPU VMs serving Azure AI models using chunked OHTTP. Learn more here.
The repo supports build and development using GitHub Codespaces and devcontainers. The repository includes a devcontainer configuration that installs all dependencies.
.
Build the attested OHTTP server container.
make build-server-container
For local testing, this repository includes a sample whisper container.
make build-whisper-container
Next, clone and build the attested OHTTP client container.
git submodule update --recursive
make build-client-container
Finally, run the containers locally. This command will launch the OHTTP server in a mode where the server generates its own HPKE key pair, and publish an OHTTP key configuration at a local endpoint http://127.0.0.1:9443/discover. This will also launch the whisper container, which listens at the endpoint http://127.0.0.1:3000/whisper.
make run-server-whisper
In a separate terminal, launch the client providing as input an audio file (included in this repo) and a OHTTP key configuration obtained from the discovery endpoint.
./scripts/service_wait.sh 127.0.0.1:3000
./scripts/service_wait.sh 127.0.0.1:9443
make run-client-container
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.