Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Cognito is having issues and health dashboards are still green

status.aws.amazon.com

Post reply on HN
Print view View original

121–130 of 369 posts

Re: AWS Cognito is having issues and health dashboards are still green

#121

Post by Griffinsauce »

s_dev wrote: post #25

Can anyone explain why status pages are so difficult. Theres even statups like status.io dedicated to this one thing. It really does seem that anytime there is an outage more often than not the status page is showing all green traffic lights. Making it redundant as a tool to corroborate whats happening. How did AWS status page compare with status.io/aws?

This is why my instinct is to check Twitter feeds of the related service first. So far in several years of experience it has been more informative and helpful than a status has ever been. It's a sad state.

Re: AWS Cognito is having issues and health dashboards are still green

#122

Post by drfritznunkie »

sk5t wrote: post #108
drfritznunkie wrote: post #86

Cognito is one of the most frustrating AWS services I have to work with, it is almost, but not quite, entirely unlike an SP. We're using it to federate customer IDPs through user pools, but this ends up with customer configs being region specific. Has anyone figured out how to set up Cognito in multiple regions without the hijinx of having the customer setup trusts for each region? Not to mention, while multiple trus…

Eh? Brokering amongst multiple trusts (and managing protocol transition) is almost the raison d'etre for lifting token issuance out of your app and into ADFS, Okta, Auth0, etc. Of course you'll have to deal with home realm discovery--really need to go in with open eyes on that one.

Yes, but cognito endpoints and pools ids are regional and globally unique, and there is no way that I know of to setup duplicate userpools in multiple regions and have requests served by either region. That means the customer IDP side would need to have two different SAML apps configured for each region...

Re: AWS Cognito is having issues and health dashboards are still green

#123

Post by Griffinsauce »

ti_ranger wrote: post #89
rexreed wrote: post #74

Earlier quoted context omitted.

Yes but only if you initiate a claim and follow their steps. Check out these onerous terms: Credit Request and Payment Procedures To receive a Service Credit, you must submit a claim by opening a case in the AWS Support Center. To be eligible, the credit request must be received by us by the end of the second billing cycle after which the incident occurred and must include: 1. the words “SLA Credit Request” in the su…

> Yes but only if you initiate a claim and follow their steps. Check out these onerous terms: There's most likely a reason for this. Like, maybe in the past AWS customers have tried claiming for SLA credits for incidents that didn't impact them, in order to reduce their bill.

It's much more likely that the reason is someone going "well what if people want to abuse this?" without any evidence that they would.

Also: requiring your customers to ask for their money back when you know that you didn't deliver the service promised and all other billing is automated.. come on.

Re: AWS Cognito is having issues and health dashboards are still green

#124

Post by Griffinsauce »

gt565k wrote: post #88
RohMin wrote: post #31

Earlier quoted context omitted.

You've missed the point entirely, bravo

Ughh, he claims to have been scammed by AWS because their services are having an outage, and I'm missing the point? This stupid hyperboles need to be shot down. I'm sick and tired of the victim mentality and hyperboles. Every time something inconvenient happens, people scream and shout at the top of their lungs like the world has wronged them. NO, YOU DID NOT GET SCAMMED BY AMAZON BECAUSE THEY HAVE A SERVICE OUTAGE.…

Congrats on missing the point more loudly and repeatedly.

Re: AWS Cognito is having issues and health dashboards are still green

#125

Post by willcipriano »

Twirrim wrote: post #117
jtdev wrote: post #102

Earlier quoted context omitted.

Maybe they should ask a question about resilient status page architecture among the ridiculous coding riddles they give candidates...lol!

Part of the problem is, engineers love shiny things. Status pages are fundamentally boring things. Who wants to work on them? It's always tempting to complicate something simple because in part "ooh shiny", and you can always find reasons to justify why. It takes some strong engineering leadership to effectively argue against complicating things, and not be just a constant pain in the arse to everyone and every thing…

>Part of the problem is, engineers love shiny things. Status pages are fundamentally boring things. Who wants to work on them?

I would work on a status page. It's a interesting problem, creating tests that prove services are viable at a place like AWS would be fun. However what I don't want to deal with is some director of so and so I never heard of yelling at me at 3 in the morning because my status page reported that his service was down accurately. I suspect that plays more into the problem. The status page is a political implement not a technical one.

Re: AWS Cognito is having issues and health dashboards are still green

#126

Post by WrtCdEvrydy »

simlevesque wrote: post #120
jjoonathan wrote: post #106

Earlier quoted context omitted.

That's typical. The AWS status page is a marketing gimmick whose job is to stay green, not a good faith attempt to assess and report status. If there's an outage, seeing it accurately reflected on the status page is the exception, not the rule.

Isn't that fraud ? edit: not sure why my question deserved a downvote...

If you're small, yes, if you're AWS, it's business as usual?

Re: AWS Cognito is having issues and health dashboards are still green

#127

Post by GilbertErik »

tuwtuwtuwtuw wrote: post #107
Frost1x wrote: post #94

Earlier quoted context omitted.

I find it surprising how many people forget how much underlying business motives drive pretty much every action they make and how this is quickly forgotten by many. No matter how much you value science and engineering, it ultimately doesn't matter to the business unless that aligns directly with their revenue stream. Sometimes it does, sometimes it doesn't.

Yes. But I wonder if self-hosting their status page is really the correct decision from a marketing perspective. The people who consumes the status page on say Google Cloud probably know that Google self-hosting it is a bad decision from a technical point of view. So to the only people who care, their choice appear stupid. So I don't really understand what they gain by doing it. I think maybe I am wrong about it bein…

If they host it somewhere else, it signals they lack confidence in their own product.

If they self-host it, it signals that they're overconfident in their ability to maintain an accurate status page.

Given these two options, which do you think a budget manager will have an easier time signing off on and defending upward?

Re: AWS Cognito is having issues and health dashboards are still green

#128

Post by piewzko »

Now is probably a good time to plug some of the open source alternatives to vendor locked in identity solutions:

- https://github.com/ory

- https://github.com/dexidp/dex

- https://github.com/authelia/authelia

- https://github.com/keycloak/keycloak

- https://www.gluu.org/

- https://github.com/accounts-js/accounts

Re: AWS Cognito is having issues and health dashboards are still green

#129

Post by srveale »

tuwtuwtuwtuw wrote: post #63
turdnagel wrote: post #18

Isn't it common practice to host your status board on someone else's infrastructure? In 2017 there was an S3 issue that supposedly affected their ability to post. I believe they said that they were updating how they posted to the status board so that there would no longer be a dependency on S3. Well, I guess whatever they're dependent on now broke.

It's common practice for small players but Amazon, Microsoft Azure and Google Cloud host their status pages on their own servers because they value the marketing aspect higher than a functioning status page for their customers.

Reminds me of: "When a measure becomes a target, it ceases to be a good measure"

When you're advertising uptime/availability, you're motivated not to report downtime/unavailability. Then the value of such reports is lost; developers start banging their heads trying to figure out if it's a service outage or a bug in their software (yes, informed by personal experience).

Re: AWS Cognito is having issues and health dashboards are still green

#130

Post by swyx »

s_dev wrote: post #25

Can anyone explain why status pages are so difficult. Theres even statups like status.io dedicated to this one thing. It really does seem that anytime there is an outage more often than not the status page is showing all green traffic lights. Making it redundant as a tool to corroborate whats happening. How did AWS status page compare with status.io/aws?

there's also https://stop.lying.cloud/
Post reply on HN