CLoudFormation changed its behaviour. If an RDS instance is deleted, a manual snapshot is now created by default which could cause costs.

For AWS::RDS::DBInstance resources that don't specify the DBClusterIdentifier property, the default policy is Snapshot which can cause unwanted costs. However, for production setups, we highly recommend to stay with the default to avoid data loss.

Author: michaelwittig

chapter14/wordpress-loadtest.json

@@ -236,6 +236,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"BackupRetentionPeriod": "0",

chapter14/wordpress.json

@@ -223,6 +223,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"BackupRetentionPeriod": "0",

chapter2/template.json

@@ -197,6 +197,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"BackupRetentionPeriod": "0",

chapter9/template-multiaz.json

@@ -216,6 +216,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"DBInstanceClass": "db.t2.micro",

chapter9/template-snapshot.json

@@ -216,6 +216,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"DBInstanceClass": "db.t2.micro",

chapter9/template.json

@@ -216,6 +216,7 @@
 		},
 		"Database": {
 			"Type": "AWS::RDS::DBInstance",
+			"DeletionPolicy": "Delete",
 			"Properties": {
 				"AllocatedStorage": "5",
 				"DBInstanceClass": "db.t2.micro",