6.1 Objective

Since the deployment mechanism was already built and proven in Day 7-10, this phase focused on verifying the pipeline’s reliability under real edits rather than rebuilding it.

6.2 Tests Performed

Test 1: End-to-end content update

Edited a visible line in index.html, committed, and pushed to main. Workflow triggered automatically and completed in 9 seconds. Change was reflected in the S3 bucket contents and confirmed live on the site - matched the local code exactly.

Test 2: Deletion propagation

Deleted README.md locally, committed, and pushed. The – delete flag in the aws s3 sync command correctly removed the file from the S 3 bucket as well, confirming the sync is a true mirror rather than additive-only.

6.3 Result

Full push-to-live loop confirmed working end-to-end: edits, additions, and deletions all sync correctly and quickly ( $true$ s trigger-to-complete).

6.4 Screenshots

workflow run

S3 bucket after README.md deletion

6.5 Checkpoint Summary

• Status: Done
• Outcome: Pipeline verified reliable for updates and deletions, fast turnaround ( $true$ s)
• Blockers: None
• Key learning: Testing deletions, not just additions, is essential to confirm a sync-based deploy step behaves as a true mirror of the repo