Week 9 ‐ 14.04.2025 ‐ 20.04.2025 - Campus-Castolo/m300 GitHub Wiki

Week 9 – 14.04.2025 ‐ 20.04.2025

✅ Week 9 - Task List

Task Description Notes Status Start Date Completion Date Hours Needed
Confirm SNS Notifications for Alarms Test and verify SNS integration for CloudWatch alerts Verified with email and logs 14.04.2025 14.04.2025 1 Hrs
Add ECR Lifecycle Policy Automatically clean up old images from ECR Keep 3 recent images + delete untagged 14.04.2025 14.04.2025 1.5 Hrs
Add RDS Snapshot Cleanup Automation Prevent excessive snapshot accumulation Keep recent backups only 14.04.2025 14.04.2025 1.5 Hrs
Complete System Documentation Markdown-based documentation of entire infrastructure stack Includes all modules, diagrams & final remarks 14.04.2025 16.04.2025 3 Hrs
Finalize Entire Project Final review, polish, decommission resources Project officially completed on Wednesday 14.04.2025 16.04.2025 0.5 Hrs

📅 Daily Log – 14.04.2025

Task Description Notes Status Start Date Completion Date Hours Needed
SNS Alert + Email Notification Connected CloudWatch Alarms to SNS with email alerting Confirmed working alert with test alarm 14.04.2025 14.04.2025 1 Hrs
ECR Lifecycle Policy Created cleanup rules to manage Docker image retention Applied to m300 repo, tested via image push 14.04.2025 14.04.2025 1.5 Hrs
RDS Snapshot Cleanup Lambda Extended backup Lambda to delete older snapshots Ensures no long-term storage bloat 14.04.2025 14.04.2025 1.5 Hrs
Documentation Kick-off Started documenting the system in Markdown Includes structure, AWS modules, and automation 💡 14.04.2025 --- ---

📅 Daily Log – 16.04.2025

Task Description Notes Status Start Date Completion Date Hours Needed
Complete Documentation Finalized Markdown docs for infrastructure, logic, and Terraform modules Includes diagrams, ECS flow, RDS setup, IAM, etc. 14.04.2025 16.04.2025 3 Hrs
Finalize Project Final polish, backups, and documentation wrap-up Project officially completed 14.04.2025 16.04.2025 0.5 Hrs

✍️ Daily Summary – 14.04.2025

Massive progress day.
I completed three core automation tasks (SNS alerts, ECR cleanup, RDS retention) and laid the foundation for project documentation. These were key for transitioning the project into a maintainable and explainable state.


✍️ Daily Summary – 16.04.2025

Project completed.
All documentation was finalized, infrastructure was reviewed and polished, and the last bits of automation were tested. The entire M300 project is now officially complete and decommissioned. All Terraform modules, Lambda logic, CloudWatch, RDS, ECS, and ECR components are clean, secured, and documented.


📌 Weekly Summary – 14.04.2025 – 20.04.2025

Task Description Status Completion Date Hours Spent
SNS alert email confirmation Verified email integration with CloudWatch alarms 14.04.2025 1 Hrs
ECR lifecycle policy Cleanup rules for old images + untagged images 14.04.2025 1.5 Hrs
RDS snapshot cleanup Lambda logic Extended backup solution to include deletion of old backups 14.04.2025 1.5 Hrs
Finalized Markdown documentation Wrote intro, file structure, automation & monitoring docs 16.04.2025 3 Hrs
Project officially closed Reviewed, wrapped up, and marked project as complete 16.04.2025 0.5 Hrs

✅ Weekly Results

  • 📩 SNS Notifications: Confirmed working via test alarms + email alerts.
  • 🧹 ECR Lifecycle: Old and untagged images now cleaned up automatically.
  • 🗑️ RDS Cleanup: Lambda now deletes old snapshots to prevent cost bloat.
  • 📘 Documentation: All key components documented. Clean, complete, and usable as a reference.
  • 🏁 M300 Project Completed. All infrastructure has been decommissioned and archived.

⚠️ Problems Faced

  • ECR lifecycle policies took time to propagate; results weren’t instant.
  • Had to delete old Lambda zip deployments manually during testing.
  • Initial snapshot filter was too aggressive—refined it to target only rayan-tagged snapshots.

❓ Open Questions

  • Should lifecycle cleanup be extended to include CloudWatch logs or S3 objects?
  • What's the best tool for final infrastructure diagram visuals? (draw.io, Lucidchart, etc.)
  • Should I host the documentation as a static site (e.g., MkDocs or GitHub Pages)?

✔ Last updated: 20.04.2025