i try to keep my comments on here positive, but man, my experience using this product has been awful.
paulddraper 1 days ago [-]
You should really stay away from any "high level" AWS product, as there is almost always something much better and more flexible.
Use EC2, EBS, S3, Route53 plus EKS, RDS, ElastiCache.
But anything else that isn't low-to-mid-level (looking at you Beanstalk), use something better.
Clerk, WorkOS, etc.
dogma1138 17 hours ago [-]
Cognito isn’t a high level product not anymore than any of those you’ve mentioned it’s a CIAM solution.
paulddraper 16 hours ago [-]
It's a Clerk/Auth0/WorkOS alternative.
If you implemented it yourself, you would do it on top of those.
cmiles8 1 days ago [-]
This has been an obvious feature request for many years, but glad to see AWS investing in what started to feel like a service that was mostly abandoned for investment.
jeffwask 1 days ago [-]
I recall complaining about this with one of my architects who was looking to implement Cognito round about 2019.
ecshafer 1 days ago [-]
Cognito just supported multi-region? For identity this seems like a very high priority issue. I was at a company 10 years ago that we didn't use Cognito to build, and build our own AWS based identity because Cognito didn't have this (and just seemed pretty half-baked).
arpinum 1 days ago [-]
They wanted to rebase onto a different database first to make multi-region easier, but that work took many years.
mannyv 1 days ago [-]
Yay, it's only taken them years to do this.
Since the pool identifiers are static, how do you actually fail over?
Oh, you need a custom domain that presumably routes if the primary dies.
jwnin 1 days ago [-]
This prevented us from failing over during last October's outage (unless we wanted to reset everyone's password). Glad to see AWS focusing in on resiliency.
mooreds 1 days ago [-]
I work for a Cognito competitor, but I am glad to see them investing in improving the lives of folks using this native AWS service.
It felt like Cognito was abandoned for a while.
grimleech 1 days ago [-]
[dead]
UltraSane 1 days ago [-]
This should have been available from the beginning. I don't understand why it took so long.
semiquaver 1 days ago [-]
I think cognito was internally low-staff/KTLO for a while and that changed recently.
mooreds 1 days ago [-]
What does KLTO mean?
Insanity 1 days ago [-]
To add to the other posters, keep-the-lights-on usually means a product has no active feature development. It’s just supported with on-call and maybe some bug fixes depending on capacity.
No clue if Cognito actually was KTLO though.
xyzzy_plugh 1 days ago [-]
Probably meant KTLO: Keep The Lights On
christophercork 1 days ago [-]
"Keep Lights To On." It's the post-it on the light switch wired to the Cognito server.
crises-luff-6b 1 days ago [-]
[dead]
Rendered at 18:26:34 GMT+0000 (Coordinated Universal Time) with Vercel.
Use EC2, EBS, S3, Route53 plus EKS, RDS, ElastiCache.
But anything else that isn't low-to-mid-level (looking at you Beanstalk), use something better.
Clerk, WorkOS, etc.
If you implemented it yourself, you would do it on top of those.
Since the pool identifiers are static, how do you actually fail over?
Oh, you need a custom domain that presumably routes if the primary dies.
It felt like Cognito was abandoned for a while.
No clue if Cognito actually was KTLO though.