How devopsbuddies2/certified-aws-solutions-architect-associate works
Project Type and Purpose
• This repository is a static documentation website for AWS Solutions Architect Associate exam notes.
• It uses Markdown files (organized into numbered folders by topic) and a Jekyll-like configuration (_config.yml) to generate a navigable site.
File Structure Analysis
• Top-level folders “1-aws-fundamentals” through “6-whitepapers” each contain .md files grouping AWS topics.
• README.md provides an overview and links to each markdown page.
• _config.yml suggests a static-site generator (e.g., Jekyll) controlling site metadata, theme, plugins.
Key Components
a. Content Source
• Markdown files (.md) organized by topic.
• README.md as entry point / landing page.
• _config.yml for site settings.
b. Version Control & CI/CD
• Git repository on GitHub (or similar).
• CI pipeline (e.g., GitHub Actions, Travis CI) triggered on pushes to main.
• Build step: static-site generator runs, reads .md + config, outputs HTML/CSS/JS into a _site folder.
c. Hosting & Delivery
• Static assets deployed to a hosting service:
• GitHub Pages or
• AWS S3 bucket + CloudFront CDN
• DNS resolution via Route 53 or GitHub custom domain settings.
d. End Users
• Browser clients fetch HTML/CSS/JS from CDN edge locations.
Relationships and Data Flow
1. Developer commits content changes to GitHub.
2. CI/CD builds site with Jekyll (or chosen static generator).
3. Built artifacts are deployed to hosting: S3/CloudFront or GitHub Pages.
4. DNS (Route 53 or GitHub pages) directs user requests to the CDN or Pages IP.
5. Users retrieve static pages instantly from the nearest edge.
Architectural Patterns and Principles
• Content-Service Separation: content (Markdown) decoupled from rendering engine and hosting.
• Infrastructure as Code: _config.yml + any CI scripts codify build/deploy steps.
• High Availability & Performance: use of CDN (CloudFront) to cache static assets globally.
• Versioned Deployments: Git tags/branches can map to staging vs production sites.
c. CI step: Jekyll build → produces _site/ (HTML/CSS/JS).
• Option A: GitHub Pages (branch-to-pages)
f. Right-most: End User Browser requests content; response flows back via CDN edge.