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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@node-in-layers/aws

v2.0.0

Published

A Node In Layers Package for handling AWS.

Downloads

48

Readme

AWS - A Node In Layers Package for AWS services

This package has a number of apps that assist with using AWS.

How to Install

npm install @node-in-layers/aws

Core

The core domain provides the ability to get a configured AWS 3 client based on your configs.

import { CoreNamespace } from '@node-in-layers/core/index.js'
import { AwsNamespace, AwsService } from '@node-in-layers/aws/types.js'

// Add the aws core app so context.services[AwsNamespace.root].aws3 is available
const core = {
  apps: [import('@node-in-layers/aws/index.js')],
  layerOrder: ['services', 'features'],
}

// Optional: limit services or pass AWS client options (Aws3PartialConfig)
const awsConfig = {
  [AwsNamespace.root]: {
    services: [AwsService.s3, AwsService.ssm, AwsService.secretsManager],
    awsClientProps: { region: 'us-east-1' },
  },
}

// In a layer, use the configured client from context
// const { s3, ssm, secretsManager } = context.services[AwsNamespace.root].aws3

Config

Provides a Secret Service for the @node-in-layers/secrets package. This creates the ability for configurations to have paths for parameter store and secrets manager, that are then populated at runtime.

How To Use

Setup With @node-in-layers/secrets

This package can be used as the secretServiceFactory for @node-in-layers/secrets.

Example system config:

import { CoreNamespace } from '@node-in-layers/core'
import {
  config as secretsConfig,
  SecretsNamespace,
} from '@node-in-layers/secrets'
import { secretsService, AwsNamespace, AwsService } from '@node-in-layers/aws'

export default async () => ({
  systemName: 'my-example-system',
  environment: 'dev',

  // Used by the AWS secrets adapter to create AWS SDK clients
  [AwsNamespace.root]: {
    awsClientProps: { region: 'us-east-1' },
    services: [AwsService.secretsManager, AwsService.ssm],
  },

  [CoreNamespace.root]: {
    apps: [
      secretsConfig,
      // your domains...
    ],
    layerOrder: ['services', 'features', 'express'],
  },

  [SecretsNamespace.Core]: {
    secretServiceFactory: secretsService,
  },

  // Example configurations, to be replaced
  myApp: {
    myClient: {
      key: {
        type: 'nil-secret',
        //awsService: "secretsManager", // don't need to put this, but can be helpful for making explicit.
        format: 'string',
        key: '/path/with-in/secrets-manager',
      },
    },
    aDynamicAwsPath: {
      type: 'nil-secret',
      awsService: 'parameterStore',
      format: 'string',
      key: '/path/with-in/parameter-store',
    },
  },
})