Skip to content
The checklist for meticulous AWS DevOps engineers
JavaScript CSS HTML Dockerfile
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github edit project files from mainstream Jul 7, 2019
config/main add deployment pipeline Jul 7, 2019
data rm newline Jul 11, 2019
src check in attr before counting Aug 8, 2019
templates add permission to invalidate cache Jul 7, 2019
test Remove draft mocha tests Nov 15, 2017
.babelrc 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
.editorconfig 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
.eslintrc.js 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
.gitignore Add tmp gitignore Nov 20, 2017
.nvmrc regenerate package-lock to fix native node crash (#294) Oct 12, 2018
.prettierrc 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
.stylelintrc Update npm stylelint corrections Mar 11, 2018
CHANGELOG.md 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
Dockerfile support docker for dev and build Jul 7, 2019
LICENSE Changing MIT to CC0 Nov 15, 2017
README.md link to sister project Jul 11, 2019
README_APP.md edit project files from mainstream Jul 7, 2019
ROADMAP.md 🌟First commit Front-End Checklist App 🌟 Nov 15, 2017
docker-compose.yml support docker for dev and build Jul 7, 2019
gulpfile.babel.js rm reference to domain from upstream Aug 8, 2019
modernizr-config.json
package-lock.json update package files for cfn Jul 7, 2019
package.json update package files for cfn Jul 7, 2019
wallaby.js New files for translation Nov 23, 2017
webpack.config.js Update all NPM packages and correct issues related to new modules Jul 17, 2018

README.md


  CloudFormation Checklist

The CloudFormation Checklist is a list of all elements you need to have / to test before launching your infra to production.

  How To UseContributing

Sister project: Lambda Checklist
  🎮 Lambda Checklist

Inspired by the Front-end Checklist
  🎮 Front-End Checklist

Table of Contents

See https://cfnchecklist.com


How to use?

All items in the CloudFormation Checklist are required for the majority of the projects, but some elements can be omitted or are not essential (in the case of an administration web app, you may not need RSS feed for example). We choose to use 3 levels of flexibility:

  • Low means that the item is recommended but can be omitted in some particular situations.
  • Medium means that the item is highly recommended and can eventually be omitted in some really particular cases. Omitting these that engineers may not work at full speed.
  • High means that the item can't be omitted by any reason. You may risk security issues in your infra. The testing priority needs to be on these elements first.

Some resources possess an emoticon to help you understand which type of content / help you may find on the checklist:

  • 📖: documentation or article
  • 🛠: online tool / testing tool
  • 📹: media or video content

You can contribute to the CloudFormation Checklist App reading the README_APP file which explains everything about the project.

CloudFormation Checklist Badge

If you want to show you are following the rules of the CloudFormation Checklist, put this badge on your README file!

CloudFormation_Checklist followed

[![CloudFormation_Checklist followed](https://img.shields.io/badge/Front‑End_Checklist-followed-brightgreen.svg)](https://github.com/jeshan/cloudformation-checklist/)

Contributing

Open an issue or a pull request to suggest changes or additions.

Authors

Original checklist application author: David Dias

Modified for AWS CloudFormation: Jeshan G. BABOOA

License

CC0

You can’t perform that action at this time.