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

@crowi/plugin-aws

v0.1.0-alpha.0

Published

AWS base configuration for Crowi 2.0 — shared region / accessKeyId / secretAccessKey for downstream AWS service plugins (S3, SES, ...).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

sotaroksotarok

Keywords

Readme

@crowi/plugin-aws

Shared AWS credentials base plugin. Holds region / accessKeyId / secretAccessKey once, so any number of AWS-using plugins (@crowi/plugin-storage-aws-s3, future @crowi/plugin-mail-aws-ses, etc) can read the same configuration without operators duplicating it.

This plugin does not register any driver on its own — it's a config-holder. It auto-loads when any AWS plugin lists it under requires, so operators do not need to add it to crowi.config.json:plugins themselves.

Configure

Open /admin/plugins, select @crowi/plugin-aws, and fill in:

| Field | Required? | Notes | |---|---|---| | region | Recommended | e.g. ap-northeast-1, us-east-1. Validated against the <area>-<sub>-<num> shape. Empty string falls back to the SDK default region resolution. | | accessKeyId | Optional | Long-lived IAM access key. Leave blank to use the SDK's default credential chain (see below). | | secretAccessKey | Optional | Pairs with accessKeyId. Encrypted at rest with CROWI_ENCRYPTION_KEY. |

When to leave the keys blank

Both accessKeyId and secretAccessKey empty → the AWS SDK falls back to its default credential provider chain, in this order:

  1. Environment variables (AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_SESSION_TOKEN)
  2. Shared credentials file (~/.aws/credentials)
  3. EC2 / ECS / EKS instance / task / pod identity
  4. Other SDK-managed sources (SSO, web identity, etc.)

For production on AWS, leave the keys blank and use an IAM role. You get short-lived credentials rotated by AWS without operators ever holding a long-lived secret.

What this plugin does NOT do

  • Does not register a storage / search / auth / notifier driver. Its only job is to publish a typed config to dependent plugins via ctx.dependencyConfig<AwsConfig>('@crowi/plugin-aws').
  • Does not pre-validate credentials. A bad key shows up at the first AWS API call from the dependent plugin (e.g. an S3 PutObject), not at boot.
  • Does not configure per-service knobs (S3 bucket, SES verified identity, etc). Those live in the consuming plugin's own config.

See also