Cloud Internship 2026
Chapter 7
Activity Presentations
Every activity ends with a short individual presentation. The capstone presentation is more detailed.
7.1 Standard Activity Presentation Format (10 min)
| Section | Time | What to cover |
|---|---|---|
| Output demo | 3 min | Show the running resources in the AWS Console or the terraform apply output. Show the successful destroy. |
| Technical approach | 3 min | Walk through your key Terraform or CloudFormation code. Explain your design decisions. |
| Challenges | 2 min | What went wrong. How you found the cause. What you learned. |
| Learnings | 2 min | What clicked this week. What you would do differently next time. |
7.2 Capstone Presentation Format (20 min)
| Section | Time | What to cover |
|---|---|---|
| Architecture overview | 5 min | Walk through your architecture diagram. Explain all components and why you made key design decisions. |
| Terraform code walkthrough | 7 min | Show your module structure. Walk through one complete module. Show variables, outputs, and the root module call. |
| Deployment and testing | 4 min | Show the ALB DNS working. Jump host SSH working. RDS reachable from jump host. terraform destroy confirmed. |
| Blockers and learnings | 4 min | What was hardest. What you debugged. What you are taking away from the internship. |
7.3 Pre-Presentation Checklist
- All Terraform code is committed to GitLab with a clean history
- terraform plan shows no unexpected changes
- Architecture diagram is complete and committed to docs/
- README explains how to deploy and destroy the infrastructure
- All testing notes are written up
- Resources are NOT destroyed before the presentation โ you need them for the demo
- You can explain every resource and every Terraform block in your code
- terraform destroy confirmed and resources cleaned up AFTER the presentation