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

@pharmaspectra/dynamodb-stream-elasticsearch

v4.0.1

Published

Missing blueprint for AWS Lambda. Reads stream from AWS DynamoDB and writes it to AWS ElasticSearch.

Downloads

50

Readme

js-standard-style Build Status

             _                                   _  _     
          __| | _  _  _ _   __ _  _ __   ___  __| || |__  
         / _` || || || ' \ / _` || '  \ / _ \/ _` || '_ \
         \__,_| \_, ||_||_|\__,_||_|_|_|\___/\__,_||_.__/
                |__/  _                                                     
                  ___| |_  _ _  ___  __ _  _ __  
                 (_-<|  _|| '_|/ -_)/ _` || '  \ 
                 /__/ \__||_|  \___|\__,_||_|_|_|
           _            _    _                              _    
      ___ | | __ _  ___| |_ (_) __  ___ ___  __ _  _ _  __ | |_  
     / -_)| |/ _` |(_-<|  _|| |/ _|(_-</ -_)/ _` || '_|/ _|| ' \ 
     \___||_|\__,_|/__/ \__||_|\__|/__/\___|\__,_||_|  \__||_||_|
                                                             
                                                                            

DynamoDB --> Stream --> Elasticsearch

The missing blueprint for AWS Lambda, which reads stream from AWS DynamoDB and writes it to Elasticsearch.

Whenever data is changed (modified, removed or inserted) in DynamoDB one can use AWS Lambda function to capture this change and update Elasticsearch machine immediately. Further reading:

Indexing Amazon DynamoDB Content with Amazon Elasticsearch Service Using AWS Lambda

Getting Started

Install:

npm i dynamodb-stream-elasticsearch 

Use it in your lambda:

const { pushStream } = require('dynamodb-stream-elasticsearch');

const { ES_ENDPOINT, INDEX } = process.env;

function myHandler(event, context, callback) {
  console.log('Received event:', JSON.stringify(event, null, 2));
  pushStream({ event, endpoint: ES_ENDPOINT, index: INDEX })
    .then(() => {
      callback(null, `Successfully processed ${event.Records.length} records.`);
    })
    .catch((e) => {
      callback(`Error ${e}`, null);
    });
}

exports.handler = myHandler;

Upload Lambda to AWS and star this repository if it works as expected!!

Parameters

| Param | Description | Required | ------------- | ------------- | ------------- | | event | Event object generated by the stream (pass it as it is and don't modify) | required | endpoint | Exact url of Elasticsearch instance (it works with AWS ES and standard ES) (string) | required | index | The name of Elasticsearch index (string). If not provided will set the same as DynamoDB table name | optional | refresh | Force Elasticsearch refresh its index immediately more here (boolean). Default: true | optional | useBulk | Enables bulk upserts and removals (boolean). Default: false | optional | transformFunction | A function/promise to transform each record before sending them to ES. Applies to INSERT and UPDATE operations. If transformFunction returns an empty object or false the row will be skipped. This function will receive body (NewImage), oldBody (OldImage) and (record) as the whole record as arguments. | optional | elasticSearchOptions | Additional set of arguments passed to elasticsearch Client see here | optional

Running the tests

Setup elastic node

Docker can be used to host a node of Elasticsearch

To run tests locally you need to have an Elasticsearch Docker container running. Simply type:

docker-compose up -d 

Running tests

Tests are written using Mocha [https://mochajs.org/]. Tests can be launched using:

npm test

If you modify src/utils/aws-es-connection you will have to setup localstack on your local machine

You will need to:

  • start localstack locally with docker
  • install localstack via pip
  • configure a new elastic-search domain (and wait for it to be available)
  • run the tests
docker-compose up -d
pip install awscli-local
aws --endpoint-url http://localhost:4566 es create-elasticsearch-domain --domain-name domain-test
AWS_ES_ENDPOINT=http://localhost:4571 npm test-aws 

One Note: there seem to be problems running localstack on macs M1, to check if the cluster has been created run: awslocal es describe-elasticsearch-domain --domain-name domain-test | grep Created

Contributing

If you want to commit changes, make sure if follow these rules:

  1. All code changes should go with a proper integration test;
  2. Code should follow Javascript Standard Guideline;
  3. Commit messages should be set according to this article.

TODO

  • Introduce Continuous Integration;
  • Add Elasticsearch bulk operation instead of index for multiple records

Authors & Contributors

License

This project is licensed under the MIT License - see the LICENSE.md file for details

Donate

If you find this project to be useful and you would like to support the author for maintaining it, you might consider to make any donation under this link:

Donate via Paypal

Release notes:

Compatible with node 8.10. (If for some reason you want to use it with node 6.10, then use 1.0.0 of this module)

Third version doesn't support types as they were deprecated in ES 7.0.