https://github.com/jeshan/cloudformation-checklist
The checklist for meticulous AWS DevOps engineers
https://github.com/jeshan/cloudformation-checklist
checklist cloudformation
Last synced: 5 months ago
JSON representation
The checklist for meticulous AWS DevOps engineers
- Host: GitHub
- URL: https://github.com/jeshan/cloudformation-checklist
- Owner: jeshan
- License: cc0-1.0
- Archived: true
- Created: 2019-07-04T15:32:09.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2022-02-11T11:05:13.000Z (about 3 years ago)
- Last Synced: 2024-08-09T02:16:02.366Z (8 months ago)
- Topics: checklist, cloudformation
- Language: JavaScript
- Homepage: https://cfnchecklist.com
- Size: 3.53 MB
- Stars: 72
- Watchers: 4
- Forks: 17
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
- jimsghstars - jeshan/cloudformation-checklist - The checklist for meticulous AWS DevOps engineers (JavaScript)
README
CloudFormation Checklist
The CloudFormation Checklist is a list of all elements you need to have / to test before launching your infra to production.
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][low_img] means that the item is **recommended** but can be omitted in some particular situations.
* ![Medium][medium_img] 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][high_img] 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](https://github.com/jeshan/cloudformation-checklist/blob/master/README_APP.md) 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!
➔ [](https://github.com/jeshan/cloudformation-checklist/)
```md
[](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](https://github.com/thedaviddias)**
Modified for AWS CloudFormation:
**[Jeshan G. BABOOA](https://github.com/jeshan)**
## Infrastructure
The website is a static one deployed on AWS. Contents are stored in Amazon S3 while CloudFront cdn is used to deliver the contents. This is how the stack is:
This is how the deployment pipeline has been set up:
*Images automatically generated with [cfnbuddy](https://www.cfnbuddy.com)*
## License
[](https://creativecommons.org/publicdomain/zero/1.0/)
[low_img]: https://front-end-checklist.now.sh/low.svg
[medium_img]: https://front-end-checklist.now.sh/medium.svg
[high_img]: https://front-end-checklist.now.sh/high.svg