diff --git a/images/334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B_AliCloud_patch.png b/images/334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B_AliCloud_patch.png
new file mode 100644
index 0000000000..284240f342
Binary files /dev/null and b/images/334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B_AliCloud_patch.png differ
diff --git a/modules/about-manually-maintained-credentials-upgrade.adoc b/modules/about-manually-maintained-credentials-upgrade.adoc
index 06435d5a5c..39bcece996 100644
--- a/modules/about-manually-maintained-credentials-upgrade.adoc
+++ b/modules/about-manually-maintained-credentials-upgrade.adoc
@@ -26,14 +26,14 @@ Some platforms only support using the CCO in one mode. For clusters that are ins
 For platforms that support using the CCO in multiple modes, you must determine which mode the cluster is configured to use and take the required actions for that configuration.
 
 .Credentials update requirements by platform type
-image::334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B.png[Decision tree showing the possible update paths for your cluster depending on the configured CCO credentials mode.]
+image::334_OpenShift_cluster_updating_and_CCO_workflows_0523_4.11_B_AliCloud_patch.png[Decision tree showing the possible update paths for your cluster depending on the configured CCO credentials mode.]
 
 {rh-openstack-first} and VMware vSphere::
 These platforms do not support using the CCO in manual mode. Clusters on these platforms handle changes in cloud provider resources automatically and do not require an update to the `upgradeable-to` annotation.
 +
 Administrators of clusters on these platforms should skip the manually maintained credentials section of the update process.
 
-{alibaba}, {ibm-cloud-title}, and Nutanix::
+{ibm-cloud-title} and Nutanix::
 Clusters installed on these platforms are configured using the `ccoctl` utility.
 +
 Administrators of clusters on these platforms must take the following actions:
diff --git a/modules/cco-ccoctl-upgrading.adoc b/modules/cco-ccoctl-upgrading.adoc
index f0faf56867..f467d96eae 100644
--- a/modules/cco-ccoctl-upgrading.adoc
+++ b/modules/cco-ccoctl-upgrading.adoc
@@ -24,28 +24,6 @@ On AWS clusters, some `ccoctl` commands make AWS API calls to create or modify A
 
 . Use the `ccoctl` tool to process all `CredentialsRequest` objects by running the command for your cloud provider. The following commands process `CredentialsRequest` objects:
 +
-.{alibaba}
-[%collapsible]
-====
-[source,terminal]
-----
-$ ccoctl alibabacloud create-ram-users \
-  --name <name> \// <1>
-  --region=<alibaba_region> \// <2>
-  --credentials-requests-dir=<path_to_credentials_requests_directory> \// <3>
-  --output-dir=<path_to_ccoctl_output_dir> <4>
-----
-<1> Specify the name used to tag any cloud resources that are created for tracking.
-<2> Specify the Alibaba Cloud region in which cloud resources will be created.
-<3> Specify the directory containing the files for the component `CredentialsRequest` objects.
-<4> Optional: Specify the directory in which you want the `ccoctl` utility to create objects. By default, the utility creates objects in the directory in which the commands are run.
-
-[NOTE]
-=====
-A RAM user can have up to two AccessKeys at the same time. If you run `ccoctl alibabacloud create-ram-users` more than twice, the previously generated manifests secret becomes stale and you must reapply the newly generated secrets.
-=====
-====
-+
 .Amazon Web Services (AWS)
 [%collapsible]
 ====