Skip to content

The Full loop (AWS)

Build, run, watch, govern: the Calliope AI Workbench, Astrolift and Zentinelle on one perimeter. The Workbench hub and user servers and Zentinelle's backend, worker, console and own Temporal all run as pods on Astrolift's tenant cluster, on Astrolift's network, Aurora cluster and load balancer.

It is the Workbench on Astrolift and Zentinelle in Astrolift blueprints together, and it inherits the Workbench's constraint: on AWS Astrolift joins a VPC, ECS cluster, Aurora cluster and load balancer that already exist in the account.

Not yet validated end to end

Written from the installer source as of release 0.1.57. No step on this page has been run end to end on a clean AWS account yet. Read the known blockers first. Both cluster placements have been certified on local kind clusters only.

What you need

Everything Workbench on Astrolift needs: the deployment, DNS and Workbench values, and the existing VPC, private subnets, ECS cluster, Aurora cluster (identifier, writer endpoint, master secret ARN), load balancer, HTTPS listener and certificate. Zentinelle adds no required field. Capacity must be on-demand, or Spot with the on-demand anchor.

Choose it

  1. Choose what to install: The Full loop.
  2. Pick the cloud: AWS and a region.
  3. Pick a footprint.
  4. Review the drawing: the card sets Share everything, "Where the Workbench runs" and "Where Zentinelle runs" to On the Astrolift tenant cluster. "Network and database" resolves to reuse. Keep "Tenant runtime" on Create a cluster.
  5. Fill in the values, review Before we start, and finish setup.

The card resolves to four units: Calliope AI Workbench on the Astrolift cluster, Astrolift, Zentinelle and Zentinelle on the Astrolift cluster.

Apply

First, as for Workbench on Astrolift, make sure the adopted Aurora cluster admits TCP 5432 from inside the VPC; Astrolift adds no rules to it. Then on Install:

  1. Dry run Plan Astrolift, read the plan, Deploy it.
  2. Dry run Plan Zentinelle, read the plan, Deploy it. Its ECS services are created at zero and parked after the apply.
  3. Dry run Plan Zentinelle on the Astrolift cluster, read the plan, Deploy it. The dry run is refused until step 2 has marked the record. This unit opens its own NodePorts to the load balancer's security groups.
  4. Add the rule the Workbench unit does not add for an adopted load balancer: the tenant nodes' security group admits the load balancer's security group on TCP 30808.
  5. Dry run Plan Calliope AI Workbench on the Astrolift cluster, read the plan, Deploy it.

Verify

Run the checks from both blueprints:

The hub, Zentinelle's backend, console and Temporal, and Astrolift's platform pods share the on-demand anchor node. The installer does not check that they fit before the apply; on Lean the anchor is a t3.large.

To connect Astrolift organizations to this Zentinelle, use Install, Integrations, Zentinelle with Astrolift, Connect, as in Zentinelle in Astrolift.

First app and first agent run

On Astrolift, as in Astrolift standalone.

Undo

Teardown enforces the order: Calliope AI Workbench on the Astrolift cluster, Zentinelle on the Astrolift cluster, Zentinelle, then Astrolift. The infrastructure you supplied and the hosted zone are kept; remove the security group rules you added yourself. Then remove the state store and the Deployment Manager as in Undo.