How minhlk/nuxt-s3-deployment works
Main Components
A. Frontend Layer:
• Nuxt.js Application (SSR/SSG)
• Components structure
• Vue layouts and pages
B. Infrastructure Layer:
• CloudFront Distribution
• S3 Bucket (Static hosting)
• API Gateway (planned)
• GitHub Actions (CI/CD)
• IAM/OIDC (Authentication)
[Client Tier]
• ↓ ↑
[Distribution Tier]
• ↓ ↑
[Storage/Compute Tier]
Specific Component Relationships
Users → CloudFront → S3 Bucket (static assets)
• → API Gateway (for /api routes)
Deployment Flow Section
GitHub Actions → OIDC → AWS → S3/CloudFront
Key Elements to Emphasize
a. Frontend Architecture:
• Nuxt.js application structure
• Separation between pages, components, and stores
• Server API endpoint (/server/api)
b. AWS Infrastructure:
• CloudFront distribution serving as the main entry point
• S3 bucket for static asset hosting
• Future Route53 integration (marked as planned)
• API Gateway integration (marked as planned)
c. DevOps Flow:
• GitHub Actions workflows for deployment
• OIDC authentication flow
• Environment-specific deployments (dev/prod)
Create distinct sections for:
Important Notes
• Environment indicators (dev/prod)
• Configuration references (cloudfront-s3.yml)
• Docker container boundary (Dockerfile present)
Technical Details
• Nuxt.js SSR/SSG configuration
• API endpoints structure
• S3 bucket configuration
• CloudFront distribution settings
• GitHub Actions workflow paths