Configured
The configuration links A to B: an API Gateway integration, a listener and its target group, a CloudFront origin, an SNS subscription or an event source mapping. A solid line that moves in the direction of the call.
AAA Sentinel reads the metadata of your AWS, Azure and Google Cloud accounts and draws each application: what it is made of, how it connects, what each component costs and where the risk is. Nothing to install, using the read-only permissions the connection already has.
The application list is on every plan, Free included. The interactive diagram is on Pro and Business.
Cost. The more a component spends, the thicker its orange border. In the app, each one carries its monthly cost in your organization’s currency.
Illustration · sample application
3
clouds: AWS, Azure and Google Cloud
5
layers over the same drawing
4
levels, from account to component
90
days of change history
Where the money goes, what is exposed, what happens if a region goes down, what has no owner and what has changed. Pick a layer and tap a component to open its panel.
Cost: the more it spends, the thicker the orange border.
Tap a component, or reach it with the keyboard, to see its panel. Press a layer again to turn it off.
Illustration · sample application
What does not fit in one view is split into levels, with breadcrumbs, a link of its own for each level and transitions that zoom in as you enter and out as you go back.
Account level, Applications view: six application cards, among them shop, payments and No application, each with its cost bar.
Illustration · sample application
Replicas, failover and backups across regions and accounts appear with the configuration that proves them: DynamoDB global tables, Aurora Global Database, S3 replication, Route 53 failover, cross-account AWS Backup, Azure SQL failover groups or Cloud SQL replicas.
With the resilience layer: the API has Route 53 failover, and the database and the bucket have a replica in eu-central-1; the functions exist in both regions with no copy between them, and the queue only in eu-west-1.
It states what is configured, never that recovery has been tested or works. “Primary” and “replica” come from the configuration (source and target of the replica or failover); if nothing proves it, the region gets no role.
Illustration · sample application
In the account view, with the resilience layer, every application with notices carries a mark: data with no copy, replica or failover configured outside its region, and parts of a multi-region application that are only in one region.
On the application map, with the resilience layer, a button with the number of notices opens the list and each notice takes you to its component. The list view lists them too.
The same notices, with their count, are in the /v1 API, in the JSON you export from the account view and in the reliability pillar of the pillar review (tab and PDF).
Anything not assigned to an application only gets the no-copy notice. On Pro and Business, with the diagram.
The map separates what the configuration links from what the network merely allows, and the panel shows the read that proves each connection, with a link to the provider’s console.
The configuration links A to B: an API Gateway integration, a listener and its target group, a CloudFront origin, an SNS subscription or an event source mapping. A solid line that moves in the direction of the call.
A rule allows it: the database security group accepts 5432 from the function’s. A dashed, still line, with protocol and port.
It does not read Flow Logs, X-Ray or the content of anything. A dependency that lives only in code or in an environment variable does not appear: the map does not make it up.
Applications come from what you already use to organise your cloud. Anything left over appears as a suggestion you confirm, rename or merge, and you can group by hand.
By tags (app, application, service, project) and CloudFormation stacks; without a tag, it suggests by stack or by VPC.
Draws, among others
Reads with ViewOnlyAccess + SecurityAudit
By tags or resource group. Reads mostly through Resource Graph, asking only for the fields the map needs.
Draws, among others
Reads with Reader
By labels or project. Asks each service for network and configuration fields only.
Draws, among others
Reads with Viewer
The same tag in two accounts or two regions is the same application. Each account gets its own band, the resilience layer also answers what goes down if an account goes down, and an account you have not connected is drawn as such, without making up what is inside.
Each version comes from a fresh read (all of it, or only what was affected when CloudTrail triggers it) and is compared with the previous one: new, removed and changed components and connections, with 90 days of history.
Since the last version: 2 new components, 1 removed and 1 moved to another application
Illustration · sample application
The map uses the read-only permissions the connection already has. It asks for nothing new, reads the content of nothing and, before saving, drops in the collector anything that could carry a secret.
envenvironmentsecretsappSettingscredentialsCustomHeadersParametersOutputsThe diagram comes out as an image for documentation or an audit, the graph as JSON in the same format as the public API, the C4 views as Structurizr DSL or C4-PlantUML to keep working on them as code, and each application as a PDF report.
The view on your screen, ready for a document, an architecture review or an audit.
Applications, components with their cost and findings, and the graph with the proof of each connection.
GET /v1/architecture/accounts/{accountId}/apps
GET /v1/architecture/accounts/{accountId}/graph?app={appId}Three tools in the read-only MCP server so your AI assistant can query your applications and their graph.
Plans
With Free you already know which applications you have, what they are made of and what each component costs. With Pro and Business you see them connected, with every layer.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Application list with components, monthly cost, cost findings and tag coverage | Included | Included | Included |
| Grouping by tags, stacks, resource group or project, and by hand | Included | Included | Included |
| 90-day change history | Included | Included | Included |
| Interactive diagram with C4 system landscape, context and container views, layers, levels and flow tracing | Not included | Included | Included |
| Application across accounts | Not included | Included | Included |
| Export to PNG, SVG and JSON, the C4 views to Structurizr and PlantUML, and a PDF report per application | Not included | Included | Included |
| API /v1 and MCP server | Not included | Included | Included |
| Team notes on components and applications | Not included | Included | Included |
Security findings for each component and CloudTrail-driven updates come with the risk and compliance add-on, available on Pro and Business. Free connects one account.
The application list is included in Free; the interactive diagram, in Pro and Business.