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-lockbox

v2.0.3

Published

AWS SSM Secrets manager

Downloads

329

Readme

AWS Lockbox

aws-lockbox is a secrets management service for node and AWS Parameter Store (SSM). aws-lockbox handles all of your secrets by running on app start. It will populate the appropriate process.env variables with parameters stored in your AWS Parameter Store.

Getting Started

Directory Structure

  1. You variables need to be available in AWS Parameter Store (SSM)
  2. Have a local lockbox directory with corresponding environment names as files in your root folder
    • There are two properties that are utilized in the lockbox configuration files: parameters and overrides.
      • parameters is an array of parameter names (strings) that are found in SSM
      • overrides is an array of key value pairs that you want to override locally
    • default.js is defaulted to if there is no file that matches the environment variable.
lockbox/
    - production.js
    - stage.js
    - development.js
    - local.js
    - default.js

Initialization

/*
* The max number of tries you want to attempt before throwing an error.
* It uses exponential backoff to avoid conflicts with other services that use aws-lockbox
*/
const maxTries = 100;
const lb = new Lockbox.Lockbox(maxTries);
lb.exec();

/*
* waitMS together winpm init --scopeth maxWaits allows you to determine how long you want to wait
* before stopping. Stopping by default means, throwing an error.
*/
const waitMS = 100;
const maxWaits = 10;
await lb.wait(maxWaits, waitMS);

Overview

default.js

This is where you put the name of the keys that you wished to pull from Parameter Store. All the other files in lockbox/ depend on default.js and it's parameters list.

module.exports = {
  parameters: [
    "THE_NAME_OF_THE_PARAMETER_1",
    "THE_NAME_OF_THE_PARAMETER_2",
    ...
  ]
}

[your environment].js | production.js | stage.js | dev.js | localdev.js | etc.

const defaultParameters = require('./default.js');
module.exports = {
  parameters: defaultParameters.parameters,
  overrides: [
    {
      Name: "THE_NAME_OF_THE_PARAMETER,
      Value: "the value of the parameter"
    }
  ],
}

parameters: []

This is where you can add parameters to retrieve from Parameter Store

overrides: []

This is where you can add as many Name, Value pairs as you want to override