FAQs

Short answers. The self-hosting guide has the long ones.

The basics

What is Delegaris, in one sentence?

A self-hosted web app that lets people who have no AWS access start, stop and keep on EC2 instances, RDS databases and other AWS services across your accounts, within rules you set.

Who is it for?

Organisations where a hosting or platform team owns the AWS accounts and the schedules, and everyone else (developers, testers, support, the business) just needs a machine on at a particular time. It replaces the ticket, the shared console login and the tag edited by hand.

Does it replace my scheduler?

No. Your scheduler (AWS Instance Scheduler, Systems Manager Quick Setup, or something home-built) keeps running. Delegaris works around it: to keep a machine on it takes the schedule tag off for a while and puts it back afterwards. It can read the scheduler's definitions so it knows the hours each schedule means.

What does it need in my AWS accounts?

A narrow IAM role in each account that allows listing, starting, stopping and tagging the services you choose, and nothing else. The UI gives you a CloudFormation template and the exact parameters. The service itself needs only the right to assume those roles, and to read AWS list prices for cost estimates.

Sign-in and access

How do people sign in?

With the account they already have: on-premises Active Directory over LDAPS (nested groups followed), Microsoft Entra ID through OpenID Connect, or both at once while you move between them. Delegaris has its own two-step sign-in, with a code from an authenticator app after the password, which you can require for nobody, administrators or everyone; Entra ID sign-ins keep Microsoft's own MFA.

How do I decide who can do what?

Access rules: a group or a person, the actions (start, stop, reboot, keep on, manage named tags, connect with Remote Desktop), and the machines, chosen by account, region, type, tag or ID. People see only what a rule gives them. Administrators and read-only auditors are roles given to groups in the UI.

Can two people fight over the same machine?

A machine has one keep-on. Anyone with the right can extend it; only the people who set a time on it, or an administrator, can bring it forward or end it, so nobody's evening is cut short by a colleague who did not know they were still working. Simultaneous requests end as one keep-on.

What are approvals?

A rule can say its actions need approval first. Pressing Stop then sends a request instead of stopping anything; the approvers named on the rule (or the administrators) decide under Approvals, and the action runs at once as the person who asked. Nobody can approve their own request.

Running it

What does it run on?

One Docker container, or the native Linux package (a systemd service on Ubuntu, Debian, RHEL, Rocky, Alma or Amazon Linux, x86_64 or arm64) on servers without Docker. On an EC2 instance for preference, so it can use the instance's IAM role, or anywhere that can reach AWS. The Docker image is linux/amd64; on arm64 servers such as Graviton, use the Linux package. SQLite by default; PostgreSQL when you want two or more copies.

Is it highly available?

It can be: two or more copies sharing a PostgreSQL database take turns at the timed work through a lease, so if one server goes down at nine, the other still puts the tag back at ten. The self-hosting guide has the AWS recipe.

What happens if Delegaris is down when a keep-on ends?

Everything is in the database. When the service is back, overdue keep-ons are dealt with on the first pass. With two copies, the other one does it within a minute or two.

Where do notifications go?

Slack, to the person (reminders before a stop, decisions on their requests), found by their email address. Microsoft Teams and a generic signed webhook get everything as a stream. None are required.

Does it phone home?

No. There is no licence check, no telemetry and no update check. The only things it talks to are AWS, your directory, and the notification destinations you configure.

Still have a question?

Email contact@goodhallsolutions.co.uk. We read everything.