provision-managed-instance

Orchestrate per-slug AWS provisioning with DNS delegation and checksum-based artifact verification.

3|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/equaltoai/lesser-host --skill provision-managed-instance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provision-managed-instance
Source: https://github.com/equaltoai/lesser-host/tree/main/.codex/skills/provision-managed-instance
Command: npx skills add https://github.com/equaltoai/lesser-host --skill provision-managed-instance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisioning and maintaining tenant-isolated managed instances across per-slug AWS accounts and DNS delegated zones is complex and error-prone; this skill coordinates the end-to-end provisioning lifecycle, including artifact verification and release-readiness, to reduce blast radius and ensure governance.

Core Features & Use Cases

  • Per-slug AWS account provisioning and DNS delegation setup for new tenants.
  • Checksum-based verification of release artifacts before deployment.
  • Managed-update flow with step-level recovery and rollback.
  • Release-verification discipline for consumer-facing portal and soul registry interactions.

Quick Start

Initiate a per-slug provisioning change to exercise the end-to-end flow, including per-slug AWS account provisioning, DNS delegation, and release-verification.

Frequently Asked Questions about provision-managed-instance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate per-slug AWS account provisioning with DNS delegation for tenant isolation?

Per-slug AWS account provisioning with DNS delegation is orchestrated end-to-end by coordinating account setup, DNS zone delegation, and CodeBuild to ensure strict tenant isolation. It reduces blast radius by applying governance guardrails across each tenant slug.

What is checksum-based artifact verification for release deployments?

Checksum-based artifact verification validates release artifacts before deployment to ensure release-readiness. It enforces integrity checks across the managed-update flow and consumer-facing portal interactions to prevent unauthorized or corrupted deployments.

Can I use step-level recovery and rollback during a managed-update flow?

Step-level recovery and rollback are supported during the managed-update flow across tenant slugs. The provisioning pipeline applies recovery mechanisms at each step to handle failures without compromising the entire tenant isolation boundary.

What's the best way to enforce release-verification for consumer-facing portal and soul registry interactions?

Release-verification discipline for consumer-facing portal and soul registry interactions is enforced through checksum-based artifact verification and CodeBuild coordination. This ensures release-readiness and maintains governance across the per-slug tenant environment.

Does per-slug provisioning work with existing AWS accounts or does it require new account setup?

Per-slug provisioning applies to changes touching the provisioning pipeline across per-slug AWS accounts. It orchestrates account setup and DNS delegated zones, enforcing tenant isolation and checksum-based artifact verification for each tenant slug.