Cleanup

Delete monitoring resources now; optionally keep or remove patientping-web-v2 and its Elastic IP depending on whether you're continuing.

1. Delete CloudWatch resources:
   1. Navigate to "CloudWatch" → "Alarms" in the AWS Console.
   2. Select the patientping-cpu-alarm.
   3. Click "Actions" → "Delete" and confirm deletion.
   4. Navigate to "CloudWatch" → "Dashboards" in the AWS Console.
   5. Select patientping-dashboard.
   6. Click "Delete dashboard" and confirm deletion.
   7. Navigate to "CloudWatch" → "Logs" → "Log Management" → "Log groups" in the AWS Console.
   8. Select the patientping-monitoring log group.
   9. Click "Actions" → "Delete log group(s)" and confirm deletion.
2. Delete the SNS topic:
   1. Navigate to "SNS" → "Topics" in the AWS Console.
   2. Select the patientping-alerts topic.
   3. Click "Delete" and confirm deletion (you may need to type delete me).
3. If you're continuing and keeping patientping-web-v2, switch it back to the patientping-ec2-readonly-role IAM role:
   1. Navigate to "EC2" → "Instances" in the AWS Console.
   2. Select patientping-web-v2.
   3. Click "Actions" → "Security" → "Modify IAM role."
   4. Select patientping-ec2-readonly-role and click "Update IAM role."
4. Delete the IAM role created for monitoring:
   1. Navigate to "IAM" → "Roles" in the AWS Console.
   2. Select patientping-monitoring-role.
   3. Click "Delete" and confirm deletion.

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

1. Optional: terminate patientping-web-v2.
   1. Navigate to "EC2" → "Instances" in the AWS Console.
   2. Select patientping-web-v2.
   3. Click "Instance state" → "Terminate (delete) instance" and confirm termination.
   4. Wait until the instance state is Terminated.
2. Optional: release the Elastic IP attached to patientping-web-v2.
   1. Navigate to "EC2" → "Elastic IPs" in the AWS Console.
   2. Select the Elastic IP used by patientping-web-v2.
   3. Click "Actions" → "Release Elastic IP addresses" and confirm the release.