Package Health Score

81 / 100

security
No known security issues
popularity
Small
maintenance
Healthy
community
Active

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
3.0.0	\|	11/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.2.6	\|	04/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.2.5	\|	03/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.8.0	\|	02/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.7.0	\|	08/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (4,585)

GitHub Stars: 297
Forks: 205
Contributors: 20

Direct Usage Popularity

The npm package aws-kcl receives a total of 4,585 downloads a week. As such, we scored aws-kcl popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package aws-kcl, we found that it has been starred 297 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: No
Code of Conduct: Yes
Contributors: 20
Funding: No

With more than 10 contributors for the aws-kcl repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 41
Open PR: 27
Last Release: 2 months ago
Last Commit: 17 days ago

Further analysis of the maintenance status of aws-kcl based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that aws-kcl demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >= 0.8.0

Age: 10 years
Dependencies: 2 Direct
Versions: 13
Install Size: 87.4 kB
Dist-tags: 1
# of Files: 16
Maintainers: 1
TS Typings: Yes

aws-kcl has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Amazon Kinesis Client Library for Node.js

This package provides an interface to the Amazon Kinesis Client Library (KCL) MultiLangDaemon for the Node.js framework.

Developers can use the KCL to build distributed applications that process streaming data reliably at scale. The KCL takes care of many of the complex tasks associated with distributed computing, such as load-balancing across multiple instances, responding to instance failures, checkpointing processed records, and reacting to changes in stream volume.

This package wraps and manages the interaction with the MultiLangDaemon, which is provided as part of the Amazon KCL for Java so that developers can focus on implementing their record processing logic.

A record processor in Node.js typically looks like the following:

var kcl = require('aws-kcl');
var util = require('util');

/**
 * The record processor must provide three functions:
 *
 * * `initialize` - called once
 * * `processRecords` - called zero or more times
 * * `shutdown` - called if this KCL instance loses the lease to this shard
 *
 * Notes:
 * * All of the above functions take additional callback arguments. When one is
 * done initializing, processing records, or shutting down, callback must be
 * called (i.e., `completeCallback()`) in order to let the KCL know that the
 * associated operation is complete. Without the invocation of the callback
 * function, the KCL will not proceed further.
 * * The application will terminate if any error is thrown from any of the
 * record processor functions. Hence, if you would like to continue processing
 * on exception scenarios, exceptions should be handled appropriately in
 * record processor functions and should not be passed to the KCL library. The
 * callback must also be invoked in this case to let the KCL know that it can
 * proceed further.
 */
var recordProcessor = {
  /**
   * Called once by the KCL before any calls to processRecords. Any initialization
   * logic for record processing can go here.
   *
   * @param {object} initializeInput - Initialization related information.
   *             Looks like - {"shardId":""}
   * @param {callback} completeCallback - The callback that must be invoked
   *        once the initialization operation is complete.
   */
  initialize: function(initializeInput, completeCallback) {
    // Initialization logic ...

    completeCallback();
  },

  /**
   * Called by KCL with a list of records to be processed and checkpointed.
   * A record looks like:
   *     {"data":"","partitionKey":"someKey","sequenceNumber":"1234567890"}
   *
   * The checkpointer can optionally be used to checkpoint a particular sequence
   * number (from a record). If checkpointing, the checkpoint must always be
   * invoked before calling `completeCallback` for processRecords. Moreover,
   * `completeCallback` should only be invoked once the checkpoint operation
   * callback is received.
   *
   * @param {object} processRecordsInput - Process records information with
   *             array of records that are to be processed. Looks like -
   *             {"records":[, ], "checkpointer":}
   *             where  format is specified above.
   * @param {callback} completeCallback - The callback that must be invoked
   *             once all records are processed and checkpoint (optional) is
   *             complete.
   */
  processRecords: function(processRecordsInput, completeCallback) {
    if (!processRecordsInput || !processRecordsInput.records) {
      // Must call completeCallback to proceed further.
      completeCallback();
      return;
    }

    var records = processRecordsInput.records;
    var record, sequenceNumber, partitionKey, data;
    for (var i = 0 ; i &lt; records.length ; ++i) {
      record = records[i];
      sequenceNumber = record.sequenceNumber;
      partitionKey = record.partitionKey;
      // Note that "data" is a base64-encoded string. Buffer can be used to
      // decode the data into a string.
      data = new Buffer(record.data, 'base64').toString();

      // Custom record processing logic ...
    }
    if (!sequenceNumber) {
      // Must call completeCallback to proceed further.
      completeCallback();
      return;
    }
    // If checkpointing, only call completeCallback once checkpoint operation
    // is complete.
    processRecordsInput.checkpointer.checkpoint(sequenceNumber,
      function(err, checkpointedSequenceNumber) {
        // In this example, regardless of error, we mark processRecords
        // complete to proceed further with more records.
        completeCallback();
      }
    );
  },

  /**
  * Called by the KCL to indicate that this record processor should shut down.
  * After the lease lost operation is complete, there will not be any more calls to
  * any other functions of this record processor. Clients should not attempt to
  * checkpoint because the lease has been lost by this Worker.
  * 
  * @param {object} leaseLostInput - Lease lost information.
  * @param {callback} completeCallback - The callback must be invoked once lease
  *               lost operations are completed.
  */
  leaseLost: function(leaseLostInput, completeCallback) {
    // Lease lost logic ...
    completeCallback();
  },

  /**
  * Called by the KCL to indicate that this record processor should shutdown.
  * After the shard ended operation is complete, there will not be any more calls to
  * any other functions of this record processor. Clients are required to checkpoint
  * at this time. This indicates that the current record processor has finished
  * processing and new record processors for the children will be created.
  * 
  * @param {object} shardEndedInput - ShardEnded information. Looks like -
  *               {"checkpointer": }
  * @param {callback} completeCallback - The callback must be invoked once shard
  *               ended operations are completed.
  */
  shardEnded: function(shardEndedInput, completeCallback) {
    // Shard end logic ...
    
    // Since you are checkpointing, only call completeCallback once the checkpoint
    // operation is complete.
    shardEndedInput.checkpointer.checkpoint(function(err) {
      // In this example, regardless of the error, we mark the shutdown operation
      // complete.
      completeCallback();
    });
    completeCallback();
  }
};

kcl(recordProcessor).run();

Before You Get Started

Prerequisite

Before you begin, Node.js and NPM must be installed on your system. For download instructions for your platform, see https://nodejs.org/download/.

To get the sample KCL application and bootstrap script, you need git.

Amazon KCL for Node.js uses MultiLangDaemon provided by Amazon KCL for Java. You also need Java version 1.8 or higher installed.

Setting Up the Environment

Before running the samples, make sure that your environment is configured to allow the samples to use your AWS Security Credentials, which are used by MultiLangDaemon to interact with AWS services.

By default, the MultiLangDaemon uses the DefaultCredentialsProvider, so make your credentials available to one of the credentials providers in that provider chain. There are several ways to do this. You can provide credentials through a ~/.aws/credentials file or through environment variables (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY). If you're running on Amazon EC2, you can associate an IAM role with your instance with appropriate access.

For more information about Amazon Kinesis and the client libraries, see the Amazon Kinesis documentation as well as the Amazon Kinesis forums.

Running the Sample

The Amazon KCL for Node.js repository contains source code for the KCL, a sample data producer and data consumer (processor) application, and the bootstrap script.

To run sample applications, you need to get all required NPM modules. From the root of the repository, execute the following command:

npm install

This downloads all dependencies for running the bootstrap script as well as the sample application.

The sample application consists of two components:

A data producer (samples/basic_sample/producer/sample_kinesis_producer_app.js): this script creates an Amazon Kinesis stream and starts putting 10 random records into it.
A data processor (samples/basic_sample/consumer/sample_kcl_app.js): this script is invoked by the MultiLangDaemon, consumes the data from the Amazon Kinesis stream, and stores received data into files (1 file per shard).

The following defaults are used in the sample application:

Stream name: kclnodejssample
Number of shards: 2
Amazon KCL application name: kclnodejssample
Amazon DynamoDB table for Amazon KCL application: kclnodejssample

Running the Data Producer

To run the data producer, execute the following commands from the root of the repository:

    cd samples/basic_sample/producer
    node sample_kinesis_producer_app.js

Notes

The script samples/basic_sample/producer/sample_kinesis_producer_app.js takes several parameters that you can use to customize its behavior. To change default parameters, change values in the file samples/basic_sample/producer/config.js.

Running the Data Processor

To start the data processor, run the following command from the root of the repository:

    cd samples/basic_sample/consumer
    ../../../bin/kcl-bootstrap --java /usr/bin/java -e -p ./sample.properties

Notes

The Amazon KCL for Node.js uses stdin/stdout to interact with MultiLangDaemon. Do not point your application logs to stdout/stderr. If your logs point to stdout/stderr, log output gets mingled with MultiLangDaemon, which makes it really difficult to find consumer-specific log events. This consumer uses a logging library to redirect all application logs to a file called application.log. Make sure to follow a similar pattern while developing consumer applications with the Amazon KCL for Node.js. For more information about the protocol between the MultiLangDaemon and the Amazon KCL for Node.js, go to MultiLangDaemon.
The bootstrap script downloads MultiLangDaemon and its dependencies.
The bootstrap script invokes the MultiLangDaemon, which starts the Node.js consumer application as its child process. By default:
- The file samples/basic_sample/consumer/sample.properties controls which Amazon KCL for Node.js application is run. You can specify your own properties file with the -p or --properties argument.
- The bootstrap script uses JAVA_HOME to locate the java binary. To specify your own java home path, use the -j or --java argument when invoking the bootstrap script.
To only print commands on the console to run the KCL application without actually running the KCL application, leave out the -e or --execute argument to the bootstrap script.
You can also add REPOSITORY_ROOT/bin to your PATH so you can access kcl-bootstrap from anywhere.
To find out all the options you can override when running the bootstrap script, run the following command:

    kcl-bootstrap --help

Cleaning Up

This sample application creates an Amazon Kinesis stream, sends data to it, and creates a DynamoDB table to track the KCL application state. This will incur nominal costs to your AWS account, and continue to do so even when the sample app is finished. To stop being charged, delete these resources. Specifically, the sample application creates following AWS resources:

An Amazon Kinesis stream named kclnodejssample
An Amazon DynamoDB table named kclnodejssample

You can delete these using the AWS Management Console.

Running on Amazon EC2

Log into an Amazon EC2 instance running Amazon Linux, then perform the following steps to prepare your environment for running the sample application. Note the version of Java that ships with Amazon Linux can be found at /usr/bin/java and should be 1.8 or greater.

    # install node.js, npm and git
    sudo yum install nodejs npm --enablerepo=epel
    sudo yum install git
    # clone the git repository to work with the samples
    git clone https://github.com/awslabs/amazon-kinesis-client-nodejs.git kclnodejs
    cd kclnodejs/samples/basic_sample/producer/
    # download dependencies
    npm install
    # run the sample producer
    node sample_kinesis_producer_app.js &amp;

    # ...and in another terminal, run the sample consumer
    export PATH=$PATH:kclnodejs/bin
    cd kclnodejs/samples/basic_sample/consumer/
    kcl-bootstrap --java /usr/bin/java -e -p ./sample.properties &gt; consumer.out 2&gt;&amp;1 &amp;

NPM module

To get the Amazon KCL for Node.js module from NPM, use the following command:

  npm install aws-kcl

Under the Hood: Supplemental information about the MultiLangDaemon

Amazon KCL for Node.js uses Amazon KCL for Java internally. We have implemented a Java-based daemon, called the MultiLangDaemon that does all the heavy lifting. The daemon launches the user-defined record processor script/program as a sub-process, and then communicates with this sub-process over standard input/output using a simple protocol. This allows support for any language. This approach enables the Amazon KCL to be language-agnostic, while providing identical features and similar parallel processing model across all languages.

At runtime, there will always be a one-to-one correspondence between a record processor, a child process, and an Amazon Kinesis shard. The MultiLangDaemon ensures that, without any developer intervention.

In this release, we have abstracted these implementation details away and exposed an interface that enables you to focus on writing record processing logic in Node.js.

Release Notes

Release 3.0.0 (November 6, 2024)

New lease assignment / load balancing algorithm
- KCL 3.x introduces a new lease assignment and load balancing algorithm. It assigns leases among workers based on worker utilization metrics and throughput on each lease, replacing the previous lease count-based lease assignment algorithm.
- When KCL detects higher variance in CPU utilization among workers, it proactively reassigns leases from over-utilized workers to under-utilized workers for even load balancing. This ensures even CPU utilization across workers and removes the need to over-provision the stream processing compute hosts.
Optimized DynamoDB RCU usage
- KCL 3.x optimizes DynamoDB read capacity unit (RCU) usage on the lease table by implementing a global secondary index with leaseOwner as the partition key. This index mirrors the leaseKey attribute from the base lease table, allowing workers to efficiently discover their assigned leases by querying the index instead of scanning the entire table.
- This approach significantly reduces read operations compared to earlier KCL versions, where workers performed full table scans, resulting in higher RCU consumption.
Graceful lease handoff
- KCL 3.x introduces a feature called "graceful lease handoff" to minimize data reprocessing during lease reassignments. Graceful lease handoff allows the current worker to complete checkpointing of processed records before transferring the lease to another worker. For graceful lease handoff, you should implement checkpointing logic within the existing shutdownRequested() method.
- This feature is enabled by default in KCL 3.x, but you can turn off this feature by adjusting the configuration property isGracefulLeaseHandoffEnabled.
- While this approach significantly reduces the probability of data reprocessing during lease transfers, it doesn't completely eliminate the possibility. To maintain data integrity and consistency, it's crucial to design your downstream consumer applications to be idempotent. This ensures that the application can handle potential duplicate record processing without adverse effects.
New DynamoDB metadata management artifacts
- KCL 3.x introduces two new DynamoDB tables for improved lease management:
  - Worker metrics table: Records CPU utilization metrics from each worker. KCL uses these metrics for optimal lease assignments, balancing resource utilization across workers. If CPU utilization metric is not available, KCL assigns leases to balance the total sum of shard throughput per worker instead.
  - Coordinator state table: Stores internal state information for workers. Used to coordinate in-place migration from KCL 2.x to KCL 3.x and leader election among workers.
- Follow this documentation to add required IAM permissions for your KCL application.
Other improvements and changes
- Dependency on the AWS SDK for Java 1.x has been fully removed.
  - The Glue Schema Registry integration functionality no longer depends on AWS SDK for Java 1.x. Previously, it required this as a transient dependency.
  - Multilangdaemon has been upgraded to use AWS SDK for Java 2.x. It no longer depends on AWS SDK for Java 1.x.
- idleTimeBetweenReadsInMillis (PollingConfig) now has a minimum default value of 200.
  - This polling configuration property determines the publishers wait time between GetRecords calls in both success and failure cases. Previously, setting this value below 200 caused unnecessary throttling. This is because Amazon Kinesis Data Streams supports up to five read transactions per second per shard for shared-throughput consumers.
- Shard lifecycle management is improved to deal with edge cases around shard splits and merges to ensure records continue being processed as expected.
Migration
- The programming interfaces of KCL 3.x remain identical with KCL 2.x for an easier migration. For detailed migration instructions, please refer to the Migrate consumers from KCL 2.x to KCL 3.x page in the Amazon Kinesis Data Streams developer guide.
Configuration properties
- New configuration properties introduced in KCL 3.x are listed in this doc.
- Deprecated configuration properties in KCL 3.x are listed in this doc. You need to keep the deprecated configuration properties during the migration from any previous KCL version to KCL 3.x.
Metrics
- New CloudWatch metrics introduced in KCL 3.x are explained in the Monitor the Kinesis Client Library with Amazon CloudWatch in the Amazon Kinesis Data Streams developer guide. The following operations are newly added in KCL 3.x:
  - LeaseAssignmentManager
  - WorkerMetricStatsReporter
  - LeaseDiscovery

Release 2.2.6 (April 25, 2024)

PR #327 Upgraded amazon-kinesis-client from 2.5.5 to 2.5.8
PR #329 Upgraded aws-sdk from 2.1562.0 to 2.1603.0
PR #95 Upgraded jcommander from 1.72 to 1.82
PR #271 Upgraded org.codehaus.mojo:animal-sniffer-annotations from 1.20 to 1.23
PR #266 Upgraded com.amazonaws:aws-java-sdk-core from 1.12.370 to 1.12.512
PR #313 Upgraded logback.version from 1.3.12 to 1.5.3
PR #305 Upgraded org.slf4j:slf4j-api from 2.0.5 to 2.0.12
PR #325 Upgraded mocha from 9.2.2 to 10.4.0
PR #307 Upgraded com.google.protobuf:protobuf-java from 3.21.7 to 3.25.3
PR #262 Upgraded checker-qual from 2.5.2 to 3.36.0
PR #303 Upgraded commander from 8.3.0 to 12.0.0
PR #287 Upgraded sinon from 14.0.2 to 17.0.1
PR #318 Upgraded awssdk.version from 2.20.43 to 2.25.11
PR #319 Upgraded org.reactivestreams:reactive-streams from 1.0.3 to 1.0.4
PR #320 Upgraded netty-reactive.version from 2.0.6 to 2.0.12
PR #330 Upgraded io.netty:netty-codec-http from 4.1.100.Final to 4.1.108.Final
PR #331 Upgraded ion-java from 1.5.1 to 1.11.4
PR #211 Upgraded fasterxml-jackson.version from 2.13.4 to 2.14.1

Release 2.2.5 (February 29, 2024)

PR #309 Updated amazon-kinesis-client and amazon-kinesis-client multilang from 2.5.4 to 2.5.5 and updated awssdk.version to match amazon-kinesis-client from 2.19.2 to 2.20.43

Release 2.2.4 (January 16, 2024)

PR #298 Added dependency on aws-sdk arns
PR #293 Updated logback-classic to 1.3.12

Release 2.2.3 (December 18, 2023)

PR #291 Updated KCL and KCL multilang to the latest version 2.5.4
PR #284 Updated netty to 4.1.100.Final, fasterxml-jackson to 2.13.5, and guava to 32.1.1-jre
PR #277 Updated com.google.protobuf:protobuf-java from 3.21.5 to 3.21.7

Release 2.2.2 (January 4, 2023)

PR #207 Add endpoints-spi dependency

Release 2.2.1 (January 3, 2023)

PR #202 Keep Java dependencies in sync with the KCL V2.4.4
- Updated dependencies to match the v2.4.4 KCL Java release
- Updated slfj to resolve the logger's incompatibility problem

Release 2.2.0 (September 15, 2022)

PR #165 Update Java dependencies
- KCL and KCL-multilang are updated to the latest version 2.4.3

Release 2.1.0 (January 31, 2020)

Milestone #4

Fixing bootstrap to use HTTPS
- PR #75
Adding support for Win32 platform
- PR #67
Relicensing to Apache-2.0
- PR #69

Release 2.0.0 (March 6, 2019)

Added support for Enhanced Fan-Out.
Enhanced Fan-Out provides dedicated throughput per stream consumer, and uses an HTTP/2 push API (SubscribeToShard) to deliver records with lower latency.
Updated the Amazon Kinesis Client Library for Java to version 2.1.2.
- Version 2.1.2 uses 4 additional Kinesis API's
  WARNING: These additional API's may require updating any explicit IAM policies
- For more information about Enhanced Fan-Out with the Amazon Kinesis Client Library please see the announcement and developer documentation.
Added support for the newer methods to the KCLManager.
While the original shutdown method will continue to work it's recommended to upgrade to the newer interface.
- The shutdown has been replaced by leaseLost and shardEnded.
- Added the leaseLost method which is invoked when a lease is lost.
  leaseLost replaces shutdown where shutdownInput.reason was ZOMBIE.
- Added the shardEnded method which is invoked when all records from a split or merge have been processed.
  shardEnded replaces shutdown where shutdownInput.reason was TERMINATE.
Updated the AWS Java SDK version to 2.4.0
MultiLangDaemon now provides logging using Logback.
- MultiLangDaemon supports custom configurations for logging via a Logback XML configuration file.
- The kcl-bootstrap program was been updated to accept either -l or --log-configuration to provide a Logback XML configuration file.

Release 0.8.0 (February 12, 2019)

Updated the dependency on Amazon Kinesis Client for Java to 1.9.3
- This adds support for ListShards API. This API is used in place of DescribeStream API to provide more throughput during ShardSyncTask. Please consult the AWS Documentation for ListShards for more information.
  - ListShards supports higher call rate, which should reduce instances of throttling when attempting to synchronize the shard list.
  - WARNING: ListShards is a new API, and may require updating any explicit IAM policies
- PR #59
Changed to now download jars from Maven using https.
- PR #59

Release 0.7.0 (August 2, 2017)

Updated the dependency on Amazon Kinesis Client for Java to 1.8.1.
This adds support for setting a timeout when dispatching records to the node.js record processor. If the record processor doesn't respond in the given time the Java processor is terminated. The timeout for the this can be set by adding timeoutInSeconds = . The default for this is no timeout.
Setting this can cause the KCL to exit suddenly, before using this ensure that you have an automated restart for your application
Updating minimum requirement for the JDK version to 8
- Amazon Kinesis Client Issue #185
- PR #41
Added support to handle graceful shutdown requests.
- PR #39
- Issue #34

Release 0.6.0 (December 12, 2016)

Updated the dependency on Amazon Kinesis Client for Java to 1.7.2.
- PR #23
- PR #24

Release 0.5.0 (March 26, 2015)

The aws-kcl npm module allows implementation of record processors in Node.js using the Amazon KCL MultiLangDaemon.
The samples directory contains a sample producer and processing applications using the Amazon KCL for Node.js.

License

This library is licensed under the Apache 2.0 License.

aws-kcl dependencies

commander xml-js

aws-kcl development dependencies

async aws-sdk chai grunt grunt-cli grunt-contrib-clean grunt-contrib-jshint grunt-jsdoc grunt-mocha-test ink-docstrap log4js mocha sinon

FAQs

What is aws-kcl?

Kinesis Client Libray (KCL) in Node.js. Visit Snyk Advisor to see a full health score report for aws-kcl, including popularity, security, maintenance & community analysis.

Is aws-kcl popular?

The npm package aws-kcl receives a total of 4,585 weekly downloads. As such, aws-kcl popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is aws-kcl well maintained?

We found that aws-kcl demonstrated a healthy version release cadence and project activity. It has a community of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is aws-kcl safe to use?

The npm package aws-kcl was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 22 December-2024, at 08:54 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (4,585)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Amazon Kinesis Client Library for Node.js

Before You Get Started

Prerequisite

Setting Up the Environment

Running the Sample

Running the Data Producer

Notes

Running the Data Processor

Notes

Cleaning Up

Running on Amazon EC2

NPM module

Under the Hood: Supplemental information about the MultiLangDaemon

See Also

Release Notes

Release 3.0.0 (November 6, 2024)

Release 2.2.6 (April 25, 2024)

Release 2.2.5 (February 29, 2024)

Release 2.2.4 (January 16, 2024)

Release 2.2.3 (December 18, 2023)

Release 2.2.2 (January 4, 2023)

Release 2.2.1 (January 3, 2023)

Release 2.2.0 (September 15, 2022)

Release 2.1.0 (January 31, 2020)

Release 2.0.0 (March 6, 2019)

Release 0.8.0 (February 12, 2019)

Release 0.7.0 (August 2, 2017)

Release 0.6.0 (December 12, 2016)

Release 0.5.0 (March 26, 2015)

License

aws-kcl dependencies

aws-kcl development dependencies

FAQs

What is aws-kcl?

Is aws-kcl popular?

Is aws-kcl well maintained?

Is aws-kcl safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues