All courses / Architecture as Code / Module 5 / Chapter 21
Learning objectives
After the lesson the participant can:
- Explain the four dimensions of digital transformation that must be addressed together.
- Identify the regulatory drivers that shape cloud-first strategies for organisations in the EU.
- Evaluate cloud provider offerings against data sovereignty requirements and write the result as a selection policy.
- Assess the limitation of keyword-based compliance checks and name the appropriate alternative.
Key concepts
- Transformation dimensions
- Four dimensions to be addressed holistically: technical transformation, organisational change, cultural evolution and competence development. Technical transformation must be combined with organisational and cultural change to achieve lasting results.
- Cloud-first strategy
- A strategy in which organisations primarily choose cloud-based solutions for new initiatives. In the EU it must comply with data sovereignty regulations, which creates demand for Architecture as Code that handles sensitive data in line with the GDPR and sector rules.
- EU-trusted provider policy
- A codified provider selection policy that differentiates providers that are inherently sovereign from those acceptable only when their EU-only controls are in force. EU-headquartered platforms form the default where obligations prohibit other arrangements.
- Self-service developer portal
- A portal through which developers provision infrastructure from templates that carry compliance defaults from the start. The chapter cites Backstage, created at Spotify, with a software catalogue and software templates.
- Keyword-based compliance check
- A pipeline step that searches infrastructure code for words such as encryption. The chapter warns that this is not a meaningful GDPR compliance check and points to policy-as-code tooling as the alternative.
Interactive exercises
Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.
Interactive exercise 1 · Match
Sovereign cloud offerings and a developer portal
Match each offering or platform to what the chapter reports about it.
Interactive exercise 2 · Scenario
A workload under a sovereignty clause
Read the situation and choose what the chapter's reasoning leads to. Each choice gives feedback.
Teaching plan
| 15 min | Teacher presents the transformation challenges and the four dimensions, with the regulatory instruments the chapter names. |
| 15 min | Map the provider ecosystem on a board: EU-native providers and the sovereign offerings of global providers, and what makes each qualify. |
| 10 min | Teacher walks through the compliant template with its parameterised EU region and state locking, the developer portal, and the warning on keyword checks. |
| 25 min | Exercise: write a provider selection policy for one class of workload. |
| 10 min | Close on the key lesson: Architecture as Code is the technical foundation, but success needs organisational and cultural change. |
Discussion
- The chapter distinguishes providers that are inherently sovereign from those that become acceptable only when EU-only controls are in force. How would you verify, continuously, that those controls remain in force?
- Why is a pipeline step that searches for the word encryption worse than no check at all in some respects?
- Which of the four transformation dimensions receives the least attention in your organisation's digital strategy, and what does that cost?
Written exercise
Exercise · 25 minutes
A provider selection policy for one class of workload
Choose one class of workload in your own organisation that processes personal data. Write a provider selection policy for it in plain structured language that a policy engine could later enforce. State the regulatory obligations that apply, as your organisation has documented them. Define which providers and regions are permitted by default, which are permitted only when named EU-only controls are in force, and which are excluded. Specify the checks a pipeline must run on every change: region within the approved list, encryption, audit logging and state storage. Replace any keyword-style check with a rule that inspects the actual configuration value. State who may grant an exception, for how long, and where it is recorded.
Deliverable: A one-page provider selection policy with default, conditional and excluded options, four enforceable pipeline rules and an exception procedure.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
What does the chapter say about searching infrastructure code for encryption keywords in a compliance pipeline?
Show the answer
C. It is not a meaningful GDPR compliance check
The pipeline example carries an explicit warning that searching for encryption keywords is not a meaningful GDPR compliance check, and the learning objectives point to policy-as-code tooling instead.How should policy catalogues treat cloud providers, according to the chapter?
Show the answer
A. Differentiate inherently sovereign providers from those acceptable only with EU-only controls
Policy catalogues should differentiate between providers that are inherently sovereign and those that become acceptable only when their EU-only controls are in force.Which four dimensions of digital transformation does the chapter say must be addressed holistically?
Show the answer
B. Technical, organisational, cultural and competence
The dimensions are technical transformation, organisational change, cultural evolution and competence development, to be balanced with one another.