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

@bazylhorsey/aws-dotenv

v1.1.1

Published

Manage your dotenv variables with the help of AWS Secrets Manager

Downloads

3

Readme

version license size node

aws-dotenv :toolbox:

aws-dotenv is a cli tool that manages the envrionment variables for an application stored in the AWS Secrets Manager. The tool can set dotenv variables from your machine to the AWS Secrets Manager and pull them back from AWS to a .env file.

Installation :hammer:

npm install aws-dotenv --save-dev

Configuration :gear:

  • Add .secretsrc to the project root
{
  "name": "My-Project",
  "description": "This project uses aws-dotenv!",
  "keys": [
    "ENV_VARIABLE",
    "ANOTHER_ENV_VARIABLE"
  ]
}

Authentication :key:

Using .awsrc

  • Create .awsrc
{
    "accessKeyId": "ACCESS_KEY_ID",
    "secretAccessKey": "SECRET_ACCESS_KEY",
    "region": "us-east-2"
}

Using AWS default configuration

AWS Credentials can be configured using the AWS CLI tool. For additionnal AWS configuration documentation please refer to Configuration and credential file settings.

  • Configure the AWS account by creating ~/.aws/credentials
[default]
aws_access_key_id=access_key_id
aws_secret_access_key=secret_access_key
  • Configure the AWS region by creating ~/.aws/config
[default]
region=ca-central-1
output=json
  • Create .env at the root of the project
AWS_SDK_LOAD_CONFIG=1

AWS_SDK_LOAD_CONFIG allows the tool to use your ~/.aws/ config folder. We recommend to leave it permanently as well as storing the variable inside AWS Secrets Manager.

Usage :rocket:

$ aws-dotenv (command) (stage)

Available Commands

  • pull
  • set

Stages

Default stage is dev.

Refers to the development stage of the application. It is used to differentiate the multiple .env configurations your project might use at any time. Generally in the form of dev, test and prod but the name does not matter.

example

In these examples the files .env.prod and .env.dev are used. Secret name is defined in AWS Secrets Manager. Setting up package.json

  "scripts": {
    "set-env-dev": "aws-dotenv set {Secret Name}", // Store the environment variables of this machine to AWS Secrets Manager for dev environment.
    "pull-env-dev": "aws-dotenv pull {Secret Name} dev", // Retrieve the environment variables from AWS Secrets Manager dev envrionment to a .env file in the root folder.
    "set-env-prod": "aws-dotenv set {Secret Name}", // Store the environment variables of this machine to AWS Secrets Manager for prod environment.
    "pull-env-prod": "aws-dotenv pull {Secret Name} prod" // Retrieve the environment variables from AWS Secrets Manager prod envrionment to a .env file in the root folder.
  }