4 ms·

Just to chime in here and maybe help explain some of the more snarky responses... If I were in your shoes, I wouldn't expect one, and if one ever does get publ

Just to chime in here and maybe help explain some of the more snarky responses... If I were in your shoes, I wouldn't expect one, and if one ever does get published, be suspicious of it. VERY suspicious. Because it's likely missing critical information and/or some portion is likely fictitious to some degree. I mean, this is a company that can't even update its own system status dashboard truthfully, so don't expect any degree of honesty or accountability here.

beebmam 5y ago
Frankly, why should a company NOT lie? There's no reason to tell the truth if the truth will hurt your business.
- mapmap 5y ago
  Credibility?
- yunwal 5y ago
  I'm an infrastructure engineer that has never considered using a comparable cloud provider unless the solution I was looking for wasn't supported by AWS. It used to feel like AWS cared about it's reputation and trustworthiness, and now they clearly do not. If I was starting a project from scratch now, I'd certainly explore other cloud providers, which is not something I would've said 3 years ago. Their blatant lying is definitely going to cost them in the long run.
  - ptcrash 5y ago
    When did AWS lie? On their status page? That's the last place to receive updates on service status. It sucks but it's also common knowledge. I'll give you a little insider knowledge: The SHD is updated manually. If it's any consolation, GCP does the exact same thing. I saw notifications in the AWS Personal Health Dashboard pretty very early into the issue. Did you see something different? Also, I've seen issues logging into the default console a lot, so I keep one of the backup endpoints bookmarked. Might come in handy for you too! https://us-east-2.console.aws.amazon.com/ https://us-east-2.console.aws.amazon.com/
  - randombits0 5y ago
    If you do not design your cloud resources to be vendor-independent, that’s on you. You absolutely need the ability to cross vendors in short order, whatever stack you’re running.
    - yuppie_scum 5y ago
      This is easy for the Monday morning armchair QB to say, but the fact of the matter is that most SMBs are not in a position to run multi cloud. Legacy pre container pre kube workloads (tech debt) exist, as do persistent data stores that are too large to replicate between clouds without racking up massive transfer costs. Not even getting into vendor lock-in around networking or things like dynamo or serverless. “Well just move all your stuff to Kube then!” Ok fine, mr CTO, I’ll do it but I’ll need about 3 engineers at 175k and budget a couple mil more in Op Ex. the reality of the matter is that most of us will just gear for MTTR and hope that Amazon takes some lessons from the incident.
ptcrash 5y ago
Having some authority on the subject because I've seen how both GCP and AWS handle their public status pages internally. They are manually updated by hand and are the last step in raising a large-scale issue. Automated issue notifications get pushed to the Personal Health Dashboard for AWS and to my knowledge, GCP doesn't have automated status updates available to customer. (But AWS requires a support plan to gain access to their PHD, so it can be considered inaccessible to many as well).
systemvoltage 5y ago
I wish HN was more professional. It used to be.
- jankcorn 5y ago
  +1
- R0b0t1 5y ago
  Professionals recognize professionals lie.
  - dang 5y ago
    Please don't post unsubstantive and/or flamebait comments to HN. We're trying for something else here. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
    - R0b0t1 5y ago
      Strong disagree. The suggestion that they could be lying is what is under question in this comment chain. And, certainly, they could be, informed not only by general life experience but directly by the threads about Amazon management culture that pop up. If professionals don't lie then why do doctors get popped for writing bad prescriptions? Why did scientists and executives lie about the harms of tobacco or lead? Etc. What is being fought here is the suggestion that Amazon and its workers have some drive to tell the truth. Common sense dictates that is false. Keep in mind an Amazon employee could have flagged my comment out of self interest.
      - dang 5y ago
        Sorry, but your GP comment was obviously unsubstantive flamebait. This isn't a borderline call. If you have some specific information to add to the discussion, by all means post it (in an informative way, not a provocative way). But definitely please don't post like the above. Even your reply here is nothing but rhetoric. Edit: I just noticed https://news.ycombinator.com/item?id=29427506 https://news.ycombinator.com/item?id=29427506. Posting like that ("please consider offing as many CBP officials as possible") is very obviously a bannable offense on HN. I won't ban you for a week-old comment now, but if you do anything like that again, we will have to. Actually that comment is so shocking that I really had to think about this for a while. But you've also posted quite a lot of good comments in the past, so perhaps it will suffice to ask you to please review https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on.

beebmam 5y ago

Frankly, why should a company NOT lie? There's no reason to tell the truth if the truth will hurt your business.

mapmap 5y ago
Credibility?
yunwal 5y ago
I'm an infrastructure engineer that has never considered using a comparable cloud provider unless the solution I was looking for wasn't supported by AWS. It used to feel like AWS cared about it's reputation and trustworthiness, and now they clearly do not. If I was starting a project from scratch now, I'd certainly explore other cloud providers, which is not something I would've said 3 years ago. Their blatant lying is definitely going to cost them in the long run.
- ptcrash 5y ago
  When did AWS lie? On their status page? That's the last place to receive updates on service status. It sucks but it's also common knowledge. I'll give you a little insider knowledge: The SHD is updated manually. If it's any consolation, GCP does the exact same thing. I saw notifications in the AWS Personal Health Dashboard pretty very early into the issue. Did you see something different? Also, I've seen issues logging into the default console a lot, so I keep one of the backup endpoints bookmarked. Might come in handy for you too! https://us-east-2.console.aws.amazon.com/ https://us-east-2.console.aws.amazon.com/
- randombits0 5y ago
  If you do not design your cloud resources to be vendor-independent, that’s on you. You absolutely need the ability to cross vendors in short order, whatever stack you’re running.
  - yuppie_scum 5y ago
    This is easy for the Monday morning armchair QB to say, but the fact of the matter is that most SMBs are not in a position to run multi cloud. Legacy pre container pre kube workloads (tech debt) exist, as do persistent data stores that are too large to replicate between clouds without racking up massive transfer costs. Not even getting into vendor lock-in around networking or things like dynamo or serverless. “Well just move all your stuff to Kube then!” Ok fine, mr CTO, I’ll do it but I’ll need about 3 engineers at 175k and budget a couple mil more in Op Ex. the reality of the matter is that most of us will just gear for MTTR and hope that Amazon takes some lessons from the incident.

ptcrash 5y ago

Having some authority on the subject because I've seen how both GCP and AWS handle their public status pages internally. They are manually updated by hand and are the last step in raising a large-scale issue. Automated issue notifications get pushed to the Personal Health Dashboard for AWS and to my knowledge, GCP doesn't have automated status updates available to customer. (But AWS requires a support plan to gain access to their PHD, so it can be considered inaccessible to many as well).

systemvoltage 5y ago

I wish HN was more professional. It used to be.

jankcorn 5y ago
+1
R0b0t1 5y ago
Professionals recognize professionals lie.
- dang 5y ago
  Please don't post unsubstantive and/or flamebait comments to HN. We're trying for something else here. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
  - R0b0t1 5y ago
    Strong disagree. The suggestion that they could be lying is what is under question in this comment chain. And, certainly, they could be, informed not only by general life experience but directly by the threads about Amazon management culture that pop up. If professionals don't lie then why do doctors get popped for writing bad prescriptions? Why did scientists and executives lie about the harms of tobacco or lead? Etc. What is being fought here is the suggestion that Amazon and its workers have some drive to tell the truth. Common sense dictates that is false. Keep in mind an Amazon employee could have flagged my comment out of self interest.
    - dang 5y ago
      Sorry, but your GP comment was obviously unsubstantive flamebait. This isn't a borderline call. If you have some specific information to add to the discussion, by all means post it (in an informative way, not a provocative way). But definitely please don't post like the above. Even your reply here is nothing but rhetoric. Edit: I just noticed https://news.ycombinator.com/item?id=29427506 https://news.ycombinator.com/item?id=29427506. Posting like that ("please consider offing as many CBP officials as possible") is very obviously a bannable offense on HN. I won't ban you for a week-old comment now, but if you do anything like that again, we will have to. Actually that comment is so shocking that I really had to think about this for a while. But you've also posted quite a lot of good comments in the past, so perhaps it will suffice to ask you to please review https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on.