Dan Goosby dangoosby
| { | |
| "rules" : [ | |
| { | |
| "name": "parameter-description", | |
| "object": "parameter", | |
| "enabled": true, | |
| "description": "parameter objects should have a description", | |
| "truthy": "description" | |
| }, | |
| { |
| /* | |
| Name: Database Snapshot | |
| Purpose: Create a Manual AWS RDS Snapshot from most recent Automated AWS RDS Snapshot of Database | |
| */ | |
| package main | |
| import ( | |
| "fmt" |
On 2/28/17, AWS had an outage for 4hrs within the us-east-1 region that affected the S3 service. Specifically, an S3 team member executed a command to remove a small number of servers on one of the S3 subsystems. This was executed incorrectly which resulted in a larger set of servers were removed unintentionally. One of those subsystems manages the metadata and location information of all the S3 objects in the North Virginia region making the negative effect greater. While the AWS S3 team designed their subsytems for removal or failure of significant capacity, they have not completely restarted the index subsystem or the placement subsystem in larger regions for many years; the process of restarting those services and running the necessary safety checks took longer than expected.
AWS is making several changes as result of this event. Firstly, the tool used all