swapped svg diagram files

Author: jddocs

docs/guides/platform/migrate-to-linode/migrate-from-aws-security-groups-to-cloud-firewalls/Equivalent_architectures_AWS.svg

@@ -63,7 +63,7 @@ The AWS Security Group is configured with inbound rules to restrict access to kn
 
 The equivalent setup on Akamai Cloud uses a single Linode instance running the same services. The Cloud Firewalls service is used to recreate the access controls previously handled by the AWS Security Group.
 
-![Architecture diagram of AWS EC2 instance and services environment with equivalent setup on Akamai Cloud.](example-environment-architecture.svg)
+![Architecture diagram of AWS EC2 instance and services environment with equivalent setup on Akamai Cloud.](Equivalent_architectures_AWS.svg)
 
 ## Document Your Current Configuration
 
@@ -231,7 +231,7 @@ To access this information using the `aws` CLI, run the following commands:
 
 The example in this guide only has inbound rules, with traffic allowed for specific IP addresses. The inbound permissions for the example in this guide are diagrammed below:
 
-![Visual flowchart of inbound port permissions in the example setup.](inbound-permissions-diagram.svg)
+![Visual flowchart of inbound port permissions in the example setup.](Inbound_policies_example_AWS.svg)
 
 {{< note title="Note Your Own Firewall Configuration" >}}
 Your firewall may have both inbound and outbound rules, with traffic allowed or denied for specific IP addresses.

docs/guides/platform/migrate-to-linode/migrate-from-aws-security-groups-to-cloud-firewalls/Inbound_policies_example_AWS.svg

@@ -63,7 +63,7 @@ The Azure Firewall is configured with inbound rules to restrict access to known
 
 The equivalent setup on Akamai Cloud uses a single Linode instance running the same services. The Cloud Firewalls service is used to recreate the access controls previously handled by the Azure Firewall.
 
-![Architecture overview of Azure Firewall and VM network with equivalent setup on Akamai Cloud.](example-environment-architecture.svg)
+![Architecture overview of Azure Firewall and VM network with equivalent setup on Akamai Cloud.](Equivalent_architectures_Azure.svg)
 
 ## Document Your Current Configuration
 
@@ -249,7 +249,7 @@ To view Azure Firewall rules from the `az` CLI, run the following commands:
 
 The inbound traffic routing rules for the example in this guide are diagrammed below:
 
-![Inbound traffic routing through Azure Firewall to VM.](inbound-routing-diagram.svg)
+![Inbound traffic routing through Azure Firewall to VM.](Inbound_policies_example_Azure.svg)
 
 ### Plan Your Rule-Mapping Strategy
 

docs/guides/platform/migrate-to-linode/migrate-from-aws-security-groups-to-cloud-firewalls/index.md

@@ -63,7 +63,7 @@ The Google Cloud NGFW is configured with inbound rules to restrict access to kno
 
 The equivalent setup on Akamai Cloud uses a single Linode instance running the same services. The Cloud Firewalls service is used to recreate the access controls previously handled by the Google Cloud NGFW.
 
-![Architecture diagram of Google Cloud VM instance and services environment with equivalent setup on Akamai Cloud.](example-environment-architecture.svg)
+![Architecture diagram of Google Cloud VM instance and services environment with equivalent setup on Akamai Cloud.](Equivalent_architectures_Google_Cloud.svg)
 
 ## Document your Current Configuration
 
@@ -182,7 +182,7 @@ gcloud compute firewall-rules list \
 
 The example in this guide only has inbound rules, with traffic allowed for specific IP addresses. The inbound permissions for the example in this guide are diagrammed below:
 
-![Visual flowchart of inbound port permissions in the example setup.](inbound-permissions-diagram.svg)
+![Visual flowchart of inbound port permissions in the example setup.](Inbound_policies_example_Google_Cloud.svg)
 
 {{< note title="Note Your Own Firewall Configuration" >}}
 Your firewall may have both inbound and outbound rules, with traffic allowed for specific IP addresses or denied for specific IP addresses.