SWAO

English

Deutsch

English

Deutsch

Landing Zone catalogues ​

A Landing Zone catalogue describes one cloud provider as SWAO sees it: its regions, the sovereignty facts of each region (residency country, operator jurisdiction, extraterritorial exposure, certifications) and the platform services each region offers, with the capabilities they fulfil and the key custody models they support. Each catalogue is one JSON file, lz-catalogues/<provider>.json, with a meta block (name, last update, source, confidence, region count) and a regions list.

SWAO ships 10 catalogues: four hyperscaler catalogues (AWS, Microsoft Azure, Google Cloud, Oracle Cloud Infrastructure), three sovereign offerings of hyperscalers (AWS European Sovereign Cloud, AWS ISOE Europe, Azure Local) and three European providers (Delos Cloud, Open Telekom Cloud / T Cloud Public, STACKIT).

How SWAO uses a catalogue ​

  1. Targets. You name one or more targets of the form provider:region, for example stackit:eu01, with --lz-cat-targets on the command line or under assessment.landing_zone.targets in the app .swao.yml (the older comma-separated assessment.lz_cat_targets is still read). The terminal interface writes the same key when you pick a provider and regions.
  2. Geographies. Instead of a region ID, a target may name a geography such as azure:Europe or gcp:Germany. One geography model applies to every catalogue: a region belongs to a geography when its residency country is in that geography, and the default region prefers residency country DE, then the region with the most services, then the lowest region ID. Each catalogue page below shows the default region for Europe and Germany.
  3. Fit. The Landing Zone Catalog Assessment looks up the services the application needs (from its Application Assessment) in the target region and checks the region's sovereignty facts against the requirements of your active frameworks, for example BSI C5 or GDPR. It returns a verdict per service and an overall verdict per target (READY, READY_WITH_CHANGES, NEEDS_VERIFICATION, BLOCKED or SOVEREIGNTY_BLOCKED). The assessment is deterministic, makes no LLM calls and needs no cloud credentials.

A catalogue stores facts only. Whether a region is acceptable is always decided by the frameworks you activate, never by the catalogue itself.

Automated and curated refresh ​

The bundled catalogues are point-in-time seeds; each page shows the date and the confidence of its catalogue.

  • Automated. Six catalogues (aws, aws-esc, aws-iso-e, azure, gcp, stackit) are generated from public provider sources. swao lz catalogue update --provider all (Consultant and above, no credentials needed) refreshes their service lists into the workspace folder wsp/inputs/catalogs/lz-catalogues/ without a new SWAO release.
  • Curated. Four catalogues (azure-local, delos, oci, otc) are curated by hand from the providers' public documentation, because no machine-readable source exists. They are refreshed with SWAO releases.

To correct a fact, add a region or describe a private cloud, copy a catalogue into the workspace (swao lz catalogue copy <provider>) or start a new one (swao lz catalogue new <provider>). The workspace copy then takes precedence over the bundled catalogue. See Adapting LZ catalogues for the full workflow, and swao lz catalogue list --origin to see which copy is used.

Catalogue list ​

CatalogueProvider IDOperator jurisdictionRegionsRefreshConfidenceLast updated
Amazon Web ServicesawsUS entity34automatedhigh2026-09-04
AWS European Sovereign Cloudaws-escEU entity1automatedhigh2026-09-04
AWS ISOE Europe (classified)aws-iso-eUS entity1automatedlow2026-09-04
Microsoft AzureazureUS entity87automatedhigh2026-09-04
Azure Localazure-localOperator site2curatedmedium2026-08-11
Delos ClouddelosEU entity1curatedlow2026-08-11
Google Cloud PlatformgcpUS entity42automatedmedium2026-09-04
Oracle Cloud InfrastructureociUS entity, EU entity6curatedmedium2026-09-20
Open Telekom Cloud / T Cloud PublicotcEU entity2curatedmedium2026-08-11
STACKITstackitEU entity2automatedmedium2026-09-04

The catalogue files and the template _lz-catalogue-template.json are public: github.com/Accenture/SWAO/tree/main/lz-catalogues. Providers announced but not yet catalogued are listed in _coming-soon.json.

Important notes ​

  • Catalogue facts are point-in-time. Check the date and confidence of a catalogue and refresh or review it before an engagement.
  • Certifications and jurisdictions are recorded facts, not verified by SWAO. They are not legal advice; review the provider's contracts and data processing terms.