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.
StaticWebsite resource takes two arguments for configuration,
ContentArgs is required, and configures the content being served.
pathToContent- A file path to the static content, relative from
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
targetDomain- the domain to serve the website on, e.g. "example.com" or "www.example.com". A DNS
Arecord will be created to point the target domain to the CloudFront distribution. If set, a
Route53hosed 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-1region and support
npm installnpm run buildnpm run lintnpm publish
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.