fix: use t3.large and add Buildx for visualizer EC2#43
Conversation
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughUpdated EC2 CloudFormation infrastructure for the database visualizer lab by upgrading the instance type from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. Two-line fix: CloudFormation instance type t3.medium -> t3.large, and added Docker Buildx plugin install to UserData (required by latest Docker Compose for image building). Verified end-to-end on EC2: stack deploys, visualizer loads, all 4 API endpoints work. |
There was a problem hiding this comment.
Pull request overview
This PR updates the Lab 10 database visualizer’s EC2 provisioning and lab instructions to support the current Docker Compose build flow and improve runtime reliability by increasing instance capacity.
Changes:
- Upgraded the visualizer EC2 instance type from
t3.mediumtot3.large. - Added Docker Buildx plugin installation to EC2 UserData (required for
docker compose buildon the provisioned AMI/Docker package). - Updated the lab’s CloudFormation stack creation time estimate to 5–10 minutes.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
10-databases/visualizer/cloudformation.yaml |
Increases instance size and installs the Docker Buildx CLI plugin alongside Compose in UserData. |
10-databases/visualizer/LAB-VISUALIZER.md |
Updates expected stack creation time to reflect initial image pulls/build. |
Summary
Test plan
Summary by CodeRabbit
Documentation
Chores