Detecting Unmanaged Configuration Changes to Stacks and Resources (CloudFormation Drift Detection)

Amazon Web Services. Detecting Unmanaged Configuration Changes to Stacks and Resources (CloudFormation Drift Detection).

Type

Web resource

Intellectual base

Web

Link

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-stack-drift.html

Cited from

engineering_design

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Primes

• Configuration Drift
  • The compression also organises the intervention space into three mutually exclusive families. Eliminate the operational/state distinction by making the system immutable from the operational side — immutable infrastructure, read-only filesystems, locked-down runbooks — so change must go through the record. Continuously reconcile via scheduled diffs, drift detectors, and compliance scanners that flag and revert or escalate any divergence.

    This sourceAWS Documentation. Drift-detection and continuous-compliance tooling that compares running cloud resources against a declarative system of record and flags divergences for reconciliation or remediation.

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:00df02f14cf8 · see in the full table