Changes between Initial Version and Version 1 of Ticket #2068


Ignore:
Timestamp:
2013-08-29T13:21:40Z (11 years ago)
Author:
daira
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2068 – Description

    initial v1  
    1 LeastAuthority.com's monitoring sees occasional DNS errors [https://github.com/LeastAuthority/leastauthority.com/issues/30] when trying to resolve $BUCKETNAME.s3.amazonaws.com from an EC2 instance. It could fall back to a bucket-in-path URL for retries in this case. Alternatively, it may be that the existing retry is sufficient to mask these failures, but we need to know whether that is the case. (The monitoring code does not retry.)
     1!LeastAuthority.com's monitoring sees occasional DNS errors [https://github.com/LeastAuthority/leastauthority.com/issues/30] when trying to resolve $BUCKETNAME.s3.amazonaws.com from an EC2 instance. It could fall back to a bucket-in-path URL for retries in this case. Alternatively, it may be that the existing retry is sufficient to mask these failures, but we need to know whether that is the case. (The monitoring code does not retry.)
    22
    33(We originally switched to bucket-in-host URLs because bucket-in-path requests were sometimes failing, claiming that we were using the wrong endpoint. If that happens in the same situation as the DNS failures, then we might not be able to improve reliability by falling back to bucket-in-path.)