Thread replies: 8
Thread images: 3
Thread images: 3
File: sysadmin1-300x227.jpg (24KB, 300x227px) Image search:
[Google]
24KB, 300x227px
>https://aws.amazon.com/message/41926/
>Summary of the Amazon S3 Service Disruption in the Northern Virginia (US-EAST-1) Region
> At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that is used by the S3 billing process. Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended.
>Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended.
>Unfortunately, one of the inputs to the command was entered incorrectly
put your stuff in the cloud guys, so these 'rockstars' can look after you data
>>
"Whenever you're going to do something destructive, read it aloud first."
>>
File: 1479674012254.gif (3MB, 355x201px) Image search:
[Google]
3MB, 355x201px
>>59218000
>>
Holy fuck. My shit was down for most of a day because a pajeet poo on keyboard slapped a * in a command?
>>
>>59220037
Maybe he asked help on /g/.
>>
File: 1479144611854.gif (291KB, 200x331px) Image search:
[Google]
291KB, 200x331px
>>59220093
>AWS was down because he installed Gentoo on every AWS backend.
>>
>>59218000
didnt even notice that it was down
>>
>>59220487
Hey Jeff, watchya doin?
Thread posts: 8
Thread images: 3
Thread images: 3