Yeah, and it wasn't too long ago that SO Documentation was shut down as well. Hopefully Channels works out better for them.
Confirmed this is also impacting CodeDeploy in us-east-1, makes sense since it has S3 dependency on revision location.
Yes, seeing issues with the autoscaling API for a single zone in us-east-1.
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…
Something that wasn't addressed -- there seems to be an architectural issue with ELB where ELBs with S3 access logs enabled had instances fail ELB health checks, presumably while the S3 API was returning 5XX. My load…
Experiencing issues with S3 and ELB for over an hour now.
I hope this starts a trend. It has been very frustrating to see large services stop offering RSS feeds, often with no or cumbersome alternatives.
Yeah, and it wasn't too long ago that SO Documentation was shut down as well. Hopefully Channels works out better for them.
Confirmed this is also impacting CodeDeploy in us-east-1, makes sense since it has S3 dependency on revision location.
Yes, seeing issues with the autoscaling API for a single zone in us-east-1.
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…
Something that wasn't addressed -- there seems to be an architectural issue with ELB where ELBs with S3 access logs enabled had instances fail ELB health checks, presumably while the S3 API was returning 5XX. My load…
Experiencing issues with S3 and ELB for over an hour now.
I hope this starts a trend. It has been very frustrating to see large services stop offering RSS feeds, often with no or cumbersome alternatives.