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

snssqs-msgbus

v1.0.6

Published

SNS and SQS message bus + queue

Downloads

10

Readme

SNSSQS-MSGBUS

A message bus using AWS SNS Topics and SQS Queues


Install

npm

$ npm install snssqs-msgbus

yarn

$ yarn add snssqs-msgbus

Usage

This lib provides two classes, MessageBus and MessageQueue. MessageBus will send command messages (AWS SNS), while MessageQueue will gather messages from a queue (AWS SQS).

Both MessageBus and MessageQueue will retrieve credentials from the Default credentials chain.


MessageBus

Send messages to services through SNS Topic.

import { createMessageBus, getMessageBus } from 'snssqs-msgbus';
// Provide the region ans SNS ARN
const msgBus = createMessageBus(process.env.AWS_REGION, process.env.AWS_SNS_ARN);

// the MessageBus instance can be reached from msgBus and also from
// getMessageBus(), which will return the previously created MessageBus instance.

// ...

// Somewhere in your code
const commandData = { whatheverContent: 1, someValue: 'this string' };

getMessageBus().sendCommand('PascalCasedCommandName', JSON.stringify(commandData));

// This will send a SNS message with Attribute command=PascalCasedCommandName and MessageBody=commandData

MessageQueue

Receive commands and data from a SQS Queue.

import { createMessageQueue, getMessageQueue } from 'snssqs-msgbus';

// Create the MesssageQueue instance
createMessageQueue(process.env.AWS_REGION);

// Create a subscription to a Queue.
// First arg is for logging purposes only
// Then provide Queue URL and callback. If callback is async, it will be awaited.
getMessageQueue().addSubscription('MyCommandName', process.env.MY_CMD_QUEUE_URL, (messageId, messageBody) => {
  console.log(`Received a message with MessageId:${messageId} and body: ${messageBody}`);
});

// To start polling queues invoke run()
getMessageQueue().run();

// It can be stopped also with getMessageQueue().stop();

AWS Setup:

  1. Create SNS Topic_X

  2. Create a SQS Queue_Y

  3. On SNS Topic_X:

  • Add subscription with Queue_Y's ARN

  • Select Enable raw message delivery (it MUST BE SELECTED !)

  • On subscription filter policy add this (which commands will enter the queue)

{
  "command": [
    "CommandName"
  ]
}

Where "CommandName" is the identifier to route an operation notification to certain queue. (command is a sns notification attribute, not a field on message body)

  1. On SQS Queues > Queue_Y
  • Select Access Policy, and edit with the following Policy
{
  "Version": "2012-10-17",
  "Id": "Policy1598555915018",
  "Statement": [
    {
      "Sid": "Stmt1598555833567",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "sqs:SendMessage",
      "Resource": "<QUEUE_Y_ARN>",
      "Condition": {
        "StringEquals": {
          "aws:SourceArn": "<TOPIC_X_ARN>"
        }
      }
    },
    {
      "Sid": "Stmt1598555909987",
      "Effect": "Allow",
      "Principal": "*",
      "Action": [
        "sqs:ChangeMessageVisibility",
        "sqs:DeleteMessage",
        "sqs:GetQueueAttributes",
        "sqs:GetQueueUrl",
        "sqs:ReceiveMessage"
      ],
      "Resource": "<QUEUE_Y_ARN>"
    }
  ]
}
  • The first statement allows SNS to send messages to the queue, and restricts sending messages only be from this SNS topic.
  • The second defines who can receive messages from the Queue. (Adjust principal as needed to control access)

(Without the first Statement messages will NOT arrive to the queue)