npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

aws-lambda-auth

v0.1.0

Published

Make your lambda custom authorizer easier

Downloads

7

Readme

aws-lambda-auth

The library allows you to write lambda custom authorizers easier.

Installation

npm install aws-lambda-auth

Using

You have to override handler (AuthHandler) that will generate a policy depends on your conditions.

Let's do it first of all. Minimal case can look so:

const {AuthHandler, utils} = require('aws-lambda-auth');

class MyHandler extends AuthHandler {
  get name() {
    // The handler have to be named
    return 'I will see this name in logs';
  }

  get policyArn() {
    // You have to restrict access to certain ARN
    return utils.buildExecutionApiArn({path: 'users/*'});
  }
}

Then you can use this handler in auth flow:

const {SingleAuthFlow, lambda} = require('aws-lambda-auth');

export default lambda(async ({lambdaEvent, lambdaContext}) => {
  // In real life you will extract token from header or context
  const jwtToken = lambdaEvent.headers.Authorization;
  // You have to decode passed token and pass payload to flow
  // so that you can compare it, check access, etc.
  const tokenPayload = decode(jwtToken);

  return new SingleAuthFlow({lambdaEvent, lambdaContext, tokenPayload})
    .useHandler(MyHandler)
    .createPolicy();
});

That's all. You can build a bundle and deploy to the AWS.

Single flow

Use this flow when there is only one type of user.

look at the example

Multiple flow

Use this flow when there are a few types of users and you want to handle each independently.

look at the example

Middlewares

Middlewares allow you to extend lambda context so that you will have a chance to use in in your handlers.

look at the example

Utils

buildExecutionApiArn

Allows you to build ARN.

Params and default:

  • region = '*'
  • acountId = '*'
  • appId = '*'
  • stage = '*'
  • method = '*'
  • path = '*'