2 ms·
I'm not seeing any UX problems here. They configured an S3 access policy incorrectly while troubleshooting, 5 years ago. FTFA: > During our incident review,
by politelemon 6y ago
I'm not seeing any UX problems here. They configured an S3 access policy incorrectly while troubleshooting, 5 years ago.
FTFA:
> During our incident review, we identified that this path was not initially configured with public write access when it was added in 2015. We implemented a change 5 months later while troubleshooting a problem with one of our build systems and the permissions on that path were not properly reset once the issue had been fixed.
> {
"Sid": "AllowPublicRead",
"Effect": "Allow",
"Principal": {
"AWS": ""
},
"Action": [
"s3:GetObject",
"s3:PutObject"
],
"Resource": "arn:aws:s3:::media.twiliocdn.com/taskrouter/"
}
- soco 6y agoThis is exactly one of the things Terraform would catch and correct in a snap. I rather think Twilio was so confident before they had everything understood and smooth running that they didn't need other tools like Terraform. Infrastructure as code emerged as a thing EXACTLY because cloud's hundreds of consoles and checkboxes and whatnot, although each one simple and logical, spinned out of our mind's capacity to hold.