Worklog Week 9

Week 9 Objectives:

  • Infrastructure as Code (IaC): Codify all manual resources using AWS SAM (Serverless Application Model) to ensure reproducibility.
  • Environment Consistency: Eliminate “works on my machine” issues by containerizing the build process with Docker.
  • Deployment Strategy: Establish a reliable “Cloud-based Development” workflow to validate IAM permissions and service integrations.
  • Integrate Docker to standardize the environment for sam build.

Tasks to be Deployed This Week:

DayTaskStart DateCompletion DateResources
Monday- IaC Definition- Authored the template.yaml to define Serverless resources (Functions, APIs, Tables).
- Applied SAM Policy Templates (e.g., DynamoDBCrudPolicy) to enforce the Principle of Least Privilege.		04/11/202504/11/2025
Tuesday- Containerization- Integrated Docker into the sam build --use-container workflow.
- Solved binary incompatibility issues (Python libraries with C-extensions) between local Windows/Mac OS and the AWS Lambda Linux environment.		05/11/202506/11/2025
Wednesday- Troubleshooting- Encountered limitations with sam local start-api (local emulation does not support full IAM or Service integration).
- Root caused build failures related to requirements.txt dependency conflicts.		06/11/202507/11/2025
Thursday- Strategy Shift- Transitioned from Local Emulation to Cloud-based Testing.
- Provisioned a dedicated dev stack on AWS to run integration tests against real service endpoints.		07/11/202508/11/2025
Friday- First Deployment- Successfully executed sam deploy --guided to the development environment.
- Verified the CloudFormation Stack creation and resource output values.		08/11/202508/11/2025

Week 9 Achievements:

  • Completed the technology transition to the AWS SAM development model for the entire project.
  • Infrastructure is now Code: The entire environment can be spun up or torn down with a single CLI command (sam deploy/sam delete).
  • Consistent Runtimes: Docker integration ensures that code compiled locally runs identically in production.
  • Testing Maturity: Moved to a more reliable testing strategy that validates actual AWS cloud behaviors and permissions.