How skulltech/aws-solutions-architect-associate-notes works
Project type and purpose
• This “project” is a single-file Markdown repository containing AWS Solutions Architect Associate exam notes (README.md).
• Purpose: serve as a reference/knowledge base for AWS services and best practices.
File structure
• Top level only:
• README.md
• No source code, no frontend/backend code, no tests.
• This is a documentation-only repository.
README for additional insights
• The README is organized as a series of AWS service topics (Route53, S3, Lambda, VPC, etc.)
• No build instructions, no code snippets, purely reference content.
• Main components:
a. Version control repository (GitHub / Bitbucket / GitLab)
b. Continuous integration / continuous deployment (CI/CD) process (e.g., GitHub Actions, CircleCI)
c. Static site generator or Markdown‐to‐HTML converter (optional)
d. Static hosting (e.g., Amazon S3 bucket hosting a static site)
e. CDN / Distribution layer (e.g., Amazon CloudFront)
f. DNS layer (e.g., Amazon Route 53)
g. End user’s browser
• Relationships & interactions:
1. Developer pushes updates to README.md → trigger CI/CD
2. CI/CD pulls the Markdown file → runs static site generator (if used) → outputs HTML/CSS/JS
3. CI/CD deploys built assets to S3 bucket
4. CloudFront distribution pulls content from S3 (origin)
5. Route 53 directs end-user requests (e.g., docs.example.com) to the CloudFront distribution
6. End user fetches content from CloudFront → browser renders documentation
• Architectural patterns / design principles:
• Infrastructure as Code (script your CI/CD and S3/CloudFront setup)
• Immutable deployments (deploy a new version of static assets on each change)
• Cache‐first delivery (CloudFront caches assets globally)
• Least privilege IAM (grant CI/CD only the permissions to upload to S3 and invalidate CloudFront)
• Key technologies / frameworks:
• GitHub (or equivalent Git hosting)
• GitHub Actions (or other CI/CD)
• Static site generator (optional: Hugo, MkDocs, Jekyll)
• AWS S3 (static website hosting)
• AWS CloudFront (CDN)
• AWS Route 53 (DNS)
Detail & essential elements
• IAM roles/policies as a side component if desired
• Caching/invalidation step in CloudFront
• Relevant AWS nodes even if optional (e.g., Lambda@Edge for custom logic)