Update README.md

examples/combined_design/README.md

@@ -10,7 +10,8 @@ The Terraform code presented here will deploy Palo Alto Networks VM-Series firew
 
 ## Reference Architecture Design
 
-![Simplified High Level Topology Diagram](https://github.com/PaloAltoNetworks/terraform-aws-swfw-modules/assets/2110772/9c08a6e3-bb3e-49c8-87ec-2fccb914899e)
+![Simplified High Level Topology Diagram](https://github.com/PaloAltoNetworks/terraform-aws-swfw-modules/assets/2110772/425bb2f3-976f-4262-8595-32f98a9b391a)
+
 
 This code implements:
 - a _centralized design_, which secures outbound, inbound, and east-west traffic flows using an AWS transit gateway (TGW). Application resources are segmented across multiple VPCs that connect in a hub-and-spoke topology, with a dedicated VPC for security services where the VM-Series are deployed
@@ -25,7 +26,7 @@ This design supports interconnecting a large number of VPCs, with a scalable sol
 
 Inbound traffic originates outside your VPCs and is destined to applications or services hosted within your VPCs, such as web or application servers. The combined model implements inbound security by using the VM-Series and Gateway Load Balancer (GWLB) in a Security VPC, with distributed GWLB endpoints in the application VPCs. Unlike with outbound traffic, this design option does not use the transit gateway for traffic forwarding between the security VPC and the application VPCs.
 
-![Detailed Topology Diagram](https://github-production-user-asset-6210df.s3.amazonaws.com/9674179/240822321-37a7ffc1-134a-4037-b174-5a2abe44f475.png)
+![image](https://github.com/PaloAltoNetworks/terraform-aws-swfw-modules/assets/2110772/730327e8-cb90-4d80-9b1c-e5ee927e0cc7)
 
 ## Prerequisites