

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 4
click for more info
Not enough gems
Cost: 6 gems
1: EC2 Instance Configuration: Keys
incomplete
2: EC2 Instances
incomplete
3: AMIs and Instance Types
incomplete
4: Public IPs
incomplete
5: Elastic IPs
incomplete
6: Security Groups
incomplete
7: SSH to Our Server
incomplete
8: Deploy the PatientPing Site
incomplete
9: Open Web Traffic
incomplete
10: Creating and Using Your Own AMI
incomplete
11: Reserved Instances and Savings Plans
incomplete
12: Auto Scaling Groups
incomplete
13: Launch Template
incomplete
14: Launch from Template
incomplete
15: Spot Instances
incomplete
16: Stateful and Stateless Applications
incomplete
17: Optional Cleanup
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Now that you can SSH into the patientping-web server, let's get the PatientPing application running on it. We'll install git, clone the app, install its dependencies, and start the web server.
Cost check: No new resources. You're using the same EC2 instance; cost is unchanged.
Deploy the PatientPing application on the patientping-web instance.
sudo dnf upgrade
sudo dnf install git
curl -LsSf https://astral.sh/uv/install.sh | sh
which git
which uv
cd ~
git clone https://github.com/bootdotdev/patientping-web.git
cd patientping-web
uv sync
uv run patientping.py
8080!This is the security group doing its job. By default, all inbound traffic is denied unless you explicitly allow it. Right now the only hole in the firewall is port 22 for SSH.
Don't worry, we'll fix this soon. In a new terminal, leave the server running in the original session.
Run and submit the CLI tests.