cloudfront-auth VS supertokens-website

If you already have existing users in google, github, or something like that, maybe look at this https://github.com/Widen/cloudfront-auth and skip cognito.

This article shows how to deploy your own EventCatalog in AWS CloudFront via Terraform and updates to the Catalog via CI/CD (CircleCi in this case, but can be easily applied to other CI systems). It also shows how to use Lambda@Edge to implement Google SSO / OpenID Connect via the Widen/cloudfront-auth Project.

Using it to allow Google Workspace auth access control to static websites. Leverages https://github.com/Widen/cloudfront-auth

aws.amazon.com Recognition The earlier AWS blog that investigated wiring up Cognito authentication with Lambda@Edge: https://aws.amazon.com/blogs/networking-and-content-delivery/authorizationedge-how-to-use-lambdaedge-and-json-web-tokens-to-enhance-web-application-security/ A gist that shows how to add Basic Authentication using Lambda@Edge: https://gist.github.com/lmakarov/e5984ec16a76548ff2b278c06027f1a4 An open-source project that uses a similar approach to secure CloudFront distributions, but does not yet support Cognito (at the time of this writing): https://github.com/Widen/cloudfront-auth Additional resources Check out the code on GitHub to see how the sample solution is built. You can deploy and run the code yourself: https://github.com/aws-samples/cloudfront-authorization-at-edge. You can deploy the Amazon Cognito resources from the sample solution directly from the AWS Serverless Application Repository. 10

1) Make sure your bucket is private. 2) Set up CloudFront with Origin Access Identity 3) Use Lambda@Edge for authentication.