Amazon is linking site hiccups to AI efforts

"The online retail giant said there had been a 'trend of incidents' in recent months, characterized by a 'high blast radius' and 'gen-AI assisted changes.' Under 'contributing factors,' the note included 'novel genAI usage for which best practices and safeguards are not yet fully established.'"

"If every AI-assisted change now needs a senior engineer staring at diffs, the enterprise gives back much of the speed benefit it was chasing in the first place. The real fix is to move review upstream and make it machine-enforced: policy checks before deployment, stricter blast-radius controls for high-risk services, mandatory canarying, automatic rollback, and stronger provenance."

"Junior and mid-level engineers will now require more senior engineers to sign off any AI-assisted changes."

Amazon convened an engineering meeting to address recent operational outages linked to AI tool usage. The company identified a trend of incidents with high blast radius caused by AI-assisted changes, noting that best practices and safeguards for generative AI are not yet fully established. In response, senior vice-president Dave Treadwell announced that junior and mid-level engineers must obtain senior engineer approval for any AI-assisted changes. However, analysts caution this approach may reduce the efficiency gains AI was meant to provide. Alternative solutions include implementing machine-enforced policy checks before deployment, stricter blast-radius controls, mandatory canary deployments, automatic rollback capabilities, and improved tracking of AI-assisted changes.

Read at InfoWorld