What a typical serverless architecture looks like in AWS

Re:What a typical serverless architecture looks like in AWS by mcculley on Saturday May 23, 2020 @09:37AM (#23282824)

I recently built a new app on AWS and Lambda. I really wanted to use Cognito to keep everything in AWS. I fought with getting it working for a day or so before giving up and trying out Auth0. I was up and running with Auth0 in a couple hours. I found the Cognito documentation to be insufficient for my needs. Others may have better experiences.

[ Parent | on HN ]

Re:What a typical serverless architecture looks like in AWS by imedadel on Saturday May 23, 2020 @10:07AM (#23283041)

Are you familiar with Firebase's write rules? DynamoDB has something similar with Cognito, but it's _very_ limited.

That's when I figured that I'm not gaining anything by using Cognito.

[ Parent | on HN ]

Re:What a typical serverless architecture looks like in AWS by mcculley on Saturday May 23, 2020 @01:02PM (#23284537)

No, I was not aware of that Firebase functionality as I have never used it. Interesting. Yes, it would be ideal if I could just let another layer do all of the authentication and authorization. That would have worked for the bits of code that use the database. I still would need a way to use the authentication token for things like the Stripe integration.

[ Parent | on HN ]

Re:What a typical serverless architecture looks like in AWS by k__ on Saturday May 23, 2020 @09:45AM (#23282884)

I see.

I understand the wish to keep everything in AWS.

Especially after I read many times thaz Auth0 is pretty expensive. Is this true?

[ Parent | on HN ]

Re:What a typical serverless architecture looks like in AWS by mcculley on Saturday May 23, 2020 @12:55PM (#23284475)

Auth0 is only $23 per month to start with. That's not a lot for my use case.

I would have preferred to keep everything in AWS just to make it easier to use one set of credentials (IAM) to manage permissions.

[ Parent | on HN ]