Run an event end to end Preview

This operator walkthrough presents Lite as the current event procedure. SaaS tenant creation and multi-cloud are separated as architecture reference.

Run an event with Lite

Sign in to Lite's Application Admin Console.
Create an event, a test team, and the problem selection.
Connect a test competitor AWS account with the procedure below.
Start a problem and open its endpoint.
Solve it, submit a real TC{...} flag, and confirm the score.
Reset it and confirm a second start.
Stop it and confirm the problem stack is gone from the competitor account.
Give participants the Participant Portal URL, team key, and start time.

Create a SaaS tenant (architecture reference)

The repository contains code for a System Admin to create a tenant from admin-console. There is no recent recorded fresh-AWS run from tenant creation through scoring and teardown. Re-verify it in a dedicated environment rather than treating this section as a production procedure.

Connect a competitor account

Each team deploys infrastructure/templates/competitor-bootstrap.yaml once in its AWS account. Use the same ExternalId configured by the organizer: 16–128 ASCII letters, digits, and _ = , . @ : / -. Share the resulting role ARN, never an administrator credential or secret key. The full competitor-side steps live in the competitor setup guide.

Deploy a problem

In the application-admin-console, create an event, pick problems from the catalog (the picker only offers cloud-deployable problems — local-only container problems are excluded, and non-AWS problems appear once multi-cloud is enabled), assign each team's account and region, and deploy. Each deploy assumes the team's role with the ExternalId and runs CloudFormation in their account. Watch status by polling the deployment until it reaches a terminal state, then tear it down from the same console when the event ends.

Enable multi-cloud (architecture reference)

Sakura, Azure, and GCP are not uniformly executable. Check the runtime capability matrix first, then use only a runtime explicitly marked executable in a dedicated test event.