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

crowsnest-rules-aws

v0.0.1

Published

AWS rules for Crowsnest

Downloads

2

Readme

crowsnest-rules-aws

This repo will be made public and renamed to crowsnest.

Synopsis

The goal of Crowsnest is to make it easy to define and deploy AWS Lambda functions, as well as offer a base set of Lambda functions aimed at security and best practice monitoring.

How does it make it easy

  • Mechanism to quickly define CloudFormation templating for a Lambda function
  • Pass configuration to Lambda functions as CloudFormation parameters. Uses streambot
  • Define basic CloudWatch alarms
  • Define a base IAM role and let you add additional policy statements to it
  • Build a single CloudFormation template and deploy it with cfn-config

How to use

The workflow for using Crowsnest is:

  • Define functions in the ./rules directory, following the spec. below.
  • Use the build command to wrap these functions into a CloudFormation template
  • Upload the package / lambda functions to a designated S3 location
  • Deploy the CloudFormation template

Define functions

Rules are a .js file in ./rules which:

  • export a function which will be run on AWS Lambda. The function should be exported to module.exports.fn
    • first param is event
    • second param is callback
    • call callback in standard node.js style when the function is done (callback(err, message))
  • define configuration as an object, exported to module.exports.config
    • name string name of what you call your function.
    • parameters lets you pass configuration to the specific Lambda function. Theses parameters become parameters on the CloudFormation template, and environment variables within the Lambda function when it runs.
    • statements an array of IAM policy statements which will be added to the IAM role your Lambda function runs as.
    • eventRule an object which contains an eventPattern object
      • eventPattern an object which contains a CloudWatch Event Rule Event Pattern

See ./examples for an example config and fn.

Build the template

node build.js > myCfnTemplate.template

Upload the package

Create a .zip of the repo, exclude .git, and upload to the path formed by:

  • CodeS3Bucket + CodeS3Prefix + GitSha + .zip

Deploy as CloudFormation stack

Create rules

node rules.js will create CloudWatch Event Rules and lambda targets for each rule in ./rules, so long as that rule specifies an eventRule.eventPattern object

TODO

  • Make this README less cryptic / assume reader knows less / Mapboxisms