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

@miguelpazo/pulumi_aws_toolkit

v1.0.2

Published

Reusable Pulumi TypeScript modules for AWS: networking, compute, data, security, observability and multi-region failover.

Downloads

325

Readme

@miguelpazo/pulumi_aws_toolkit

A TypeScript library of reusable Pulumi modules for AWS infrastructure. It packages opinionated, production-oriented building blocks (networking, compute, data, security, observability, and multi-region failover) so they can be consumed from any Pulumi TypeScript project.

This library is intended to be used as a dependency — it is not a deployable Pulumi project on its own.

Requirements

  • Node.js >= 22.14.0
  • npm >= 10.9.2
  • A Pulumi TypeScript project that provides the following peer dependencies:
    • @pulumi/pulumi ^3.213.0
    • @pulumi/aws ^7.15.0
    • @pulumi/awsx ^3.1.0

Installation

npm install @miguelpazo/pulumi_aws_toolkit

Pulumi peer dependencies must already exist in the consuming project.

Quick Start

Initialize the global config once, then use any module or tool.

import * as aws from "@pulumi/aws";
import * as pulumi from "@pulumi/pulumi";
import {
    AwsUtilsInit,
    AwsUtilsModules,
    AwsUtilsTools,
    AwsUtilsCommon,
} from "@miguelpazo/pulumi_aws_toolkit";

const providerVirginia = new aws.Provider("provider-virginia", {region: "us-east-1"});

AwsUtilsInit.init({
    project: "myapp",
    stack: pulumi.getStack(),
    stackAlias: "dev",
    accountId: aws.getCallerIdentity().then(id => id.accountId),
    generalPrefix: "myapp-dev",
    generalPrefixShort: "myapp",
    generalPrefixShort2: "ma",
    generalTags: {Project: "myapp", Environment: "dev"},
    region: "us-east-1",
    providerVirginia,
    cloudwatchRetentionLogs: 30,
    deleteProtection: false,
});

// Use any module
const rds = await AwsUtilsModules.Rds.getInstance().main({
    // ...module-specific config
});

// Use any tool (Lambda-based utility)
const alarms = await AwsUtilsTools.LambdaAlarms.getInstance().main({
    // ...tool-specific config
});

providerVirginia is always required, even for non-us-east-1 stacks, because CloudFront and certain ACM operations must run in us-east-1.

Public API

The package exposes four named export groups plus all public types and enums.

AwsUtilsInit

  • init(config: InitConfig) — must be called before any module or tool is used.

AwsUtilsCommon

Static utility classes (not singletons):

  • General — Handlebars template rendering, zipping helpers, misc helpers.
  • UtilsInfra — DNS, ACM certificates, and security group helpers.

AwsUtilsModules

Singleton AWS service modules. Each exposes getInstance().main(config) returning a Promise.

| Category | Modules | |---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| | Networking | Alb, AlbListener, NlbListener, ApiGateway, ApiGatewayVpcLink, CloudFrontBackend, CloudFrontFrontend, CloudMap, Route53, VpcImport | | Compute | EcsCluster, EcsService, Ecr, LambdaRole, StepFunctionFailover | | Data | Rds, RdsAurora, RdsAuroraGlobal, RdsProxy, DynamoDb, ElastiCache, Efs, S3, S3Replica, Backup, ExportFinalBackup | | Security | Kms, Secrets, ParamStore, Ssm, SSMAssociations | | Observability | Alarms, AlarmsAdmin, AlarmsCIS, AlarmsGuardDuty, AlarmsInspector, AlarmsSecurityHub, CloudWatch | | Messaging | Sqs, Ses |

AwsUtilsTools

Self-contained Lambda deployers (IAM role + log group + function, bundled source):

  • LambdaAlarms — CloudWatch alarm notification router.
  • LambdaNotifications — generic event notifier.
  • LambdaRestart — scheduled ECS / cache restart utility.
  • LambdaExportBackup — AWS Backup export pipeline.
  • LambdaFailover — multi-region failover orchestration.
  • UserProwler — Prowler security scanner IAM user.

Architecture Highlights

  • Global config singleton. AwsUtilsInit.init() sets a project-wide InitConfig; every module retrieves it via getInit(). Call it once, before any module.
  • Singleton module pattern. Every module and tool is accessed through ModuleName.getInstance().main(config).
  • Naming conventions.
    • Pulumi logical names use ${project}-${service}-${resourceType}.
    • AWS physical names use ${generalPrefix}-${service}-${resourceType} (or generalPrefixShort for Lambda, generalPrefixShort2 when ALB/TG names exceed 32 chars).
    • Tags always include generalTags plus a Name tag matching the physical name.
  • Multi-region / failover. A single codebase supports both primary and replica stacks. When multiRegion and failoverReplica are both enabled, modules import existing replica resources instead of creating them.
  • Handlebars-templated policies. IAM policies, S3 replication rules, SSM documents, and parameter configs live in src/resources/ as Handlebars JSON templates, rendered via General.renderTemplate() with project/account/region context.

Build

npm run build   # compiles TypeScript to bin/

The package's main entry points at index.ts (source), so consumers compile against the TypeScript source directly. There are no test or lint scripts.

License

MIT © Miguel Pazo