Architecture map

Your cloud, drawn for you. With what every piece costs and risks.

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.

Production accountshop

Internet and usersEntryComputeIntegrationDataUsersshop-cdnCloudFrontshop-apiAPI Gatewayorders-apiLambda ×12orders-workerLambdaorders-queueAmazon SQSweb-assetsAmazon S3orders-dbAuroraInternet and usersEntryComputeIntegrationDataUsersshop-cdnCloudFrontshop-apiAPI Gatewayorders-apiLambda ×12orders-workerLambdaorders-queueAmazon SQSweb-assetsAmazon S3orders-dbAurora

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

Try it here

One drawing, five readings

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.

Usersshop-cdnCloudFrontshop-apiAPI Gatewayorders-apiLambda ×12orders-workerLambdaorders-queueAmazon SQSweb-assetsAmazon S3orders-dbAuroraUsersshop-cdnCloudFrontshop-apiAPI Gatewayorders-apiLambda ×12orders-workerLambdaorders-queueAmazon SQSweb-assetsAmazon S3orders-dbAurora

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

Levels

From account to component, without getting lost

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

Resilience

If a region goes down, what has a fallback?

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.

eu-west-1primaryeu-central-1replicaRoute 53 failoverAurora Global DatabaseS3 CRRAWS Backupshopshop-apiordersorders-queueorders-dbinvoicesshop-apiordersorders-dbinvoicesAccount 4821…(not connected)Inside not drawneu-west-1primaryeu-central-1replicaAurora GlobalS3 CRRAWS Backupshopshop-apiordersorders-queueorders-dbinvoicesshop-apiordersorders-dbinvoicesAccount 4821…(not connected)Inside not drawn

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.

  • Replica, backup or failover configured outside its region
  • An identical one in another region, no copy configured
  • Only in one region, or data with no copy outside it

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

Notices on every 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.

Connections

Every line says where it comes from

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.

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.

Allowed by the network

A rule allows it: the database security group accepts 5432 from the function’s. A dashed, still line, with protocol and port.

Never observed traffic

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.

Multi-cloud and multi-account

AWS, Azure and Google Cloud in the same drawing

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.

AWS

By tags (app, application, service, project) and CloudFormation stacks; without a tag, it suggests by stack or by VPC.

Draws, among others

  • CloudFront
  • API Gateway
  • Elastic Load Balancing
  • Lambda
  • ECS
  • EKS
  • SQS
  • SNS
  • EventBridge
  • Step Functions
  • RDS
  • Aurora
  • DynamoDB
  • ElastiCache
  • S3

Reads with ViewOnlyAccess + SecurityAudit

Azure

By tags or resource group. Reads mostly through Resource Graph, asking only for the fields the map needs.

Draws, among others

  • Front Door
  • Application Gateway
  • API Management
  • App Service
  • Functions
  • AKS
  • Service Bus
  • SQL Database
  • Cosmos DB
  • Storage

Reads with Reader

Google Cloud

By labels or project. Asks each service for network and configuration fields only.

Draws, among others

  • Cloud Load Balancing
  • Cloud Run
  • Cloud Functions
  • GKE
  • Pub/Sub
  • Eventarc
  • Cloud SQL
  • Cloud Storage

Reads with Viewer

One application across accounts, in a single diagram

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.

Changes

What changed, without the drawing jumping around

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.

  • It updates after each cost analysis of the account and when you press “Refresh”.
  • With the risk and compliance add-on, on AWS it also updates on its own when CloudTrail records a component being created or deleted, and re-reads only the affected services and regions.
  • What was already there keeps its place and only new things get placed, unless more than 30% changes or you ask for a re-layout. If you have the screen open, it tells you a new version is available instead of redrawing by surprise.
  • New things carry a marker for 7 days, and if a region could not be read, its part stays as “unverified” instead of disappearing.
  • After a cost analysis
  • Refresh
  • From a CloudTrail change (add-on)

Since the last version: 2 new components, 1 removed and 1 moved to another application

  • orders-workernew
  • orders-queuenew
  • legacy-queueremoved
  • web-assetsmoved application

Illustration · sample application

Safe reading

Metadata only. No data, no secrets.

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.

  • AWS: ViewOnlyAccess and SecurityAudit. Azure: Reader. Google Cloud: Viewer.
  • Dropped before saving: environment variables of functions and containers, task secrets, CloudFront origin headers and stack parameters and outputs.
  • A test fails if a snapshot from any of the three providers contains one of these keys, and the collector refuses to save a version that carries them: envenvironmentsecretsappSettingscredentialsCustomHeadersParametersOutputs
Export and API

Take it wherever you need it

The 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.

PNG and SVG

The view on your screen, ready for a document, an architecture review or an audit.

  • PNG
  • SVG

JSON and API /v1

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}

MCP server

Three tools in the read-only MCP server so your AI assistant can query your applications and their graph.

  • list_architecture_apps
  • get_architecture_app
  • get_architecture_graph

Plans

The list, on every plan. The diagram, on Pro and Business.

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.

What each plan includes in the Architecture map
FeatureFreeProBusiness
Application list with components, monthly cost, cost findings and tag coverageIncludedIncludedIncluded
Grouping by tags, stacks, resource group or project, and by handIncludedIncludedIncluded
90-day change historyIncludedIncludedIncluded
Interactive diagram with C4 system landscape, context and container views, layers, levels and flow tracingNot includedIncludedIncluded
Application across accountsNot includedIncludedIncluded
Export to PNG, SVG and JSON, the C4 views to Structurizr and PlantUML, and a PDF report per applicationNot includedIncludedIncluded
API /v1 and MCP serverNot includedIncludedIncluded
Team notes on components and applicationsNot includedIncludedIncluded

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.

Frequently asked questions

See what you have built, what it costs and where the risk is

Get started

The application list is included in Free; the interactive diagram, in Pro and Business.