Skip to content

Latest commit

 

History

History
69 lines (42 loc) · 3.79 KB

README.md

File metadata and controls

69 lines (42 loc) · 3.79 KB

Static Website Stack

The Static Website stack creates a static site hosted on AWS Simple Storage Service, served throught the help of AWS Cloudfront and shipped with CI/CD powered by AWS Codepipeline.

Getting Started

The stack differs from the one shown below just in the use of Github as source instead of Codecommit. Back in the history you should be able to find also a working commit with a codecommit git repository instead. I have a plan to provide this choice throught an environment variable that can be used to set up a paramenter for the stack. Right now [01/06/2019] this parameter is not implemented yet. Everything else remains untouched.

architecture_schema

A blog post is available here.

To use the stack / modify it, just clone the repository and move to the templates/static-website folder starting from the root of the repository, like this:

git clone https://github.com/made2591/immutable.templates
cd immutable.templates/templates/static-website
# start deploy (see later)

Architecture overview

The user just git commit and git push the changes. Every time this happens, a Cloudwatch event (2) triggers the CodePipeline execution (3): this pipeline is composed of three stages. It first gets the source code from the repository (4) defined in CodeCommit/Github and puts it inside the artifact bucket (5); then, the build stage gets (6) the source code and starts the jekylls build - using a ruby docker image managed by aws - and puts the artifacts back in the bucket (in another prefix). Finally, it copies the artifacts to the content bucket. After that, a lambda is triggered (9) to invalidate the CloudFront cache: CloudFront starts cache invalidation (10) by retrieving (11) and propagating the new content from the content bucket again to the edge location. Every time a user B makes an https request to the domain, Route53 resolves (13) the request the CloudFront CDN, that uses the certificate manager (14) to operate in SSL, and stores logs (15) about the requests done by the users.

Prerequisites

The only needed tool is Node.js - ≥ 8.11.x - and the AWS Cloud Development Kit - AWS CDK. You can install it by running

$ npm i -g aws-cdk

Deployment of Stack

Just as any other CDK stack, this are the main commands that can help you with the most common actions:

  • npm run build compile typescript to js
  • npm run watch watch for changes and compile
  • cdk deploy deploy this stack to your default AWS account/region
  • cdk diff compare deployed stack with current state
  • cdk synth emits the synthesized CloudFormation template

Built With

Contributing

Please read CONTRIBUTING.md for details on how to contact me.

Authors

Almost all the stacks proposed in this repository, and their implementation, are deeply discussed between people below:

Thank you for your interest!

License

This project is licensed under the MIT License - see the LICENSE.md file for details.

Acknowledgments

  • Fix architecture schemas
  • Inspiration
  • etc