Multi-Cloud

Escher treats AWS and Azure as first-class citizens in the same estate. You can scope queries to a single cloud or reason across both in a single prompt.

Mixed-profile estate

Once you have AWS and Azure profiles enabled, Escher's EstateView merges them under a unified graph:

Estate Overview
  AWS
    Account: 123456789012 (prod-core)    380 resources
    Account: 234567890123 (stage-app)    260 resources
  Azure
    Subscription: Corp Sub (a1b2c3d4)   420 resources

  Total resources: 1,060
  Freshness: 12m ago

Cross-cloud queries

How much am I spending total across AWS and Azure this month?

Which accounts have unencrypted databases — AWS and Azure?

Show me all public-facing resources across both clouds

Compare my IAM hygiene between AWS and Azure

The platform resolves the relevant skills for each cloud provider and synthesises a unified response.

Scoping queries to one cloud

Prefix the prompt or use natural language scoping:

On AWS only: which EC2 instances are missing Name tags?

In my Azure Corp Sub: what NSGs allow unrestricted inbound?

The gateway's scope extraction phase (Phase 2A) parses cloud provider, account, region, and environment filters from the prompt.

Profile precedence

When multiple profiles cover the same account with different permissions, Escher surfaces the union of observed resources — but annotates which profile provided each observation.

Account 123456789012
  prod-admin (380 resources — full visibility)
  audit-readonly (310 resources — partial, missing KMS and CloudTrail)

  Resources only visible via prod-admin: 70

Next steps

Profiles — Manage ObserverContext profiles
Core Concepts — ObserverContext and EstateView

Multi-Cloud ​

Mixed-profile estate ​

Cross-cloud queries ​

Scoping queries to one cloud ​