diff --git a/examples/data-solutions/cloudsql-multiregion/README.md b/examples/data-solutions/cloudsql-multiregion/README.md
index a388b6b6..4ad07713 100644
--- a/examples/data-solutions/cloudsql-multiregion/README.md
+++ b/examples/data-solutions/cloudsql-multiregion/README.md
@@ -5,8 +5,10 @@ This example creates a [Cloud SQL instance](https://cloud.google.com/sql) with m
 The solution is resilient to a regional outage. To get familiar with the procedure needed in the unfortunate case of a disaster recovery, please follow steps described in [part two](https://cloud.google.com/architecture/cloud-sql-postgres-disaster-recovery-complete-failover-fallback#phase-2) of the aforementioned article.
 
 The solution will use:
-- A VPC with Private Service Access to deploy the instances
-- Postgre SQL instanced with Private IP
+- VPC with Private Service Access to deploy the instances and VM
+- Cloud SQL - Postgre SQL instanced with Private IP
+- Goocle Cloud Storage bucket to handle database import/export
+- Google Cloud Engine instance to connect to the Posgre SQL instance
 
 This is the high level diagram:
 
diff --git a/examples/data-solutions/cloudsql-multiregion/diagram.png b/examples/data-solutions/cloudsql-multiregion/diagram.png
index 6148a53e..e32543c6 100644
Binary files a/examples/data-solutions/cloudsql-multiregion/diagram.png and b/examples/data-solutions/cloudsql-multiregion/diagram.png differ