 }})
What we'll do in this lesson:
* Make small UI changes to the product page and the login page.
* Commit and push those changes to each microservice repository.
* Watch CodePipeline detect the changes, build Docker images, and update the ECS services.
* Verify the new versions are served by the Application Load Balancer.
## Changes made
I used the Cloud9 IDE to edit both microservice repositories. Below are the final files I saved for each service.
### Product microservice — templates/product.html
This is the polished, production-ready product page that was committed to the product microservice repository:
```html theme={null}
This is not actual crypto. This is just for learning purposes.
 }})
 }})
 }})
 }})
## Monitor pipeline progress and verify deployment
I opened each pipeline in the AWS Console and watched them progress through the standard stages:
| Stage | Typical Actions |
| ------ | ----------------------------------------------------------------- |
| Source | CodeCommit detects a push and supplies source artifacts |
| Build | CodeBuild builds Docker images and pushes to ECR |
| Deploy | CodePipeline updates ECS task definitions and deploys to services |
Both pipelines progressed through Source → Build → Deploy automatically. When the build completed, new ECS task definitions were registered and the ECS services were updated.
To verify the login UI change:
1. Open the ECS service for the login application.
2. Click "View Load Balancer" and copy the load balancer DNS name.
3. Open the DNS in your browser.
During a rolling deployment you may briefly see the old and new UI versions as the load balancer routes traffic between old and new containers. This is expected behavior until draining and health checks finish.