diff --git a/docs/cloud-cost-management/content/auto-stopping/aws-as.md b/docs/cloud-cost-management/content/auto-stopping/aws-as.md
index 39a755bf0bf..a707345ca87 100644
--- a/docs/cloud-cost-management/content/auto-stopping/aws-as.md
+++ b/docs/cloud-cost-management/content/auto-stopping/aws-as.md
@@ -4,8 +4,13 @@ import RedirectIfStandalone from '@site/src/components/DynamicMarkdownSelector/R
 
 <RedirectIfStandalone label="AWS" targetPage="/docs/cloud-cost-management/get-started/dynamic-get-started" />
 
-## Prerequisite: Set Up Proxy and/or Load Balancer
+## Prerequisite
 
+- [Create an AWS Connector for AutoStopping Rules](/docs/cloud-cost-management/get-started/#aws)
+- Proxy and/or Load Balancer for Traffic-based AutoStopping Rules. For scheduled only AutoStopping Rules, this is not required.
+
+
+## Setup Proxy and/or Load Balancer (for Traffic-based AutoStopping Rules)
 AutoStopping is designed to integrate seamlessly with native load-balancing solutions like **AWS ALB**. However, for use cases that fall outside of these integrations such as SSH, RDP, or RDS connections, AutoStopping offers an advanced reverse proxy solution: **AutoStopping Proxy**.
 
 
@@ -427,7 +432,7 @@ echo ">>> Setup complete."
 
 ---------
 </TabItem>
-<TabItem value="setup-access" label="Step 2: Setup Access"> 
+<TabItem value="setup-access" label="Step 2: Setup Access [Traffic-based AutoStopping Rules]"> 
 
 <Tabs>
 <TabItem value="ec2-asg" label="EC2 & ASGs">
diff --git a/docs/cloud-cost-management/content/auto-stopping/azure-as.md b/docs/cloud-cost-management/content/auto-stopping/azure-as.md
index 46061784a20..47cf676ccc7 100644
--- a/docs/cloud-cost-management/content/auto-stopping/azure-as.md
+++ b/docs/cloud-cost-management/content/auto-stopping/azure-as.md
@@ -5,7 +5,11 @@ import RedirectIfStandalone from '@site/src/components/DynamicMarkdownSelector/R
 <RedirectIfStandalone label="AWS" targetPage="/docs/cloud-cost-management/get-started/dynamic-get-started" />
 
 
-## Prerequisite: Set Up Proxy and/or Load Balancer
+## Prerequisite
+- [Create an Azure Connector for AutoStopping Rules](/docs/cloud-cost-management/get-started/#azure)
+- Proxy and/or Load Balancer for Traffic-based AutoStopping Rules. For scheduled only AutoStopping Rules, this is not required.
+
+## Set Up Proxy and/or Load Balancer
 
 Set up a proxy or load balancer that will intercept and manage traffic to your resources. This component is what enables the seamless start/stop functionality.
 
@@ -275,7 +279,7 @@ To create a fixed schedule for your rule, do the following:
 
 </TabItem>
 
-<TabItem value="setup-access" label="Step 2: Setup Access"> 
+<TabItem value="setup-access" label="Step 2: Setup Access [Traffic-based AutoStopping Rules]"> 
 
 Now that you have the AutoStopping rule configured, define how you would want to access the underlying application running on the resources managed by this Rule. You can use either of the following or both the methods depending on your requirement.
 
diff --git a/docs/cloud-cost-management/content/auto-stopping/gcp-as.md b/docs/cloud-cost-management/content/auto-stopping/gcp-as.md
index af9fb32128b..155dc295f2e 100644
--- a/docs/cloud-cost-management/content/auto-stopping/gcp-as.md
+++ b/docs/cloud-cost-management/content/auto-stopping/gcp-as.md
@@ -5,7 +5,13 @@ import RedirectIfStandalone from '@site/src/components/DynamicMarkdownSelector/R
 <RedirectIfStandalone label="AWS" targetPage="/docs/cloud-cost-management/get-started/dynamic-get-started" />
 
 
-## Prerequisite: Set Up Proxy 
+## Prerequisite
+
+- [Create a GCP Connector for AutoStopping Rules](/docs/cloud-cost-management/get-started/#gcp)
+- Proxy for Traffic-based AutoStopping Rules. For scheduled only AutoStopping Rules, this is not required.
+
+
+## Set Up Proxy 
 
 Set up a proxy or load balancer that will intercept and manage traffic to your resources. This component is what enables the seamless start/stop functionality.
 
@@ -24,7 +30,7 @@ An AutoStopping Proxy is a virtual machine that sits in front of your virtual ma
     - **VPC**: Select the Virtual Private Cloud where your resources are located
     - **Network tags**: Select the **Network tags** to enable ports on the proxy VM which would be receiving traffic or the one that would be used to access the proxy.
     - **Subnet**: Select the subnet for the proxy deployment
-    - **Machine type**: Select an appropriate AWS instance type for the proxy
+    - **Machine type**: Select an appropriate instance type for the proxy
       - Choose based on your expected traffic volume and performance needs
     - **TLS Certificate Secret Version**: Create a secret in your GCP account. Go to [Create a secret](https://cloud.google.com/secret-manager/docs/creating-and-accessing-secrets). 
     - **TLS Private Key Secret Version**: Provide the ARN of your private key secret
@@ -159,7 +165,7 @@ To create a fixed schedule for your rule, do the following:
 
 </TabItem>
 
-<TabItem value="setup-access" label="Step 2: Setup Access"> 
+<TabItem value="setup-access" label="Step 2: Setup Access [Traffic-based AutoStopping Rules]"> 
 
 <Tabs>
 <TabItem value="compute-engine" label="Compute Engine VMs">