From 1c660a36421592c15d1e82a4c6e8a7b4b77a682d Mon Sep 17 00:00:00 2001 From: Dan Stefaniuk Date: Tue, 1 Apr 2025 20:32:48 +0100 Subject: [PATCH] Add anchor to the 'build in governance' section --- practices/cloud-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/practices/cloud-services.md b/practices/cloud-services.md index bf2cbb02..fa74998f 100644 --- a/practices/cloud-services.md +++ b/practices/cloud-services.md @@ -43,7 +43,7 @@ - Services/components need prompt updates to dependencies where security vulnerabilities are found — even if they are not under active development. - Services which use deprecated or unsupported technologies should be migrated onto alternatives as a priority. - Understand and be able to justify vendor lock in (see [outsource from the bottom up](../patterns/outsource-bottom-up.md)). -- Build in [governance as a side effect](../patterns/governance-side-effect.md), e.g. +- Build in [governance as a side effect](../patterns/governance-side-effect.md), e.g. - Segregate production and non-production workloads Production and non-production workloads should be deployed into separate cloud subscriptions (Azure) or accounts (AWS) to enforce clear security boundaries, reduce risk of accidental impact and simplify policy enforcement. This separation enables: