WIP Week 1

week1.md

@@ -0,0 +1,79 @@
+## Project Context: PetCLinic  Microservices -> AWS
+
+## Context and Scope
+
+This project will migrate the Spring PetClinic Microservices demo from its local/on-premise setup to AWS Cloud. The focus is infrastructure modernization, CI/CD automation, observability, and resilience but not application feature development.
+
+### Stakeholders
+
+| Role | Responsibility | 
+|----|----|
+| Project Sponsor | Funding, final approval | 
+| Project Manager | Scheduling, stakeholder coordination |
+| Cloud Architect | Architecture, service selection |
+| Dev Lead | App changes for cloud readiness |
+| DevOps Engineer | CI/CD, IaC, deployments, monitoring |
+| Security Engineer | IAM, encryption, compliance |
+| End Users / Demo Audience | Acceptance and usability feedback
+
+### Expectations
+
+- No app feature development unless necessary for cloud deployment.
+- AWS is the only target cloud
+
+### Objectives
+
+- Run full PetClinic microservices on AWS with CI/CD.
+- Observability: logs, metrics, traces for 100% of services.
+- Cost target: keep monthly infra cost under a defined limit (set by Project Sponsor).
+- Security: secrets encrypted, least-privilege IAM, HTTPS for all endpoints.
+
+### Deadlines
+
+| Milestone | Date |
+|----|----|
+| Project approval | Oct 27, 2025 |
+| CI/CD & Automation | Nov 3, 2025 |
+| Infrastructure | Nov 10,  2025 |
+| Data | Nov 17, 2025 |
+| Observability | Nov 24, 2025 |
+| Prep: Presentation, Demo, and Pre-defense | Dec 3, 2025 |
+
+## In Scope
+
+| Included items | Objective |
+|----|----|
+| Application | Only necessary changes (if applicable) to facilitate cloud integration |
+| Infrastructure | Design and deploy a reproducible, cloud-native architecture |
+| CI/CD Automation | Implement automated build, test, and deployment pipelines |
+| Containerization | Adapt existing microservices to use AWS.|
+| Monitoring & Logging | Centralized logs, metrics, and traces |
+| Security & IAM | Least-privilege IAM roles, encryption, and subnet segmentation. |
+| Backup & Recovery | Redundancy, failover, backup, BCP/DRP |
+| Documentation | Architecture diagrams, specifications, and operational runbooks. |
+
+## Out of Scope
+
+| Excluded items | Reason |
+|----|----|
+| Application feature or UI changes | Funcitoniality remains unchanged. |
+| Multi-cloud or hybrid deployment | Focus solely on AWS environment. |
+| Cost-optimization | Addressed in a later project if necessary |
+
+
+## Requirements
+
+### Functional requirements
+| Stakeholder / Role | Requirement | Description |
+|----|----|----|
+| **Developers** | Continuous Integration | Each merge must trigger automated build, test, and image creation. |
+| | Local to Cloud Parity | Development environment must mirror AWS setup using Docker Compose or local ECS simulation. |
+| **DevOps Engineers** | Automated Deployment | CI/CD pipeline must deploy microservices to Dev, Staging, and Prod environments automatically. |
+| | Test Automation | Integration tests must run automatically in CI/CD pipeline. |
+|| Infrastructure as Code | All AWS resources defined through configuration files |
+| | Monitoring & Alerts | Centralized logging, metrics, and tracing for all microservices. Automated alerting for service downtime or threshold breaches. |
+| **Security Team** | Access Control | Roles per service with least-privilege permissions.|
+| | Secrets Management | All secrets stored securely. |
+| **Product / Management** | Availability & Demo Readiness | System must be reliable and presentable for client or internal demos.|
+| **End Users (Demo Audience)** | Stable Access | Web UI and APIs must remain responsive under typical load. |
+