Integrate all 10 projects into a unified, production-ready cloud solution. Demonstrate end-to-end cloud engineering competency through a comprehensive technical report, live demonstration, and professional presentation — your final evidence of cloud computing mastery.
FormatTechnical Demo + Report + Presentation
CoversAll 10 Projects Integrated
Duration7–10 Days (Final preparation)
Weighting40% of Final Module Grade
OutcomeCloud Engineering Portfolio Project
1. What You've Built — 10 Projects at a Glance
Before beginning the capstone, take time to appreciate the complete cloud engineering stack you've assembled across 10 projects. This is not a simplified demo — these are the actual tools, technologies, and practices used in professional cloud engineering roles today.
The capstone integrates all components into a coherent architecture narrative. Each layer builds on the previous — this is what a real-world cloud environment looks like when assembled with engineering discipline.
3. Capstone Deliverables and Tasks
TASK ATechnical Integration — Verify Full Stack is Operational
Before writing the report or preparing the presentation, ensure all components are working together as an integrated system. Document any issues and their resolutions — this troubleshooting documentation is itself a deliverable.
Run the full stack: Start all services (web, database, monitoring, AI runbooks) using either Docker Compose or Kubernetes manifests and verify each is healthy.
End-to-end test: Open the website, interact with it, verify the database connection works, and confirm data is persisted across container restarts.
Verify backups: Manually trigger a backup from Project 5, confirm the backup file is created and encrypted, and perform a test restore to a separate database.
Security audit: Run the security-audit.sh script from Project 6, review the output, and document all findings.
IAM verification: Log in as each user (webdev, dbadmin, devops, auditor) and verify the sudo permissions — confirm both allowed and denied operations work correctly.
AI Ops assistant run: Test run the AI-based runbook grounded search for system failures to make sure recommended resolutions are printed immediately.
Monitoring check: Open Grafana, verify all dashboards show data, and document what metrics are being collected.
Load test: Run load triggers against your endpoints and watch metrics spike in Grafana — screenshot this.
The technical report is the primary written artifact of the capstone. It must be professionally formatted and demonstrate deep understanding — not just descriptions of what you did, but analysis of WHY and WHAT the outcomes were. This document could be shared as a portfolio piece with potential employers.
TECHNICAL REPORT STRUCTURE — ABC RETAIL CLOUD MIGRATION
COVER PAGE
Title: "ABC Retail Pvt Ltd — Complete Cloud Migration: Technical Report"
Student Name, Roll Number, Course Name, Date
Word Count, Version Number
EXECUTIVE SUMMARY (1 page)
→ Written for a non-technical reader (CEO level)
→ What was the business problem? What was the solution?
→ What were the outcomes? (3–5 bullet points of results)
→ Total estimated cost savings from cloud migration (from P07 analysis)
SECTION 1: MIGRATION STRATEGY (P01)
→ As-is vs. To-be architecture comparison
→ Migration methodology used (Lift-and-Shift? Re-platform?)
→ Risk register summary table (top 5 risks + mitigations)
→ Success criteria and how they were met
SECTION 2: INFRASTRUCTURE DESIGN (P02 + P04)
→ Network topology diagram (from P04)
→ VirtualBox environment details (CPU, RAM, disk)
→ Firewall rules summary table
→ Load balancer configuration and health check results
SECTION 3: CONTAINERIZATION (P03)
→ Dockerfile explanation (each instruction justified)
→ Docker Compose architecture diagram
→ Results: container startup time, image size, resource usage
SECTION 4: DATA PLATFORM (P05)
→ Database schema (tables, relationships)
→ Backup schedule and verification results
→ DRP test results: did you achieve RTO/RPO targets?
→ MinIO bucket configuration and access policy
SECTION 5: SECURITY IMPLEMENTATION (P06)
→ IAM table (users, groups, permissions)
→ Security hardening checklist (completed)
→ Vault architecture and secrets stored
→ Audit log analysis: what was captured?
SECTION 6: MULTI-CLOUD STRATEGY (P07)
→ Provider comparison table (your researched figures)
→ Workload distribution decision rationale
→ Cost optimization analysis and projected savings
→ Cloud Governance Framework summary
SECTION 7: INFRASTRUCTURE AS CODE (P08)
→ Terraform resource graph (output of terraform graph)
→ Ansible playbook flow diagram
→ Before/after: manual vs. IaC deployment time comparison
→ Git commit history analysis
SECTION 8: KUBERNETES (P09)
→ K8s deployment architecture diagram
→ Resource manifest inventory (what resources were deployed)
→ Rolling update demonstration with screenshots
→ HPA scaling behavior: when did it trigger?
SECTION 9: AI OPERATIONS & FINOPS (P10)
→ Prometheus scrape targets table & alert metrics
→ Grafana dashboard screenshots (3 minimum)
→ RAG pipeline architecture & vector search scripts
→ Cost Optimization audit reports & waste savings list
SECTION 10: REFLECTION AND LEARNINGS
→ What were the 3 biggest technical challenges and how were they solved?
→ What would you do differently if starting over?
→ How does this project compare to professional cloud deployments?
→ Which project was most valuable for your learning and why?
APPENDICES
→ A: Complete Terraform configuration (main.tf)
→ B: Ansible playbook (setup-webserver.yml)
→ C: Complete Kubernetes manifests
→ D: AI operations assistant python code
→ E: Cloud Governance Framework (full document from P07)
→ F: Security audit report output
💡 Writing Quality Tip
Every section should answer three questions: (1) What was the business need or technical problem? (2) What specific implementation choice did you make and why? (3) What was the measured or observed outcome? Reports that only describe "what I did" score much lower than those that explain rationale and results.
The live demonstration proves the system is real and working — not just documented. Prepare a structured 15-minute walkthrough with clear transitions between layers. Practice at least 3 times before the actual presentation.
PRESENTATION SCRIPT — 15 MINUTES
[0:00 – 1:00] OPENING: Business Context
"ABC Retail was running everything on a single physical server with
no backup, no security, and no scalability. Here is what we built
to transform their IT infrastructure into a modern cloud-native system."
[1:00 – 3:00] ARCHITECTURE OVERVIEW (Slide — the integrated diagram)
→ Walk through the complete architecture diagram
→ Explain each layer in one sentence
→ "This diagram represents 10 projects of work — here is how each
connects to the next..."
[3:00 – 6:00] LIVE DEMO: Running System
→ Terminal: kubectl get all -n abc-retail (K8s pods running)
→ Browser: Open http://abc-retail.local (website works)
→ Browser: Open Grafana — show SLA dashboard
→ Terminal: Show Prometheus targets are UP
→ "The system is live and being actively monitored."
[6:00 – 8:00] LIVE DEMO: Security & AI
→ Terminal: sudo su - auditor; sudo systemctl restart nginx (denied!)
→ Terminal: Run ai_ops_assistant.py and query live runbooks
→ Terminal: Run finops_audit.py to show waste audit logs
→ "Security is implemented at every layer, combined with grounded AI assistance."
[8:00 – 10:00] LIVE DEMO: Infrastructure Automation
→ Terraform configurations showing Docker networks and containers
→ Ansible playbooks configuring security settings
→ "All deployments are version-controlled and reproducible."
[10:00 – 12:00] LIVE DEMO: Resilience
→ Terminal: Scale web pods down and watch auto-recovery
→ K8s: show rolling update and undo rollback commands
→ "The system detects and recovers from failures automatically."
[12:00 – 14:00] OUTCOMES AND BUSINESS VALUE
→ Slide: "Before vs. After" table
→ Show cost comparison (from P07 research)
→ Show SLA improvement (single server → 99.99% K8s SLA)
→ Show security before (none) vs. after (full IAM + encryption)
[14:00 – 15:00] CONCLUSION + Q&A INVITATION
→ "ABC Retail now has enterprise-grade cloud infrastructure that can
scale with the business, survive failures automatically, and meet
regulatory requirements for data protection."
→ "I'm happy to dive deeper into any component — what questions
do you have?"
📌 Before/After Business Value Slide
Your most impactful slide is a simple table comparing the state of ABC Retail's IT before and after the migration. Include: availability (0 redundancy → 99.99%), recovery time (hours of downtime → RTO 4 hours), deployment time (manual days → automation minutes), security (none → full IAM + encryption), monitoring (none → real-time Grafana), and monthly costs (estimated). This slide is what non-technical evaluators understand best.
4. Assessment Grading Rubric
Assessment Component
Weight
Excellent (90–100%)
Good (75–89%)
Satisfactory (60–74%)
Technical Implementation All 10 projects working
35%
All components operational, integrated, and demonstrated live with no errors
8+ of 10 projects working, minor issues documented with resolution attempts
6+ projects working, some components demonstrated only in screenshots
Technical Report 15–20 pages
30%
Every section has rationale, outcomes, and professional diagrams. Appendices complete.
All sections present, some sections lacking depth or measurement. Good diagrams.
Most sections present, descriptive rather than analytical. Basic diagrams.
Live Presentation 15 minutes
20%
Confident delivery, clear architecture narrative, smooth live demos, responds well to questions
Good delivery, all demo sections shown, some hesitation on deep questions
Reads from notes, demos mostly work, struggles with unexpected questions
Understanding & Q&A Questions from evaluator
15%
Can explain WHY each technology was chosen and what the alternatives were. Connects to real cloud services.
Understands implementation but struggles with design alternatives or cloud service mapping
Understands what was done but cannot explain why or relate to cloud equivalents
5. Final Submission Checklist
Technical Files
All .html project guides (Projects 1–10)
terraform/main.tf + variables.tf + *.tfvars
ansible/setup-webserver.yml + inventory
k8s/*.yaml (all K8s manifests)
ai_ops_assistant.py + finops_audit.py
monitoring/prometheus.yml + alert_rules.yml
/usr/local/bin/abc-retail-backup.sh
/etc/sudoers.d/abc-retail
Git repository (github.com link)
Documents
Technical Report (PDF, 15–20 pages)
Cloud Governance Framework (Word/PDF)
Migration Planning Document (P01)
Security Design Document (P06)
Disaster Recovery Plan (P05)
IAM Design Table
Cloud Pricing Comparison Table
Security Audit Report
Presentation Evidence
Slide deck (PowerPoint or PDF, 10–15 slides)
Screenshot: K8s pods running
Screenshot: Grafana dashboards
Screenshot: cost optimization logs
Screenshot: AI RAG agent responses
Screenshot: Vault secrets stored
Screenshot: Security audit script output
Screenshot: Website accessible in browser
🎓 Cloud Engineering Competency Achieved
Completing Projects 1–10 and this Capstone demonstrates hands-on experience with the full spectrum of cloud engineering — from architecture planning and security hardening to container orchestration, infrastructure automation, and production monitoring. These are the exact skills that cloud engineering, DevOps, and cloud security roles require.