Security News
38% of CISOs Fear They’re Not Moving Fast Enough on AI
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
@smallwins/lambda
Advanced tools
lambda-create
, lambda-list
, lambda-deploy
and lambda-invoke
Here is a vanilla AWS Lambda example for performing a sum. Given event.query.x = 1
it will return {count:2}
.
exports.handler = function sum(event, context) {
var errors = []
if (typeof event.query === 'undefined') {
errors.push(ReferenceError('missing event.query'))
}
if (event.query && typeof event.query != 'object') {
errors.push(TypeError('event.query not an object'))
}
if (typeof event.query.x === 'undefined') {
errors.push(ReferenceError('event.query not an object'))
}
if (event.query.x && typeof event.query.x != 'number') {
errors.push(TypeError('event.query not an object'))
}
if (errors.length) {
// otherwise Error would return [{}, {}, {}, {}]
var err = errors.map(function(e) {return e.message})
context.fail(err)
}
else {
context.succeed({count:event.query.x + 1})
}
}
A huge amount of this code is working around quirky parameter validation. Builtin Error
needs manual serialization (and you still lose the stack trace). The latter part of the code uses the funky AWS context
object.
We can do better:
var validate = require('@smallwins/validate')
var lambda = require('@smallwins/lambda')
function sum(event, callback) {
var schema = {
'query': {required:true, type:Object},
'query.x': {required:true, type:Number}
}
var errors = validate(event, schema)
if (errors) {
callback(errors)
}
else {
var result = {count:event.query.x + 1}
callback(null, result)
}
}
exports.handler = lambda(sum)
@smallwins/validate
takes care of parameter validation. The callback style above enjoys symmetry with the rest of Node and will automatically serialize Error
s into JSON friendly objects including any stack trace. All you need to do is wrap a vanilla Node errback function in lambda
which returns your function with an AWS Lambda friendly signature.
Building on this foundation we can compose multiple errbacks into a Lambda. Lets compose a Lambda that:
Error
arrayvar validate = require('@smallwins/validate')
var lambda = require('@smallwins/lambda')
function valid(event, callback) {
var schema = {
'body': {required:true, type:Object},
'body.username': {required:true, type:String},
'body.password': {required:true, type:String}
}
validate(event, schema, callback)
}
function authorized(event, callback) {
var loggedIn = event.body.username === 'sutro' && event.body.password === 'cat'
if (!loggedIn) {
// err first
callback(Error('not found'))
}
else {
// successful login
event.account = {
loggedIn: loggedIn,
name: 'sutro furry pants'
}
callback(null, event)
}
}
function safe(event, callback) {
callback(null, {account:event.account})
}
exports.handler = lambda(valid, authorized, safe)
In the example above our functions are executed in series passing event through each invocation. valid
will pass event to authorized
which in turn passes it to save
. Any Error
returns immediately so if we make it the last function we just send back the resulting account data. Clean!
AWS DynamoDB can invoke a Lambda function if anything happens to a table.
var lambda = require('@smallwins/lambda')
function save(record, callback) {
console.log('save a version ', record)
callback(null, record)
}
exports.handler = lambda.sources.dynamo.save(save)
lambda(...fns)
lambda.sources.dynamo.all(...fns)
lambda.sources.dynamo.save(...fns)
lambda.sources.dynamo.insert(...fns)
lambda.sources.dynamo.modify(...fns)
lambda.sources.dynamo.remove(...fns)
A handler looks something like this
function handler(event, callback) {
// process event, use to pass data
var result = {ok:true, event:event}
callback(null, result)
}
Good error handling makes your programs far easier to maintain. (This is a good guide.)[https://www.joyent.com/developers/node/design/errors]. When using @smallwins/lambda
always use Error
type as the first parameter to callback:
function fails(event, callback) {
callback(Error('something went wrong')
}
Or an Error
array:
function fails(event, callback) {
callback([
Error('missing email'),
Error('missing password')
])
}
@smallwins/lambda
serializes error into Slack RPC style JSON making them easy to work from API Gateway:
{
ok: false,
errors: [
{name:'Error', message:'missing email', stack'...'},
{name:'Error', message:'missing password', stack'...'}
]
}
@smallwins/lambda
includes some helpful automation code perfect for npm scripts. If you have a project that looks like this:
project-of-lambdas/
|-test/
|-src/
| '-lambdas/
| |-signup/
| | |-index.js
| | |-test.js
| | '-package.json
| |-login/
| '-logout/
'-package.json
And a package.json
like this:
{
"name":"project-of-lambdas",
"scripts": {
"create":"AWS_PROFILE=smallwins lambda-create",
"list":"AWS_PROFILE=smallwins lambda-list",
"deploy":"AWS_PROFILE=smallwins lambda-deploy",
"invoke":"AWS_PROFILE=smallwins lambda-invoke",
"deps":"AWS_PROFILE=smallwins lambda-deps"
}
}
brian
The ./scripts/invoke.js
is also a module and can be useful for testing.
var invoke = require('@smallwins/lambda/scripts/invoke')
invoke('path/to/lambda', alias, payload, (err, response)=> {
console.log(err, response)
})
FAQs
Author your AWS Lambda functions as node style errbacks.
The npm package @smallwins/lambda receives a total of 0 weekly downloads. As such, @smallwins/lambda popularity was classified as not popular.
We found that @smallwins/lambda demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.