How saulmen/conferenciaarchivos works
Project type and purpose
• This is an educational/documentation project for an AWS conference, covering how to use EC2, S3, IAM and React code examples.
• It contains static markdown guides (“capaGratuita”, “serviciosUtilizados”, “bonus”) and a sandbox React frontend under “ejemplo1” to demonstrate hands‑on AWS usage.
File structure
• Top‑level folders:
• bonus (extra tips on AWS certification discount)
• capaGratuita (how to obtain AWS free tier)
• serviciosUtilizados (detailed AWS service walkthroughs: EC2 & S3)
• ejemplo1 (React frontend demo + its own README)
• The React demo has standard React app layout: public/ and src/ directories, package.json, and static assets.
• There are no backend service directories, implying the project uses AWS managed services (no custom server code).
README for insights
• The README outlines session topics and links to each section.
Main components
a. Documentation Site
• Hosted as a static site (e.g., GitHub Pages, S3 + CloudFront)
• Contains markdown content (capaGratuita, serviciosUtilizados, bonus)
b. AWS Cloud Environment
• IAM Service (user, roles, policies)
• EC2 instance (compute)
• S3 bucket (storage for static assets or user uploads)
c. React Example Application (“ejemplo1/frontend”)
• Runs in the user’s browser
• Interacts directly with AWS services (EC2 via SSH/API? S3 via REST SDK)
d. Developer Workflow
• Local environment (npm install, npm run start/build)
• CI/CD pipeline or manual deploy to S3/Pages
Relationships & interactions
• The end user (conference attendee) uses the Documentation Site to follow steps.
• They provision resources in AWS (IAM → EC2 → S3).
• They clone/run the React demo locally or deploy it to the S3 bucket created.
• The React app sends GET/PUT requests to S3 and uses SSH/API to EC2 as part of the demo.
Architectural patterns & design principles
• Static‑first architecture: docs and demo assets are static, served via CDN/S3.
• Serverless/micro‑services mindset: no custom backend services—everything is AWS managed.
• Clear separation: Documentation layer vs. Demo layer vs. AWS resource layer.
Technologies & frameworks
• Markdown + Static site generator or direct GitHub Pages/S3
• React (create‑react‑app) for demo
• AWS services: IAM, EC2, S3
• (Optional) AWS CLI/SDK used in examples
Final advice
• Be thorough: capture every major folder or service as a component.
• “static docs vs. interactive demo vs. AWS resources.”
• Avoid over‑engineering: if there is no backend code, do not invent one—represent AWS managed services directly instead.