Design a multi-account MLOps architecture on AWS for a regulated enterprise

Separate accounts for data, development, staging and production under an Organization; models are promoted as approved registry packages across account boundaries via cross-account roles and resource policies, with all deployment driven by CI/CD rather than human console access to production.

Account boundaries are AWS's strongest isolation primitive. In regulated environments the requirement is not merely tidiness — it is that a data scientist cannot reach production, and that every production change is attributable and reproducible.

Account topology