Skip to content

Updating AS page to make it better for schedule-based options #11802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joeyouss wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Updating AS page to make it better for schedule-based options #11802

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c8d4ed5
Updating AS page to make it better for schedule-based options
joeyouss Nov 10, 2025
0a7f247
fixing nits
joeyouss Nov 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/cloud-cost-management/content/auto-stopping/aws-as.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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**.


Expand Down Expand Up @@ -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">
Expand Down
8 changes: 6 additions & 2 deletions docs/cloud-cost-management/content/auto-stopping/azure-as.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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.

Expand Down
12 changes: 9 additions & 3 deletions docs/cloud-cost-management/content/auto-stopping/gcp-as.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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
Expand Down Expand Up @@ -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">
Expand Down