Aws Well Architected Labs

Hands on labs and code to help you learn, measure, and build using architectural best practices.
Alternatives To Aws Well Architected Labs
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Sops13,87910921 hours ago13May 09, 2022372mpl-2.0Go
Simple and flexible tool for managing secrets
18 hours ago47August 03, 202319apache-2.0Python
Prowler is an Open Source Security tool for AWS, Azure and GCP to perform Cloud Security best practices assessments, audits, incident response, compliance, continuous monitoring, hardening and forensics readiness. Includes CIS, NIST 800, NIST CSF, CISA, FedRAMP, PCI-DSS, GDPR, HIPAA, FFIEC, SOC2, GXP, Well-Architected Security, ENS and more.
My Arsenal Of Aws Security Tools8,304
2 months ago1apache-2.0Shell
List of open source tools for AWS security: defensive, offensive, auditing, DFIR, etc.
Devops Resources7,566
2 months ago14Groovy
DevOps resources - Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP
Tfsec6,27516a day ago405October 25, 202212mitGo
Security scanner for your Terraform code
4 days ago45September 05, 2022188gpl-2.0Python
Multi-Cloud Security Auditing Tool
a month ago204bsd-3-clauseJavaScript
CloudMapper helps you analyze your Amazon Web Services (AWS) environments.
Steampipe5,581317 hours ago495July 31, 2023104agpl-3.0Go
Use SQL to instantly query your cloud services (AWS, Azure, GCP and more). Open source CLI. No DB required.
8 days ago4mit
Ultimate DevSecOps library
3 years ago1June 15, 201585apache-2.0Python
Security Monkey monitors AWS, GCP, OpenStack, and GitHub orgs for assets and their changes over time.
Alternatives To Aws Well Architected Labs
Select To Compare

Alternative Project Comparisons

AWS Well-Architected Labs


The Well-Architected framework has been developed to help cloud architects build the most secure, high-performing, resilient, and efficient infrastructure possible for their applications. This framework provides a consistent approach for customers and partners to evaluate architectures, and provides guidance to help implement designs that will scale with your application needs over time.

This repository contains documentation and code in the format of hands-on labs to help you learn, measure, and build using architectural best practices. The labs are categorized into levels, where 100 is introductory, 200/300 is intermediate and 400 is advanced.

Lab Website

To run these AWS Well-Architected Labs, please go to:

The labs cannot be run from GitHub. Please continue to use GitHub to log issues or make pull requests. To run the labs please use


The labs are structured around the six pillars of the Well-Architected Framework:


Licensed under the Apache 2.0 and MITnoAttr License.

Copyright 2018-2019, Inc. or its affiliates. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at

or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Deploy notes for Hugo based site

Cloudformation Deployment into Amplify

You can deploy the site using deployment/walabs.yaml file. This file will deploy the site using AWS Amplify.

Post-CloudFormation Deployment

Once the site has been deployed, you must run the first build in the console. To do this, go to Amplify, select the App name, then click on "Run Build". All builds after this point will be continuous based on commits to the master branch.

WA Labs Amplify Configuration Information

Rewrite rules for migration from old mkdocs labs site:

Included in the CloudFormation deployment is a set of re-write rules to facilitate the migration from mkdocs to Hugo. These will automatically redirect to the new path based locations for each lab.

Utilizing existing CloudFront distribution

Because we needed an additional layer in front of the Amplify deployed Hugo site, we had to disable the L2_CACHE in Amplify. This allows for a secondary CloudFront distribution to be placed in front of the Amplify site (which you will use as the Origin for the CloudFront distribution).

CloudFront Distribution

Because we had an existing CloudFront distribution, the creation of setup of this was not included in the CloudFormation deployment.

How to run locally

On a Mac:

  1. brew install hugo
  2. in the repo's main directory, run: hugo serve -D
  3. You should get a localhost:port to connect and see changes live.

How I built the base site:

The instructions below is how I built the skeleton site.

On Mac:

  1. brew install hugo
  2. hugo new site walabs (or hugo new site walabs --force if you are in an existing git repo)
  3. cd walabs
  4. git init
  5. git submodule add themes/learn
  6. modify config.tomal
  7. Until gets resolved, I have implemented the fix in these 2 files:
    1. layouts/partials/menu.html
    2. static/css/theme-walabs.css
Popular Amazon Web Services Projects
Popular Security Projects
Popular Cloud Computing Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.