4 ms·

What's missing is addressing the problems with their status page system, and how we all had to use Hacker News and other sources to confirm that US East was bor

• Scramblejams 10y ago
  No, this is addressed: >We understand that the SHD provides important visibility to our customers during operational events and we have changed the SHD administration console to run across multiple AWS regions.
  • yellow_postit 10y ago
    Which is fine until those regions go down. A status page, in my mind, should have a fallback on a completely different service provider.
    • aorloff 10y ago
      Exactly. What they should do is have the status system be independent of AWS so it can report issues regardless of AWS service status.
      • Piskvorrr 10y ago
        Awsnap! http://dilbert.com/strip/2008-02-15 http://dilbert.com/strip/2008-02-15
• danesparza 10y ago
  This was addressed in the post: "From the beginning of this event until 11:37AM PST, we were unable to update the individual services’ status on the AWS Service Health Dashboard (SHD) because of a dependency the SHD administration console has on Amazon S3. Instead, we used the AWS Twitter feed (@AWSCloud) and SHD banner text to communicate status until we were able to update the individual services’ status on the SHD. We understand that the SHD provides important visibility to our customers during operational events and we have changed the SHD administration console to run across multiple AWS regions."