Compartments

A compartment is a logical grouping of resources within a tenancy, used to organize resources and to scope access policies. What it is for in an EPM context: separating environments by purpose or by owning group, and writing policies that apply to a set of resources rather than to each one individually. Keep it simple. Most EPM estates need very few. A compartment structure that mirrors a complicated org chart is a maintenance burden. Compartments scope resources. Identity domains scope identities. Different objects doing different jobs — said explicitly because learners conflate them. When more compartments earn their place: genuinely separate administrative ownership, or a policy requirement to isolate a set of resources. Two reasons. Not "it feels tidier" — the same answer as the identity domain lesson, and not the last time.

In this module: Module 3 · Cloud Account, Identity Domains and Regions

1. 1What we are building
2. 2The decisions you cannot undo
3. 3The identity object model
4. 4Identity domains — the central decision
5. 5Regions and data residency
6. 6Compartments
7. 7Running the estate design workshop
8. 8Four worked estate structures
9. 9Activating: creating a new cloud account
10. 10Activating: adding to an existing account
11. 11Touring the Oracle Cloud Console
12. 12Enabling multifactor authentication
13. 13Subscribing to and replicating regions
14. 14Creating a compartment
15. 15Creating an identity domain
16. 16Identity domain administrators
17. 17What breaks
18. 18Lab briefing: Northwind Group
19. 19Lab solution walkthrough