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

static-website-aws

v1.0.10

Published

Pulumi package for hosting a static website on AWS.

Downloads

20

Readme

Static Website using AWS

Pulumi package for hosting a static website on AWS infrastructure. Under the hood, the package uses AWS S3, CloudFront, and optionally Route53.

Usage:

import * as staticWebsite from "static-website-aws";

const contentArgs: staticWebsite.ContentArgs = {
    pathToContent: "./www",
    custom404Path: "/www/404.html",
};

const domainArgs: staticWebsite.DomainArgs = {
    targetDomain: "blog.chrsmith.io",
    acmCertificateArn: "arn:aws:acm:us-east-1:...",
};

const website = new staticWebsite.StaticWebsite("blog", contentArgs, domainArgs);

Configuration

The StaticWebsite resource takes two arguments for configuration, ContentArgs and DomainArgs.

ContentArgs is required, and configures the content being served.

  • pathToContent - A file path to the static content, relative from Pulumi.yaml.
  • custom404Page (optional) - Path to the resource to return when serving a 404. Relative to pathToContent, must be under pathToContent. If not set, 404 errors will be the default one served from S3 (which isn't especially friendly).

DomainArgs is optional set of arguments to create a Route53 domain record to serve the website. If you want to serve the website over a custom domain or serve it using HTTPS, you should specify DomainArgs.

  • targetDomain - the domain to serve the website on, e.g. "example.com" or "www.example.com". A DNS A record will be created to point the target domain to the CloudFront distribution. If set, a Route53 hosed zone for the root domain must already exist. (e.g. "example.com" must already be managed by Route53 in the same AWS account you are running the Pulumi program in.)
  • acmCertificateArn - The ARN of the Amazon Certificate Manager cert to use for HTTPS traffic to the CloudFront distribution. Must be in the us-east-1 region and support targetDomain.

Building

npm install
npm run build
npm run lint
npm publish

Architecture

For details of how the AWS products are used to serve static content, you can read about how the code is structured on the Pulumi blog. This package is based on the aws-ts-static-website example in the pulumi/examples repo.