11/18/2025 Mid Sprint Minutes

[JohnBrennan95]

Capstone Project Meeting 11/18/2025

---

Discussion Summary

• Reviewed current progress and identified remaining blockers for Phase 1.
• Clarified Lambda authentication flow: Lambda functions run under an IAM role, and AWS injects credentials automatically. No credentials are passed directly.
• Unit tests use Moto, which bypasses IAM and focuses solely on function logic.
• Integration tests (supported by Mu) will expose real permission issues once we transition from Moto to AWS sandbox testing.
• Logging for Phase 1 will be minimal and used only for stress testing (timings, start/end markers, monitor ID).
• Monitor utility integration may require further Mu research to support bulk creation and cleanup of test monitors.

---

Updates by Member

Rory

• Completed the primary function for Issue Implement run_due_checks with Lambda Logging #27; currently debugging test failures.

---

Tim

• Open PR Run Check minimal #30 pending updates; reviewing feedback and investigating Lambda logging approach.

---

Caleb

• Architecture documentation merged; gathering integration testing requirements and IAM details, published Authentication and Testing #32.

---

John

• Mocked integration testing completed Build Monitor Utility for Stress Testing #29 ; preparing for AWS-based validation and utility integration work.

---

Next Steps / Action Items

• Rory: Finalize testing for run_due_checks and resolve current issues.
• Tim: Apply PR feedback and finalize logging strategy for Lambda execution.
• Caleb: Deliver integration test requirements and refine IAM configuration.
• John: Continue researching Mu integration for monitor utility and prepare AWS testing workflow.

---