AWS Charts

The jupyter-k8s-aws GitHub repository publishes guided charts for AWS environments.

AWS-OIDC

A full web-access stack for EKS clusters. Users access the applications running in their workspaces from their browser via OIDC authentication.

What it deploys:

• Traefik with Let’s Encrypt issued TLS certificates

• Dex as the OIDC identity provider

• OAuth2-Proxy to manage workspace-wide cookies

• Auth middleware configured to verify the OIDC token from dex

• Preconfigured access strategies and templates for browser-based workspace access

Access pattern:

• OIDC web access — users authenticate through Dex, Auth middleware issues session cookies, and Traefik proxies traffic to workspace pods.

Type	URL
Package	oci://ghcr.io/jupyter-infra/charts/jupyter-k8s-aws-oidc
Source	charts/aws-oidc

AWS-HyperPod

Designed for SageMaker HyperPod clusters.

Users connect either a/ from their web browser using bearer token URL or b/ from desktop IDEs (Code Editor) using bearer token VS Code URL.

What it deploys:

• Jupyter K8s controller with the AWS Plugin sidecar

• Preconfigured access strategies for SSM-based remote access (VS Code, Cursor)

Optionally, components for Web UI with:

• Traefik

• An AWS ALB with ACM-issued TLS certificates

• Auth middleware configured to accept bearer token URLs

Access patterns:

• Desktop IDE remote access — the AWS Plugin registers workspace pods as SSM managed instances, and users connect through SSM sessions from their desktop IDE.

• Bearer token web access - users generate a bearer token URL with connection, Auth middleware issues session cookies, and Traefik proxies traffic to workspace pods.

Type	URL
Package	oci://ghcr.io/jupyter-infra/charts/jupyter-k8s-aws-hyperpod
Source	charts/aws-hyperpod

Dive deeper

For full configuration options, see the jupyter-k8s-aws GitHub repository.