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

@prairielearn/aws

v2.0.5

Published

This package contains utilities that help us correctly configure AWS SDK clients.

Downloads

98

Readme

@prairielearn/aws

This package contains utilities that help us correctly configure AWS SDK clients.

Specifically, it's meant to address the fact that clients from the v3 AWS SDK don't share resolved credentials with each other. This means that, by default, every time a new client is created, it has to independently resolve credentials for itself. In production, this is problematic, as that requires talking to the IMDS, which will throttle requests if we make a ton of them in rapid succession. This results in clients being unable to obtain credentials, and thus the AWS API operations fail.

We resolve this with this package, which helps ensure that all AWS SDk clients are constructed with a shared and memoized credential provider.

Usage

Create a config provider with makeAwsConfigProvider:

import { makeAwsConfigProvider } from '@prairielearn/aws';
import { fromNodeProviderChain } from '@aws-sdk/credential-providers';

const awsConfigProvider = makeAwsConfigProvider({
  credentials: fromNodeProviderChain(),
  getClientConfig: () => ({
    region: 'us-east-2',
  }),
});

export const makeAwsClientConfig = awsConfigProvider.makeAwsClientConfig;
export const makeS3ClientConfig = awsConfigProvider.makeS3ClientConfig;

Then, use the makeAwsClientConfig and makeS3ClientConfig functions to configure AWS clients:

import { EC2Client } from '@aws-sdk/client-ec2';
import { S3Client } from '@aws-sdk/client-s3';

const ec2 = new EC2Client(makeAwsClientConfig());
const s3 = new S3Client(makeS3ClientConfig());

Providing extra config

The get... functions support passing in extra config. If this extra config conflicts with other config, such as that returned from getClientConfig(), this extra config will take precedence.

const s3 = new S3Client(
  makeS3ClientConfig({
    maxAttempts: 3,
  }),
);

Customizing S3 config

The config for S3 clients can be customized independently to support pointing it to other S3-compatible stores.

For instance, to use s3rver when running in dev mode, you could use something like the following config:

const awsConfigProvider = makeAwsConfigProvider({
  credentials: fromNodeProviderChain(),
  getClientConfig: () => ({
    region: 'us-east-2',
  }),
  makeS3ClientConfig: () => {
    if (process.env.NODE_ENV !== 'production') {
      return {
        forcePathStyle: true,
        credentials: {
          accessKeyId: 'S3RVER',
          secretAccessKey: 'S3RVER',
        },
        endpoint: 'http://127.0.0.1:5000',
      };
    }

    return {};
  },
});