Egeria 5.3

Launch the Egeria 5.3 on Ubuntu 24.04 LTS by SecureAnyCloud image from the Azure Marketplace on a Standard_B2s (or larger) VM. Open inbound ports 22 (SSH), 80 (HTTP) and 443 (HTTPS) in the Network Security Group. The 20 GiB data disk that carries the server configuration is provisioned automatically from the image.

When the VM is running, connect over SSH as azureuser with the SSH key you selected at launch:

ssh azureuser@<public-ip>

The platform, the server activator and nginx start automatically on boot. Confirm that all three are active:

systemctl is-active egeria-platform.service egeria-activate.service nginx.service

The command should print active for each unit. For the full status view, run:

systemctl --no-pager status egeria-platform.service egeria-activate.service nginx.service

The image contains no default password. On first boot the appliance generates a unique HTTP Basic credential (user admin) and writes it, with the service URLs, to a root-only file. Read the file with sudo:

sudo cat /var/lib/sac/secrets/sac-credentials.txt

The file lists EGERIA_URL, EGERIA_SWAGGER_URL, the configured EGERIA_SERVER, the API user id, and the admin credential for the Swagger UI and REST API.

In your browser, open the Swagger UI at https://<public-ip>/swagger-ui/index.html. The appliance uses a per-VM self-signed certificate, so accept the browser's certificate prompt. Then sign in with user admin and the password from Step 3.

The Swagger UI renders the full REST API of the running platform, Egeria's Open Metadata and Governance (OMAG) Server Platform version 5.3.

Scroll the Swagger UI to browse the platform, administration, repository and access-service operations. Expand any group, then select Try it out to call an operation live against the running server.

From the VM, confirm that the platform is serving and the active-metadata-store server is active. The commands use -k because the loopback listener presents the appliance's self-signed certificate, and they read the per-VM credential straight from the credentials file.

First, check the health endpoint:

curl -ks https://127.0.0.1/healthz

This prints the platform origin string, which confirms that Egeria is up. Next, list the active servers through the authenticated front door:

PASS=$(sudo grep '^EGERIA_PASSWORD=' /var/lib/sac/secrets/sac-credentials.txt | cut -d= -f2-)
curl -ks -u "admin:${PASS}" \
  https://127.0.0.1/open-metadata/platform-services/users/garygeeke/server-platform/servers/active

The response lists active-metadata-store in its serverList. This confirms that the configured metadata server is running the Open Metadata Repository Services (OMRS).

The same response, viewed through the browser's authenticated session:

The running server loads Egeria's full Open Metadata type system into its in-memory repository. Retrieve the type count to confirm that live metadata is being served:

PASS=$(sudo grep '^EGERIA_PASSWORD=' /var/lib/sac/secrets/sac-credentials.txt | cut -d= -f2-)
curl -ks -u "admin:${PASS}" \
  https://127.0.0.1/servers/active-metadata-store/open-metadata/repository-services/users/garygeeke/types/all \
  | python3 -c 'import sys,json; print("open metadata typeDefs loaded:", len(json.load(sys.stdin).get("typeDefs", [])))'

You can explore and call every metadata, administration and repository operation from the Swagger UI.

The platform's working directory, its server configuration documents and its logs live on the dedicated 20 GiB Azure data disk mounted at /var/lib/egeria. Confirm the mount and list the configuration:

findmnt /var/lib/egeria ls /var/lib/egeria/data/servers/active-metadata-store/config/

The configuration document for active-metadata-store lets the platform re-activate the server automatically on every reboot. The in-memory repository content is deliberately non-persistent. It is rebuilt from the loaded type system each time the server starts.