Cleanup

You made it through IAM and SSM. Before moving on, we need to remove the main RDS instance, then optionally clean up cost-driving compute resources if you're taking a break.

Cost check: RDS instances, EC2 instances, and Elastic IPs all cost money while they exist. Delete what you don't need when you're not actively working.

Assignment

Delete the main RDS database instance, then optionally clean up EC2 and Elastic IP resources.

Delete the main RDS database instance (patientping-db).
1. Navigate to "RDS" → "Databases" in the AWS Console.
2. Select patientping-db.
3. Click "Actions" → "Delete."
4. Configure deletion:
  - Create final snapshot: Uncheck
  - Retain automated backups: Uncheck
5. Type delete me to confirm, then click "Delete."
6. Wait for deletion to complete.

Optional: Only Do This If You're Taking an Extended Break

Optional: terminate the app server EC2 instance (patientping-web-v2) if you're taking a break.
1. Navigate to "EC2" → "Instances" in the AWS Console.
2. Select patientping-web-v2.
3. Click "Instance state" → "Terminate (delete) instance."
4. Confirm termination and wait for state Terminated.
Optional: release the app server Elastic IP if you're taking a break.
1. Navigate to "EC2" → "Elastic IPs" in the AWS Console.
2. Select the Elastic IP used for patientping-web-v2.
3. Click "Actions" → "Release Elastic IP addresses," then confirm.

If you do the optional EC2/EIP cleanup, you'll need to recreate patientping-web-v2 and re-associate an Elastic IP before the next time you need server-based exercises.