Three cheers to our friends at Fauna as they announce FaunaDB Serverless Cloud, a globally consistent distributed database. This is a guest post from Chris Anderson, Director of Developer Experience at Fauna.
A common serverless application architecture is to run an authentication service, which knows how to connect with OAuth identity providers like Facebook and Github, and exposes an authorizer Lambda that can control access to your functions. This makes authentication code reusable and cleanly separates it from your other functions.
FaunaDB offers instance-level security, so you can model your application’s data sharing patterns in the database. In this example we use the popular
serverless-authentication-boilerplate to connect a FaunaDB app to Facebook login. Thanks to Eetu Tuomala for the help with API Gateway details!
In the Serverless model, the authorizer supplies functions contained in the application with a FaunaDB connection secret that corresponds to the currently logged-in user. This way, there's no possibility of bugs at the application level impacting data integrity and security.
There's no limit to the data security patterns you can model in FaunaDB. See our tutorials for social graph examples, or follow this space for a multi-user TodoMVC example. For now, the content service just looks up the current user in the database.
These instructions for launching the Serverless Authentication Boilerplate with FaunaDB are based on the
This is not simplified example code, rather more like the first steps you'd take when creating a new real world application. The final result is not a cool demo, it's a useful auth service you can rely on. If you're looking for more basic usage of FaunaDB and Serverless, see our blog post about the FaunaDB Serverless CRUD example. There is also a Python version available.
The boilerplate ships with code for a few different identity backends. These steps walk you through installing the service and running it with FaunaDB. The FaunaDB example also integrates with the
test-token example content service. So once you have it running you can look at that code to see how your application would use the database.
npm install -g serverlessand make sure your AWS environment variables are set.
serverless install --url https://github.com/laardee/serverless-authentication-boilerplate, or clone or download the repository.
authentication/env.ymland set environmental variables. Delete the
CacheTableentry to avoid provisioning DynamoDB tables you won't be using.
authentication/env.ymlwith a server secret for your database.
exports = module.exports = faunaCache;
STAGE=dev npm run setup:faunato create your FaunaDB schema.
serverless deployto deploy test-token service.
Look here for the code to the test-token service and here for the code that uses FaunaDB as an authentication cache and user store.
There's no need to configure the
test-token service with database access, as the
authorize function provides a database access secret that matches the current user. Each function invocation runs only with the privileges of the current user. In a future post we'll show how to model ownership of data instances, read and update control, and delegation of capabilities to other users.
With FaunaDB you get multi-region cross-cloud replication of your data, with the option to run on-premise, avoiding vendor lock-in. You also get a functional relational query language and the ability to define complex indexes. There are temporal support for sync, audit and snapshot queries. And you never have to pre-provision, so you only pay for the database you use. Launch FaunaDB and you'll be storing data in moments.
Chris Anderson is Director of Developer Experience at Fauna.
operations-and-observabilityguides-and-tutorials - 12.02.18
A breakdown of the top serverless security risks, and steps you can take to secure your serverless applications.
written by Adnan Rahic
news - 28.11.18
AWS open-sourced Firecracker, the Lambda and Fargate core. Here’s what it means for the serverless community.
written by Jared Short