Four generations of deploying the same legacy app

Anatomy of a cascading incident: a PPA removal, an emergency AMI, and a four-year-old race condition

We reinvented container image layers — with AMIs

I audited my own four-year-old deploy script before replacing it

A 60-line deploy script: SSM Parameter Store as a release pointer

Rollback is a feature: drills, alarm gates, and an incident mode

Capacity-adaptive instance refresh: measured numbers from a real fleet

996.Leave - 新西兰

Work with me

About

梦还没开始就已经结束

两岁还是来了

男子四八

人生处处是修行

雅思经验分享

新西兰码农生活图鉴

恢复自由身

移民 NZ 的流水帐

Ten years, one legacy app, four deployment generations — from CodeDeploy to blue/green to fully-baked AMIs with instance refresh, and what each rebuild taught me.

A public postmortem: four upstream repo failures in one week, an emergency AMI, and a 16-second health-check race that routed traffic to half-deployed servers.

Porting container image layering to EC2 AMIs after the incident — weekly-baked layers, failure isolation, and a php-fpm health gate.

Five latent logic bombs found in my own blue/green deploy script, and why they slept for four years.

A deployment system is a pointer plus convergence: SSM Parameter Store as the release pointer, instance refresh as the loop, rollback without CI.

Rollback as a designed feature: deploy-gate alarms, auto vs manual boundaries, an incident mode that bypasses its own gates, and drills.

Real measured numbers for ASG instance refresh at different fleet sizes, and the capacity-adaptive strategy those numbers forced.

技术分享

新西兰码农的枯燥生活

移民

英语

首页

分类

归档

English

DevOps

password

icon

date

type

slug

status

title

summary

表格

The old world was not bad. It was full of state.

The prerequisite: an artifact that carries zero configuration

流浪在纽村

养娃

养生

绿卡

纽村生活

工作

育儿

魔幻

雅思