diff --git a/images/156_OpenShift_ROSA_Arch_0621_private_public_classic.png b/images/156_OpenShift_ROSA_Arch_0621_private_public_classic.png
new file mode 100644
index 0000000000..320424a151
Binary files /dev/null and b/images/156_OpenShift_ROSA_Arch_0621_private_public_classic.png differ
diff --git a/images/156_OpenShift_ROSA_Arch_0621_privatelink.svg b/images/156_OpenShift_ROSA_Arch_0621_privatelink.svg
deleted file mode 100644
index 37f9712650..0000000000
--- a/images/156_OpenShift_ROSA_Arch_0621_privatelink.svg
+++ /dev/null
@@ -1,258 +0,0 @@
-
diff --git a/images/156_OpenShift_ROSA_Arch_1221_privatelink.png b/images/156_OpenShift_ROSA_Arch_1221_privatelink.png
new file mode 100644
index 0000000000..8828ac1228
Binary files /dev/null and b/images/156_OpenShift_ROSA_Arch_1221_privatelink.png differ
diff --git a/images/ossm-node-badge-missing-sidecar.png b/images/ossm-node-badge-missing-sidecar.png
new file mode 100644
index 0000000000..67349ab01b
Binary files /dev/null and b/images/ossm-node-badge-missing-sidecar.png differ
diff --git a/images/ossm-node-badge-missing-sidecar.svg b/images/ossm-node-badge-missing-sidecar.svg
deleted file mode 100644
index f8005984ad..0000000000
--- a/images/ossm-node-badge-missing-sidecar.svg
+++ /dev/null
@@ -1,119 +0,0 @@
-
-
-
-
diff --git a/images/telmetry-and-insights-operator-data-flow.png b/images/telmetry-and-insights-operator-data-flow.png
new file mode 100644
index 0000000000..cfffa56818
Binary files /dev/null and b/images/telmetry-and-insights-operator-data-flow.png differ
diff --git a/images/telmetry-and-insights-operator-data-flow.svg b/images/telmetry-and-insights-operator-data-flow.svg
deleted file mode 100644
index 4d0820cdd7..0000000000
--- a/images/telmetry-and-insights-operator-data-flow.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/modules/osd-aws-privatelink-architecture.adoc b/modules/osd-aws-privatelink-architecture.adoc
index d7836b6216..dfce0e1c3d 100644
--- a/modules/osd-aws-privatelink-architecture.adoc
+++ b/modules/osd-aws-privatelink-architecture.adoc
@@ -16,7 +16,7 @@ The following diagram shows network connectivity of a PrivateLink cluster.
.Multi-AZ AWS PrivateLink cluster deployed on private subnets
-image::156_OpenShift_ROSA_Arch_0621_privatelink.svg[Multi-AZ AWS PrivateLink cluster deployed on private subnets]
+image::156_OpenShift_ROSA_Arch_1221_privatelink.png[Multi-AZ AWS PrivateLink cluster deployed on private subnets]
[id="osd-aws-reference-architecture.adoc_{context}"]
== AWS reference architectures
diff --git a/modules/ossm-sidecar-validate-kiali.adoc b/modules/ossm-sidecar-validate-kiali.adoc
index 749e390e6b..f82035fad7 100644
--- a/modules/ossm-sidecar-validate-kiali.adoc
+++ b/modules/ossm-sidecar-validate-kiali.adoc
@@ -9,7 +9,7 @@ This module included in the following assemblies:
The Kiali console offers several ways to validate whether or not your applications, services, and workloads have a sidecar proxy.
.Missing sidecar badge
-image::ossm-node-badge-missing-sidecar.svg[Missing Sidecar badge]
+image::ossm-node-badge-missing-sidecar.png[Missing Sidecar badge]
The *Graph* page displays a node badge indicating a *Missing Sidecar* on the following graphs:
diff --git a/modules/rosa-architecture.adoc b/modules/rosa-architecture.adoc
index d5f8dbee0d..0a1a9db10d 100644
--- a/modules/rosa-architecture.adoc
+++ b/modules/rosa-architecture.adoc
@@ -8,7 +8,7 @@ You can install ROSA using either a public or private network. Configure a priva
Red Hat manages the cluster with limited access through a public network. For more information, see xref:../../rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc#rosa-service-definition[ROSA service definition].
.ROSA Classic deployed on public and private networks
-image::156_OpenShift_ROSA_Arch_0621_arch.svg[ROSA deployed on public and private networks]
+image::156_OpenShift_ROSA_Arch_0621_private_public_classic.png[ROSA deployed on public and private networks]
If you are using {hcp-title-first}, you can create your clusters on public and private networks as well. The following images depict the architecture of both public and private networks.
diff --git a/modules/rosa-hcp-classic-comparison.adoc b/modules/rosa-hcp-classic-comparison.adoc
index 0fe2824fa1..36ca7689af 100644
--- a/modules/rosa-hcp-classic-comparison.adoc
+++ b/modules/rosa-hcp-classic-comparison.adoc
@@ -75,7 +75,7 @@
ROSA Classic and ROSA with HCP offer options to install your cluster on public and private networks. The following images show the differences between these options.
.ROSA Classic deployed on public and private networks
-image::156_OpenShift_ROSA_Arch_0621_arch.svg[ROSA deployed on public and private networks]
+image::156_OpenShift_ROSA_Arch_0621_private_public_classic.png[ROSA deployed on public and private networks]
.ROSA with HCP deployed on a public network
image::ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
diff --git a/modules/understanding-telemetry-and-insights-operator-data-flow.adoc b/modules/understanding-telemetry-and-insights-operator-data-flow.adoc
index 641328cb76..28c841d968 100644
--- a/modules/understanding-telemetry-and-insights-operator-data-flow.adoc
+++ b/modules/understanding-telemetry-and-insights-operator-data-flow.adoc
@@ -15,7 +15,7 @@ All of the communication with Red Hat occurs over encrypted channels by using Tr
Access to the systems that handle customer data is controlled through multi-factor authentication and strict authorization controls. Access is granted on a need-to-know basis and is limited to required operations.
.Telemetry and Insights Operator data flow
-image:telmetry-and-insights-operator-data-flow.svg[Telemetry and Insights Operator data flow]
+image:telmetry-and-insights-operator-data-flow.png[Telemetry and Insights Operator data flow]
ifdef::openshift-dedicated[]
// TODO: Not critical for now, but should this diagram be updated to say "OpenShift Dedicated" instead of "OpenShift Container Platform"?