An experiment building passkey-based auth with Swift and AWS
AWS Cognito is the user database. Cognito can do all kinds of things, including built-in support for Sign in with Apple. But, as of right now, it does not support WebAuthn. So, custom hooks and a WebAuthn package are required and made this project much more complex.
AWS API Gateway is used as an HTTP server.
Routes:
GET /.well-known/apple-app-site-associationGET /makeCredential?username=xyzPOST /makeCredential?username=xyz
AWS Lambda is used to run the Swift code for the HTTP server responses and Cognito hooks.
AWS CloudFormation is used to set up and configure the AWS resources.
I had a goal of making this all zero-cost. Unforutnately, I ran into a snag. Apple's AuthenticationServices framework requires a domain that serves /.well-known/apple-app-site-association. And a top-level path requires using a custom domain with API Gateway. This is possible do with CloudFormation, but requires a Route 53 hosted zone, which costs 0.50$ per month. To get around this, I left the custom domain for API Gateway manual.
Everyone interacting in the rake-remote-file project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.