Sign inSign up
delegaris logo

goodhallsolutions/delegaris

By goodhallsolutions

•Updated 3 days ago

Cloud infrastructure access, without cloud console access: start/stop EC2 and RDS across accounts.

Image
0

1.1K

goodhallsolutions/delegaris repository overview

⁠Delegaris

Cloud infrastructure access, without cloud console access.

A self-hosted web app that lets people who have no AWS access start and stop EC2 instances and RDS databases across any number of AWS accounts. People sign in with their Active Directory or Microsoft Entra ID account; administrators decide who can do what to which resources, and the more delicate actions can require approval. One container; SQLite by default, PostgreSQL for running several copies.

⁠What it does

  • Start, stop and reboot EC2 instances, RDS instances, Aurora, DocumentDB and Neptune clusters, Auto Scaling groups, ECS services and EKS node groups (scaled to zero and back to the size they had), Redshift clusters (pause and resume), SageMaker notebooks and Lightsail instances, in any number of accounts and regions, with a resource list that copes with large estates (fold by account, group by tag or region).
  • Keep on past the schedule: someone who needs a machine after hours sets a time; the service takes the schedule tag off so the scheduler leaves it alone, reminds them, and stops it and puts the tag back when the time comes. Works with AWS Instance Scheduler, Systems Manager Quick Setup and home-built schedulers, with one schedule tag or separate start and stop tags.
  • Book ahead: keep a machine on for a window booked in advance, once or every week, run as the person who booked it.
  • Request access: people ask; administrators grant from Approvals as an access rule with an end date.
  • Remote Desktop: administrators set up how Windows machines are reached; people with the right download a ready-made .rdp file, with no stored password.
  • My account: everyone manages their own two-step sign-in, sees the access they have and asks for more.
  • Server groups: a database and the servers that need it start in order and stop in reverse.
  • Access rules: grant an AD group or user actions on a slice of the estate, chosen by account, region, type, tag or name, with exceptions. Tag-protected machines (domain controllers, firewalls) only administrators can touch.
  • Approvals: a rule can say its actions need approval; approvers decide in the UI or with buttons in Slack, and the action runs the moment one agrees.
  • Cost estimates: what a machine costs an hour, what its schedule saves a week and what a keep-on costs, from AWS list prices.
  • Sign-in: Active Directory over LDAPS, Microsoft Entra ID (OpenID Connect), or both.
  • AWS identity: an instance role, access keys, or IAM Identity Center (SSO) from your start URL.
  • Notifications: Slack (to the person), Microsoft Teams and a generic signed webhook.
  • Reports and audit: who kept what on and for how long, who did what, every action recorded; the log can be copied to S3 for a SIEM.
  • API tokens: for scripts and pipelines, acting as the person who made them, for the everyday actions only.
  • Branding: your organisation's name, logo, icon and colours.
  • High availability: two or more copies sharing a PostgreSQL database take turns at the timed work.

⁠Quick start

# docker-compose.yml
services:
  delegaris:
    image: goodhallsolutions/delegaris:latest
    restart: unless-stopped
    env_file: .env
    ports:
      - "8080:8080"
    volumes:
      - delegaris-data:/data
    read_only: true
    tmpfs:
      - /tmp
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges:true
volumes:
  delegaris-data:

A minimal .env to try it:

PUBLIC_URL=http://localhost:8080
LOCAL_ADMIN_PASSWORD=choose-one
AWS_DEFAULT_REGIONS=eu-west-2

Then docker compose up -d, open http://localhost:8080⁠, sign in as admin, and on Accounts either sign in through IAM Identity Center, paste access keys, or rely on the instance's IAM role. Add an account (a role to assume, or the account's own keys), Test connection, then set up access rules under Settings > Access.

For production: run on EC2 with the instance profile from the iam/hub-role.yaml template (instance metadata hop limit 2), set PUBLIC_URL to the HTTPS address people use (behind nginx or a load balancer) with TRUST_PROXY_HEADERS=true, set up Active Directory or Entra ID sign-in under Settings > Sign-in (or with LDAP_* / OIDC_* in .env), name ADMIN_GROUPS, and switch the local administrator off once directory sign-in works. Every setting is documented in .env.example in the source repository.

⁠Tags

  • latest: the newest release.
  • 0.8.0, 0.7.0, 0.6.0, …: a specific release. Pin one to stay on it until you choose to upgrade.

0.2.2 sets Active Directory up like a domain join: the domain, a user and a password, with the controllers found through DNS. 0.2.1 added sign-in set-up from the admin UI (Active Directory and Entra ID under Settings > Sign-in, with tests of the directory and the identity provider) and documents running behind nginx.

The image is linux/amd64, built from python:3.12-slim, runs as an unprivileged user (UID 10001), keeps everything it stores in the /data volume (or in PostgreSQL via DATABASE_URL), and exposes GET /healthz.

⁠Health, backups, upgrades

/healthz returns the version and, with several copies, which one holds the timed-work lease. A copy of the SQLite database is written to /data/backups nightly (optionally uploaded to S3). To upgrade, pull the new tag and docker compose up -d; database changes are applied on start.

Delegaris is made by Goodhall Solutions.

Tag summary

Content type

Image

Digest

sha256:9f44c2a75…

Size

91.1 MB

Last updated

3 days ago

docker pull goodhallsolutions/delegaris