Automatically Healing CloudFormation Drift with Durable Functions

May 17, 2026 · 2:34 AM UTC ·5 min read · 0 reactions · 0 comments · 45 views

#aws #cloudformation #serverless #infrastructure as code #devops #AWS #CloudFormation #Durable Functions #Lambda #SSM #H0ukiStar #GitHub

TL;DR · WeSearch summary

AWS introduced drift-aware change sets in November 2025, enabling automatic detection and repair of configuration drift in CloudFormation stacks. Durable Functions can be used to orchestrate the asynchronous workflow of drift detection and remediation. This approach simplifies state management and improves reliability compared to using standard Lambda functions.

Key facts

▪AWS updated CloudFormation in November 2025 to support drift-aware change sets for automatic drift remediation.
▪Drift-aware change sets can be created using the --deployment-mode REVERT_DRIFT option to revert infrastructure to its defined state.
▪Durable Functions simplify the orchestration of asynchronous operations like drift detection and change set execution.
▪The solution involves detecting drift, creating a drift-aware change set, and applying it to restore configuration compliance.
▪A sample implementation uses AWS Lambda, SSM parameters, and Durable Functions to automate the healing process.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/aws-builders/automatically-healing-cloudformation-drift-with-durable-functions-bhm
Publication time	Sun, 17 May 2026 02:34:59 +0000
Retrieval time	2026-05-17T02:40:19.130Z
Last seen	2026-05-17T02:40:19.130Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	y2nILxmZ1pe4
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3830337) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ほうき星 for AWS Community Builders Posted on May 17 • Originally published at qiita.com Automatically Healing CloudFormation Drift with Durable Functions #aws #lambda #cloudformation This article is a machine translation of the contents of the following URL, which I wrote in Japanese: Durable Functions を用いて CloudFormation のドリフトを自動修復する #AWS - Qiita はじめにこんにちは、ほうき星 @H0ukiStar です。皆さんは昨年(2025年)の11月に CloudFormation がアップデートされ、ドリフト状態の修正に利用可能なドリフト認識変更セットが追加されたことをご存じでしょうか？本機能の登場以前は、ドリフ...

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments