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.
| Note |
|---|
| To run these AWS Well-Architected Labs, please go to: |
| https://wellarchitectedlabs.com/ |
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 https://wellarchitectedlabs.com/
The labs are structured around the five pillars of the Well-Architected Framework:
- Operational Excellence
- Security
- Reliability
- Performance Efficiency
- Cost Optimization
- Well-Architected Tool
Licensed under the Apache 2.0 and MITnoAttr License.
Copyright 2018-2019 Amazon.com, 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
https://aws.amazon.com/apache2.0/
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.
You can deploy the site using deployment/walabs.yaml file. This file will deploy the site using AWS Amplify.
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.
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.
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).
Because we had an existing CloudFront distribution, the creation of setup of this was not included in the CloudFormation deployment.
- brew install hugo
- in the repo's main directory, run:
hugo serve -D - You should get a localhost:port to connect and see changes live.
The instructions below is how I built the skeleton site.
- brew install hugo
- hugo new site walabs (or hugo new site walabs --force if you are in an existing git repo)
- cd walabs
- git init
- git submodule add https://github.com/matcornic/hugo-theme-learn.git themes/learn
- modify config.tomal
- Until matcornic/hugo-theme-learn#355 gets resolved, I have implemented the fix in these 2 files:
- layouts/partials/menu.html
- static/css/theme-walabs.css