Livy TLSNotary Docs
Examples

Deployed Service Surface

Public endpoints and runtime layout for the deployed TDX-backed Notary.

Purpose

This page describes what the deployed infrastructure exposes to examples and clients. For Terraform apply, destroy, DNS, and bootstrap commands, use Terraform GCP Deployment.

Architecture

The deployment creates a Google Cloud network and a TDX-enabled VM. The native Notary server runs on port 7047, and the TEE proxy used for /api/v1/prove runs locally on port 7048. Nginx terminates HTTPS and routes public requests to the correct local service.

Google Cloud Platform
├─ VPC network
│  ├─ Subnet: 10.0.1.0/24
│  └─ Cloud NAT
└─ TDX instance
   ├─ Ubuntu 24.04 LTS
   ├─ TLS Notary server, local port 7047
   ├─ notary-tee proxy, local port 7048
   ├─ Intel Trust Authority CLI and config
   ├─ systemd service management
   └─ nginx HTTPS reverse proxy

Public Endpoint

The test deployment is intended to be reached at:

https://tlsn.livylabs.xyz

Health check:

curl https://tlsn.livylabs.xyz/healthcheck

Expected response:

Ok

Routes

EndpointUpstreamPurpose
/healthcheck127.0.0.1:7047Service health status.
/info127.0.0.1:7047Server metadata, public key, git hash, and TDX quote payload when enabled.
/127.0.0.1:7047Notary server info page.
/session127.0.0.1:7047Create a notarization session.
/notarize127.0.0.1:7047WebSocket notarization flow.
/api/v1/prove127.0.0.1:7048Proxy-backed prove flow.
/api/v1/jobs/<job_id>/attestation127.0.0.1:7048Download job attestation output.
/api/v1/jobs/<job_id>/secrets127.0.0.1:7048Download job secrets output.

Example Configuration

Use these values when an example should target the deployed Notary:

NOTARY_SCHEME=https
NOTARY_HOST=tlsn.livylabs.xyz
NOTARY_PORT=443
USE_FIXTURE_CA=false

For a full example command, see Running Examples Against The Deployed Notary.

Runtime Files

FileLocationPurpose
TLSN source checkout/home/livy/src/tlsn/Source used for the deployed build.
Notary binary/home/livy/src/tlsn/target/release/notary-serverCompiled Notary server.
Proxy binary/home/livy/src/tlsn/target/release/examples/proxyCompiled notary-tee proxy.
Notary config/home/livy/tls-notary-config/config.tomlRuntime Notary configuration.
Signing key/home/livy/tls-notary-config/notary-signing-key.pemPersistent Notary signing key.
Intel TA config/home/livy/config.jsonTrust Authority configuration.
Notary service/etc/systemd/system/tls-notary-server.servicesystemd unit for the Notary.
Proxy service/etc/systemd/system/tls-notary-proxy.servicesystemd unit for the proxy.
Nginx config/etc/nginx/sites-available/tlsnHTTPS reverse proxy configuration.
SSL certificates/etc/letsencrypt/live/${domain_name}/Let's Encrypt certificates.

Operational Checks

Check cloud-init status:

gcloud compute ssh test-notary-instance --zone=us-central1-a --project=livy-infra \
  --command="sudo cloud-init status --long"

Check service state:

gcloud compute ssh test-notary-instance --zone=us-central1-a --project=livy-infra \
  --command="systemctl is-active tls-notary-server tls-notary-proxy nginx"

Follow service logs:

gcloud compute ssh test-notary-instance --zone=us-central1-a --project=livy-infra \
  --command="sudo journalctl -u tls-notary-server -u tls-notary-proxy -f"

Check HTTPS certificate state:

gcloud compute ssh test-notary-instance --zone=us-central1-a --project=livy-infra \
  --command="sudo certbot certificates"

On this page