Re:Summary of the Amazon S3 Service Disruption
by hyperanthony on Thursday March 02, 2017 @01:12PM
(#13776580)
Thanks, that is a fair perspective. In our case we're using ELB logs as a redundant trace and it isn't critical that our traffic stops if the access logs fail. It would be nice if this behavior became a toggle in ELB settings, but think we can set something up to disable access logs programatically if we start seeing S3 issues.
[ Parent
| on HN ]
Re:Summary of the Amazon S3 Service Disruption
by ctrlrsf on Thursday March 02, 2017 @04:20PM
(#13778328)
Good luck with this. We tried to make changes yesterday to mitigate impact but AWS console was also affected. Was hesitant to make API calls for the changes since we werent sure they would complete successfully given all the services we found actually depended on S3 internally.