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

read-through-s3-decrypting-memory-cache

v2.0.1

Published

Read-through in-memory cache for AWS S3 objects that are reasonable to cache in memory and need to be decrypted using AWS KMS

Downloads

15

Readme

read-through-s3-decrypting-memory-cache

Stability: 1 - Experimental

NPM version

Read-through in-memory cache for AWS S3 objects that are reasonable to cache in memory and need to be decrypted using AWS KMS.

Contributors

@tristanls

Contents

Overview

This module offers a read-through in-memory cache for small objects that are stored in S3 and need to be decrypted using KMS. It assumes it is running in an environment where aws-sdk has access to its standard credentials chain with s3:GetObject permission to the configured S3 Bucket, kms:decrypt permission. Further, this module assumes appropriate AWS KMS key policies or grants allow decryption invocations to succeed.

Installation

npm install read-through-s3-decrypting-memory-cache

Tests

npm test

Usage

const Cache = require("read-through-s3-decrypting-memory-cache");
const cache = new Cache(
{
    bucket: "name-of-my-s3-bucket",
    encryptionContext: {
        some: "encryption context"
    },
    region: "us-east-1"
});
cache.get("myKey", (error, value) =>
{
    console.log(error, value);
});

const initialCache = new Map();
initialCache.set("myKey", Buffer.from("myValue"));
const cache2 = new Cache(
{
    bucket: "name-of-my-other-s3-bucket",
    encryptionContext: {
        some: "encryption context"
    },
    initialCache,
    region: "us-east-1"
});
cache2.get("myKey", (error, value) =>
{
    console.log(error, value);
});

Documentation

Cache

Public API

Cache.S3_NOT_FOUND_CODES

  • ["AccessDenied", "NoSuchKey"]

Default S3 error codes to treat as "not found" (AccessDenied can occur if the object does not exist but the caller has no s3:ListBucket permission).

new Cache(config)

  • config: Object Cache configuration.
    • bucket: String Name of S3 bucket to retrieve values from.
    • credentials: AWS.Credentials (Default: undefined) AWS credentials to use with S3 and KMS. If not provided, the default credential provider chain will be used.
    • encryptionContext: Object Encryption context to extend when attempting KMS decryption.
    • initialCache: Map (Default: undefined) Initial cached values to use.
    • region: String AWS region to configure KMS with for decryption.
    • stderrTelemetry: Boolean (Default: false) If true, telemetry will be emitted to stderr.

Creates a new Cache.

cache.get(key, callback, [context])

  • key: String S3 Key to retrieve from cache.
  • callback: Function function(error, value){}
    • error: Error Error, if any.
    • value: Buffer S3 Object, if it exists, undefined otherwise.
  • context: Object Optional context.
    • parentSpan: TraceTelemetryEvents.Span Parent span to use to trace execution.

Retrieves the cached value from memory. If not found in memory, attempts to retrieve the value from S3. If not found in S3, caches undefined locally, otherwise, decrypts using KMS. If decryption fails, caches undefined locally, otherwise caches the platinext value locally.

The EncryptionContext used in KMS.decrypt() operation is the configured encryptionContext with addition of keyId field that equals the value of key. For example, cache.get("foo", callback) will add keyId: "foo" to the configured encryptionContext when attempting decryption.

Releases

Current releases.

Policy

We follow the semantic versioning policy (semver.org) with a caveat:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.

caveat: Major version zero is a special case indicating development version that may make incompatible API changes without incrementing MAJOR version.