vault backup: 2025-07-22 14:31:55

Author: aslamcodes

aws/s3-security/s3-vpce.md

@@ -1,11 +1,10 @@
 ---
 dg-publish: true
-tags: 
+tags:
+  - todo
 type: 
 date: 19th July 2025
 done: false
 ---
-
 We can use IAM resource based policy to force the request to be only from a vpce. 
-
 aws:SourceVpce

aws/soa/clouformation.md

@@ -43,4 +43,7 @@ Resources:
 ### Important:
 - `DeletionPolicy` is per-resource.
 - Doesn’t protect from **explicit deletes** outside CloudFormation.
-- Doesn’t stop updates that **replace** the resource.
+- Doesn’t stop updates that **replace** the resource.
+
+# Termination protection
+- If you attempt to delete a stack with termination protection enabled, the deletion fails and the stack - including its status - remains unchanged

aws/soa/direct connect and s3 vpce.md

@@ -10,6 +10,6 @@ done: false
 - Cross Network Connection
 - Public VIF
 - It's not possible to directly access an S3 bucket through a private virtual interface (VIF) using Direct Connect
-
 # References
-- [[s3-vpce]]
+- [[s3-vpce]]
+- [[public endpoint with vpce]]

aws/soa/public endpoint if vpce.md aws/soa/public endpoint with vpce.mdaws/soa/public endpoint if vpce.md renamed to aws/soa/public endpoint with vpce.md

@@ -5,12 +5,11 @@ type:
 date: 19th July 2025
 done: false
 ---
-
 #ami
-Note
 - AMI is **region specific** since they are stored in **S3**, **AMIs are basically ec2 config + its volume snapshots**
 - **No-Reboot** - AMI is taken as the instance is running, Not Application consistent
 - **Delete-on-termination** 
+- Data cached by application or os might not be stored in ebs snapshots as it only cares about what stored in disks
 
 | EBS Backed          | Instance Store backed |
 | ------------------- | --------------------- |

aws/soa/taking application-consistent AMI.md

@@ -35,7 +35,7 @@ It wasn’t a bad assumption for the general case, but it **didn’t fit many re
 - designed for high IO intensive workloads, such as databases
 -  100 IOPS up to 64,000 IOPS
 - maximum ratio of provisioned IOPS to requested volume size (in GiB) is 50:1
-- for 100 GB its 5000 IOPS
+- for 100 GB its 5000 IOPS. Ie the maximum is 50 IOPS for 1 GB
 - But maximum iops is 64000 for 1280GB or larger
 # Modifying volume 
 - After modifying a volume, you must wait at least **six hours** and ensure that the volume is in the `in-use` or `available` state before you can modify the same volume.