Unit 2.1: Resource Model: Contracts, VDCs, and Boundaries
Introduction
Unit 1.1 made the VDC the organising boundary of the platform. This unit places the VDC inside a larger boundary, the contract, and asks the first governance question of any enterprise design: how many of each do you need? Too few contracts and one administrator can reach everything, including the regulated core. Too many and you lose private connectivity, shared group access and pooled commitments.
The answer depends on knowing exactly what each boundary holds. The unit closes by creating FinCorp's first production VDC in the DCD.
1. Two Boundaries, Two Jobs
1.1 The Contract: Where Money, Identity and Audit Converge
Every account type lives inside a contract. The Contract Owner account is created automatically for the user who registered, and only one Contract Owner can exist per contract. It can fully access all resources, create and delete User accounts, and assign the Administrator role. An Administrator has the same privileges except changing the contract payment method, and the role can be revoked. Contract Owners and Administrators can create an unlimited number of User accounts.
Identity, money and audit all close at this boundary:
- Identity: Contract Owner and Administrator accounts have access to all contracted resources. Group sharing works between the groups of your contract.
- Money: the cost alert is based on the net amount of the contract invoice, and Cost Alert and Cost & Usage are available to Contract Owners and Administrators. A Cloud Savings Plan is created under a contract and applies starting with the oldest VM in the contract.
- Audit: the activity log is grouped by contract and retrieved per contract number (Unit 2.3).
- Capacity: Resource Overview shows your usage limits, and you contact IONOS CLOUD Support to extend them. DBaaS engines allocate their resources per contract as well.
The consequence for design is blunt. Anyone with the Administrator role in a contract can reach every resource in it. If a team must not reach a workload under any circumstances, that workload belongs in another contract.
1.2 The VDC: Region, Network and Change Authority
The VDC fixes location. You specify the location of a data center only when you provision it for the first time, and you cannot change it afterwards. The VDC also holds the LANs, so it is the unit of network segmentation, and resources inside it can be distributed across availability zones.
Two further properties make the VDC the unit of change authority and of cost allocation. First, permissions on infrastructure are granted per VDC, and IONOS CLOUD does not offer granular access management to individual devices within an infrastructure setup. A write permission allows all operations on the resource and the elements inside it, such as the servers in a shared VDC, and it cannot exclude delete operations. If two teams must not be able to change each other's servers, they need separate VDCs. Second, Cost & Usage aggregates VDC costs by VDC, and on the invoice, consumption billed at pay-as-you-go (PAYG) rates appears under its VDC. A VDC that maps to one owner and one environment produces a cost report that needs no further allocation (Unit 2.4).
1.3 Boundary Stickiness
The following table lists what is bound to a region or a contract and what that means for design.
| Artifact or capability | Bound to | Design consequence |
|---|---|---|
| VDC location | The VDC, at first provisioning | Choose the location before creation; moving means rebuilding |
| Reserved IPv4 addresses | Region | Reserve them in the region that will use them. They are returned only as a block and only when not in use, and a returned static IP address cannot be reserved again |
| Snapshots and uploaded private images | Region | Plan image pipelines per region |
| Cross Connect | Same contract and same region | Splitting a contract, or placing VDCs in two regions, removes this private VDC-to-VDC path |
| Group sharing of resources | Contract | Sharing works between the groups of your contract; plan group design per contract |
| Activity log | Contract | Audit aggregation across contracts is your design (Unit 2.3) |
| Cloud Savings Plans | Contract | A plan applies to eligible usage in its contract, starting with the oldest VM there; in reseller contracts, plans cannot be transferred between subcontracts |
| Inter-region traffic | Geographic region | Data transfers between data centers in the same geographical region are free; traffic between different geographical regions is charged |
Two exceptions are worth knowing. IONOS Cloud Object Storage can grant access across contracts: a contract-owned bucket can grant another contract through an ACL, or specific users of another contract through a bucket policy. And a billing contract owner can transfer the ownership of a VDC, with all related rights and responsibilities, to another customer with a billing contract through the 24/7 Enterprise Level Support. Neither is a routine integration path, but both matter when you plan a reorganisation.
2. Contract or VDC: The Split Decision
The following table maps common drivers to the boundary that answers them.
| Driver | Split the contract when... | Split the VDC when... |
|---|---|---|
| Compliance scope | Auditors need evidence for the regulated estate only, with its own administrators and activity log | Scope is shared, but the regulated tier needs its own LANs |
| Billing and ownership | A legal entity or business unit must receive its own invoice | One payer, but cost must be shown per environment or team |
| Administrative blast radius | A team needs Administrator rights but must never reach the other estate | Teams can share administrators, but need separate change authority |
| Network and region | Never on its own; you would lose Cross Connect | Different region, environment or tier isolation |
| Commitments | Each estate has a stable floor large enough to commit on its own | Commitment should pool across environments |
As shown above, the contract answers "who is responsible and who pays", and the VDC answers "where does it run and who may change it". Split contracts for compliance, billing and administrative isolation. Split VDCs for region, network and environment.
FinCorp applies this rule. It runs two contracts: a production contract for the regulated estate, with a short list of administrators and its own activity log, and a non-production contract for development, testing and early AI experiments, where engineers may hold the Administrator role. Inside the production contract, VDCs follow one naming convention, <org>-<environment>-<location>-<purpose>, for example fc-prod-fra-core for the Frankfurt core and fc-prod-txl-dr for the Berlin recovery site. Because Frankfurt and Berlin are different regions, these two VDCs cannot use Cross Connect; Module 3 designs their link.
Naming deserves the discipline even though a VDC name can be changed later. The name does not need to be unique, so the convention, not the platform, is what keeps fc-prod-fra-core distinguishable in cost reports, access reviews and runbooks. Record the owner, environment and compliance scope in the VDC description.
DCD Implementation Walkthrough
You will create FinCorp's first production VDC, fc-prod-fra-core, in the production contract. This build fixes the location and the naming convention; the network and compute builds follow in Modules 3 and 4.
Prerequisites: an Administrator account in the production contract, or membership in a group with the Create Data Center privilege. By default, contract owners and administrators can create a data center.
Build goal: Create the scenario's first VDC, fixing region and naming.
Steps (in the Data Center Designer):
- Sign in with an Administrator account. When a user with the Create Data Center privilege creates a VDC, that user becomes its owner and keeps access to it even after the privilege is revoked, so create production VDCs from an administrator account and grant teams access through groups.
- Go to Menu > Virtual Data Centers and set Create mode to Canvas. The label changes to Create in Canvas. Canvas suits multi-tier, complex topologies, and its provisioning runs asynchronously in the background. DCXpress requires an active browser session during provisioning, and an Xpress setup cannot be modified in Xpress mode afterwards. Your mode selection becomes the default for future data center creation.
- Select Create in Canvas.
- In Name, enter
fc-prod-fra-core. - In Location, choose the Frankfurt location (
de/fra). If the VDC must host Confidential VMs or Cloud GPU VMs, the location must be Germany / Frankfurt am Main (de/fra/2). Check this choice twice: it cannot be changed after the data center is provisioned. - In Description, record the owner, environment, cost centre and compliance scope.
- Select Create default network security group so that a set of predefined security rules applies to all VMs created in this data center. You can customise its rules and members later (Unit 3.2).
- Select Create. An empty data center is created immediately and appears in My Virtual Data Centers, ready to open in the Workspace. Resources you add later take effect only when you provision them.
- Confirm the location: go to Dashboard > My Data Centers and check the Region column.
- Grant your platform team's group access to the new VDC in Menu > Management > Users & Groups (Unit 2.2 builds the groups).
Common mistakes:
- Creating production VDCs from a team member's account. The creator owns the VDC and keeps access after their privilege is removed.
- Accepting a default location. In DCXpress, the default data center from DCD Default Settings is selected automatically; in the CLI, the location falls back to
de/txlwhen you omit it. The location cannot be corrected later. - Splitting a contract to separate networks. That removes Cross Connect and group sharing; separate VDCs do the job.
- Expecting Cross Connect to join a Frankfurt VDC to a Berlin VDC. It requires the same contract and the same region.
- Reserving public IPv4 addresses "somewhere" in advance. They are region-bound, and a returned address cannot be reserved again.
The same build through the CLI makes the immutable field explicit. In ionosctl, --location cannot be changed after creation, while --name and --description can be updated later:
ionosctl compute datacenter create --name "fc-prod-fra-core" \
--description "FinCorp production core, regulated" --location de/fra --wait
Summary
The contract is where identity, billing, commitments and audit close; the VDC is where location, network and change authority close. Split contracts for compliance, billing and administrative isolation, and split VDCs for region, environment and tier. Region-bound artifacts and same-contract, same-region connectivity make both choices sticky, so FinCorp fixes them before the first workload lands.
Key Points:
- One Contract Owner per contract; Administrators reach every resource in the contract, so isolation from administrators requires a separate contract.
- Permissions on infrastructure are per VDC: a write permission covers every element inside it, including delete.
- The VDC location cannot change after first provisioning; reserved IPv4 addresses, snapshots and uploaded images stay in their region.
- Cross Connect, group sharing, the activity log and Savings Plans all end at the contract boundary.
- Create production VDCs from an administrator account, with an explicit location and a naming convention.
Important Terminology:
- Contract: the commercial unit that holds accounts, groups, resources, invoices, commitments and the activity log.
- Boundary stickiness: the property that a resource or capability cannot cross a region or contract boundary without being rebuilt or reprocured.