Fix jpg

lab-3/README.md

@@ -41,7 +41,7 @@
       because it mentioned lab 2, so my assumption was that it had already been set up
       (it was not). So I had to go back and fix the missing outbound connection.
 
-![screenshot of listing s3 contents](./assets/s3-access-screenshot.jpg)
+![screenshot of listing s3 contents](./assets/s3-access-screenshot.png)
 
 ### Stretch Goals
 - [x] **Deep Dive into Bucket Policies**

lab-3/terraform/main.tf

@@ -101,27 +101,27 @@ resource "aws_iam_policy" "ec2_s3_policy" {
     }
 }
 
-# Create AMI
-resource "aws_ami_from_instance" "ami_snapshot" {
-  name = "ami-snapshot-2025-06-17"
-  source_instance_id = aws_instance.my_first_linux.id
-  snapshot_without_reboot = true
-
-  tags = {
-    Name = "labs"
-  }
-}
-
-# Launch new instance from AMI
-resource "aws_instance" "my_second_linux" {
-    instance_type = "t2.micro"
-    ami = aws_ami_from_instance.ami_snapshot.id
-	security_groups = ["ssh-access-witch"]
-
-    tags = {
-        Name = "labs"
-    }
-}    
+# # Create AMI
+# resource "aws_ami_from_instance" "ami_snapshot" {
+#   name = "ami-snapshot-2025-06-17"
+#   source_instance_id = aws_instance.my_first_linux.id
+#   snapshot_without_reboot = true
+# 
+#   tags = {
+#     Name = "labs"
+#   }
+# }
+# 
+# # Launch new instance from AMI
+# resource "aws_instance" "my_second_linux" {
+#     instance_type = "t2.micro"
+#     ami = aws_ami_from_instance.ami_snapshot.id
+# 	security_groups = ["ssh-access-witch"]
+# 
+#     tags = {
+#         Name = "labs"
+#     }
+# }