Skip to content

Oracle Cloud Infrastructure (oci) ​

This page describes the Landing Zone catalogue oci as shipped with SWAO: the provider and its sovereignty model, the regions with their residency and certifications, how the catalogue is refreshed and how to use it as a target.

Provider and sovereignty model ​

Oracle Cloud Infrastructure (OCI) is the public cloud of Oracle Corporation, a US company. The catalogue covers two products, distinguished by region ID: standard OCI regions (eu-frankfurt-1, eu-amsterdam-1, me-dubai-1, me-jeddah-1), operated by a US entity, and the OCI EU Sovereign Cloud (eu-frankfurt-2, eu-madrid-2), operated by Oracle legal entities in the EU.

Sovereignty model: the standard regions record US CLOUD Act and FISA Section 702 exposure. The EU Sovereign Cloud regions record an EU-entity operator but still record US CLOUD Act exposure, as the parent company is a US company. A framework that forbids any US extraterritorial exposure therefore blocks both products; compare the regions side by side to see the difference in services.

Summary ​

PropertyValue
Provider ID (for targets)oci
Catalogue nameOracle Cloud Infrastructure (OCI) service catalogue
Regions6
Distinct services54
Operator jurisdictionUS entity (US-entity): eu-frankfurt-1, eu-amsterdam-1, me-dubai-1, me-jeddah-1; EU entity (EU-entity): eu-frankfurt-2, eu-madrid-2
Extraterritorial exposureeu-frankfurt-1, eu-amsterdam-1, me-dubai-1, me-jeddah-1: US CLOUD Act (us_cloud_act), FISA Section 702 (fisa_702); eu-frankfurt-2, eu-madrid-2: US CLOUD Act (us_cloud_act)
Certifications recordedBSI_C5 (2 regions), ISO_27001 (6 regions), SOC_2 (6 regions)
Refresh modeCurated by hand from the provider's public documentation; refreshed with SWAO releases, not by swao lz catalogue update
Confidencemedium
Last updated2026-09-20
Schema version0.1
Default region for Europeoci:eu-frankfurt-1
Default region for Germanyoci:eu-frankfurt-1
Catalogue file in the public repositorylz-catalogues/oci.json

Regions ​

All 6 regions of the catalogue:

Region IDNameResidency countryOperator jurisdictionExtraterritorial exposureCertificationsServicesGeographies
eu-frankfurt-1Germany Central (Frankfurt), standard OCI, 3 ADs, oc1 realmGermany (DE)US entity (US-entity)US CLOUD Act, FISA Section 702BSI_C5, ISO_27001, SOC_252germany, eu, europe
eu-amsterdam-1Netherlands Northwest (Amsterdam), standard OCI, 1 AD, oc1 realmNetherlands (NL)US entity (US-entity)US CLOUD Act, FISA Section 702ISO_27001, SOC_228eu, europe
eu-frankfurt-2EU Sovereign Central (Frankfurt), OCI EU Sovereign Cloud, 1 AD, oc19 realmGermany (DE)EU entity (EU-entity)US CLOUD ActBSI_C5, ISO_27001, SOC_237germany, eu, europe
eu-madrid-2EU Sovereign South (Madrid), OCI EU Sovereign Cloud, 1 AD, oc19 realm (DR pair for eu-frankfurt-2)Spain (ES)EU entity (EU-entity)US CLOUD ActISO_27001, SOC_227eu, europe
me-dubai-1UAE East (Dubai)United Arab Emirates (AE)US entity (US-entity)US CLOUD Act, FISA Section 702ISO_27001, SOC_24middle-east
me-jeddah-1Saudi Arabia West (Jeddah)Saudi Arabia (SA)US entity (US-entity)US CLOUD Act, FISA Section 702ISO_27001, SOC_24middle-east

Certifications ​

CertificationRegions holding it
BSI_C5eu-frankfurt-1, eu-frankfurt-2
ISO_27001eu-frankfurt-1, eu-amsterdam-1, eu-frankfurt-2, eu-madrid-2, me-dubai-1, me-jeddah-1
SOC_2eu-frankfurt-1, eu-amsterdam-1, eu-frankfurt-2, eu-madrid-2, me-dubai-1, me-jeddah-1

Certifications are compared without regard to case or separators; C5 and BSI_C5 count as the same BSI C5 attestation. They are facts recorded in the catalogue, not verified by SWAO.

Using this catalogue ​

Name a region of this catalogue as a target of the Landing Zone Catalog Assessment, on the command line or in the app .swao.yml:

bash
swao lz catalogue show oci
swao assess --type landing-zone-catalog --app <app-id> --lz-cat-targets "oci:eu-frankfurt-1"
yaml
assessment:
  landing_zone:
    targets:
      - oci:eu-frankfurt-1

A geography such as oci:Europe instead of a region ID resolves to the default region shown in the summary.

To correct or extend the facts for one engagement, copy the catalogue into the workspace with swao lz catalogue copy oci and edit wsp/inputs/catalogs/lz-catalogues/oci/index.json; the workspace copy then takes precedence. See Adapting LZ catalogues.

Catalogue facts are point-in-time and are not legal advice. Check the date and confidence above and review the provider's contracts before you rely on a verdict.