У нас вы можете посмотреть бесплатно #cloudnativewisdom014 или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
𝗖𝗹𝗼𝘂𝗱𝗡𝗮𝘁𝗶𝘃𝗲 𝗪𝗶𝘀𝗱𝗼𝗺 — 𝗔𝗪𝗦 𝗨𝗦-𝗘𝗔𝗦𝗧-𝟭 𝗢𝘂𝘁𝗮𝗴𝗲 𝗘𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 With Richard Simon (CloudTherapist) & Saim — short forensic recap and lessons for architects, platform engineers and SREs. In this episode, we rewind to October 20, 2025 and unpack the major AWS us-east-1 outage: what failed, why DynamoDB (and DNS) were central to the cascade, how AWS responded, and the practical resilience trade-offs every engineering leader should consider. We dig past the headlines and give actionable guidance for teams hit by cloud outages. 𝗖𝗵𝗮𝗽𝘁𝗲𝗿𝘀 / 𝗧𝗶𝗺𝗲𝗰𝗼𝗱𝗲𝘀 0:00 Intro 0:31 Why DynamoDB mattered: service dependencies & ripple effects. 1:02 DNS resolution failure & retry feedback loop 2:02 Richard Simon: explaining the “enactors” and the race condition. 3:58 How a second enactor overwrote partial DNS state — the cascade begins. 5:28 AWS response, mitigations and what they proposed to fix automation. 7:44 Community reactions 10:19 Multi-region HA vs cost and practical options. 13:34 Expectations for AWS re: Invent; what to watch for. 14:45 Closing 𝗟𝗶𝗻𝗸𝘀 & 𝘀𝗼𝘂𝗿𝗰𝗲𝘀 Official AWS Health/Incident page (US-EAST-1 Oct 20, 2025): https://aws.amazon.com/message/101925/ Reuters summary & timeline: https://www.reuters.com/business/reta... The Verge analysis / AWS post-mortem coverage: https://www.theverge.com/news/805904/... ThousandEyes / technical writeups & postmortems: https://www.thousandeyes.com/blog/aws... If this episode helped you think differently about resilience, please like, subscribe, and leave a comment with your outage story — Richard and I may reach out and feature it on a future show. Want to collaborate/share an incident? Drop a link in the comments or DM us.