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

mmm-aws-cli

v1.1.3

Published

Meteor Multiverse Manager wrapper for the Amazon AWS CLI

Downloads

17

Readme

mmm-aws-cli

GitHub Latest Release Build Status

Meteor Multiverse Manager wrapper for the Amazon AWS CLI

Install

Install via NPM:

npm install mmm-aws-cli

IMPORTANT: This module will only work on MacOSX and/or Linux!

Configure

Get Your Amazon IAM User Access Keys

If you have not previously downloaded your IAM User Access Keys from Amazon, you will need to create (and download) a new set of User Access Keys.

Configure Your Local AWS Credentials

Update Your AWS Config File

Open the file ~/.aws/credentials for editing, e.g. with TextEdit on MacOSX:

open -a TextEdit ~/.aws/credentials

Here's what that file will look like initially:

[default]
aws_access_key_id=ACCESS_KEY
aws_secret_access_key=SECRET_KEY
aws_session_token=OPTIONAL_TOKEN
region=us-east-1

[{{LOCAL_PROFILE_NAME_OR_USERNAME_GOES_HERE}}]
aws_access_key_id={{YOUR_ACCESS_KEY_ID_GOES_HERE}}
aws_secret_access_key={{YOUR_SECRET_KEY_GOES_HERE}}
region=us-east-1

Whereever you see a {{SOME_FIELD_NAME}} annotation above, substitute in the corresponding value from your downloaded AWS Access Keys CSV file.

So, for example, my [fake] credentials file might look like this:

[default]
aws_access_key_id=ACCESS_KEY
aws_secret_access_key=SECRET_KEY
aws_session_token=OPTIONAL_TOKEN
region=us-east-1

[jgreene]
aws_access_key_id=BKICIINQZH2LTSDKLJVE
aws_secret_access_key=3dKaqob+KAjTXN6ugw9a2buYHguzsxgtptuS3fH2
region=us-east-1

Export New Environment Variables

Add the following new environment variables to your ~/.bash_profile file (or similar):

# AWS Access Credentials (combined with "~/.aws/credentials" file)
export AWS_PROFILE="{{LOCAL_PROFILE_NAME_OR_USERNAME}}"  # For AWS SDK
export AWS_DEFAULT_PROFILE="${AWS_PROFILE}"              # For AWS CLI

# AWS SDK looks for a "~/.aws/credentials" file and is not configurable.
# AWS CLI looks for a "~/.aws/config" file but IS configurable:
export AWS_CONFIG_FILE="${HOME}/.aws/credentials"

For example, mine looks like:

# AWS Access Credentials (combined with "~/.aws/credentials" file)
export AWS_PROFILE="jgreene"                 # For AWS SDK
export AWS_DEFAULT_PROFILE="${AWS_PROFILE}"  # For AWS CLI

# AWS SDK looks for a "~/.aws/credentials" file and is not configurable.
# AWS CLI looks for a "~/.aws/config" file but IS configurable:
export AWS_CONFIG_FILE="${HOME}/.aws/credentials"

NOTE: As always, you will need to open a new terminal session or else run source ~/.bash_profile in order for these environment variables to take effect.