Edge Intelligence sandbox

Service directory. These links only work while your tunnel is running.

Start the tunnel first. Every public port on these hosts is closed — the services are reachable only through an SSM port-forward that pins their hostnames to your machine. Run the tunnel script from your onboarding email, choose an environment, then use the links below.

./eiiotsandbox-tunnel-<your-name>.sh

One environment at a time: they all use the same ports.

sandbox01

Service	URL	What it is
Omni	omnimain.eiiotsandbox01.com:8080	Cluster management and the dashboards it proxies
Keycloak	keycloak.eiiotsandbox01.com:9443	Single sign-on
Nexus	nexus.eiiotsandbox01.com:8443	Artifact repository

sandbox

Service	URL	What it is
Omni	omnimain.eiiotsandbox.com:8080	Cluster management and the dashboards it proxies
Keycloak	keycloak.eiiotsandbox.com:9443	Single sign-on
Nexus	nexus.eiiotsandbox.com:8443	Artifact repository

The apps team does not have tunnel access to sandbox — only sandbox01 and sandbox02.

Why the ports are in the URLs

The SSM document requires the local port to match the remote one, and these services listen on 8080/9443/8443 rather than 443. Keycloak's redirect URIs carry the port to match, so removing it would break sign-in.

If a link fails

Symptom	Cause
Connection refused	No tunnel running, or you tunnelled a different environment
Certificate warning	The hostname is not pinned — the tunnel script does this, and undoes it on exit
`AccessDenied` starting the tunnel	MFA device not enrolled, or you lack the grant for that environment

Edit this page in infra/edge-l1-landing/www/index.html in pd-edge-intelligence.