Scans
Start on demand, inside the API process, over every account and region pair, eight at a time.
One loop covers a new VPC and an adopted account alike. What differs is where the resources start.
Declare a stack as a flat list of resources, or import resources that already exist.
Foundry resolves dependencies and diffs the declaration against live state, then lists every operation in order.
The plan passes the governance validator and the blast radius and CIDR gates, then boto3 executes it. The deployment is recorded.
Scans refresh the inventory, and compliance, advisor, cost, and IP space recompute from it.
Start on demand, inside the API process, over every account and region pair, eight at a time.
Separate scheduled functions drive remediation sweeps, forecasts, monitor reconciliation, and index refreshes by calling Foundry's internal routes.
A remediation outside the safe list waits on a Docket approval card.
The same operations are MCP tools, behind the same roles and gates.
Write to Renkara Media Group and a person will answer.