.default}){kind=icon}
.default}){kind=icon}
✅
|✅
| +| [YAML driven](/support/docs/deep-dive-into-hyperexecute-yaml/) Test orchestration driven. |✅
|✅
| +| [Powerful CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) to trigger tests. |✅
|✅
| +| Real time streaming of Terminal Logs |✅
|✅
| +| Comprehensive Test Artifacts management |✅
|✅
| +| Automated report generation for all testing frameworks. |✅
|✅
| +| User Workflow Management |✅
|✅
| +| Intelligent Test Analytics |✅
|❌
| +| Integration with major [CI/CD platforms and products](/support/docs/integration-with-hyperexecute/) |✅
|✅
| +| Includes all features from LambdaTest's Web + Mobile Automation Plan, along with exclusive HyperExecute benefits |✅
|❌
| +| 24/7 dedicated customer support for uninterrupted assistance. |✅
|✅
| +| Support for custom testing frameworks |❌
|✅
| +| Advanced data retention rules |❌
|✅
| +| Role-Based Access Control (RBAC) support for granular user permissions and security management. |✅
|✅
| +| SSO Support |✅
|✅
| +| Custom test execution environments that are completely managed by LambdaTest |❌
|✅
| +| Access to standard HyperExecute cloud for additional redundancy |NA
|✅
| +| Enhanced Performance and Boosted Security |❌
|✅
| +| Data isolation and region-specific deployment capabilities for enhanced security and compliance. |❌
|✅
| +| Increased Flexibility |❌
|✅
| +| Whitelabled Dashboards |❌
|✅
| *** diff --git a/docs/hyperexecute-private-cloud-on-jumphost.md b/docs/hyperexecute-private-cloud-on-jumphost.md index 25ff17201..97a48409e 100644 --- a/docs/hyperexecute-private-cloud-on-jumphost.md +++ b/docs/hyperexecute-private-cloud-on-jumphost.md @@ -1,7 +1,7 @@ --- id: hyperexecute-private-cloud-on-jumphost title: HyperExecute Private Cloud on JumpHost -hide_title: true +hide_title: false sidebar_label: HyperExecute Private Cloud on JumpHost description: Deploy & run HyperExecute Private Cloud on Azure with JumpHost! Follow our guide for setup, test triggering, and dashboard viewing for a smooth, customizable testing experience. keywords: @@ -36,47 +36,30 @@ slug: hyperexecute-private-cloud-on-jumphost/ }) }} > - -# Using JumpHost to run HyperExecute Private Cloud - -Congratulations on getting the HyperExecute Private setup deployed on your Azure Cloud! - -You can now trigger your test cases and view your dashboard from the JumpHost virtual machine. To understand how to do that, go through the page below. - -*** +Congratulations on getting the HyperExecute Private setup deployed on your Azure Cloud! You can now trigger your test cases and view your dashboard from the JumpHost virtual machine. To understand how to do that, go through the page below. ## Running HyperExecute via a JumpHost VM -1. Log in to your Microsoft Azure account and go to your [homepage](https://portal.azure.com/#home). +**Step 1:** Log in to your Microsoft Azure account and go to your [homepage](https://portal.azure.com/#home)..default})
-***
-
-2. Go to the **search bar** on the top of your screen and search for your managed applications.
+**Step 2:** Go to the **search bar** on the top of your screen and search for your managed applications.
.default})
-***
-
-3. You will be redirected to your managed applications where you can see your installed HyperExecute Private Cloud application. Select the HyperExecute application that you have installed recently.
+**Step 3:** You will be redirected to your managed applications where you can see your installed HyperExecute Private Cloud application. Select the HyperExecute application that you have installed recently.
.default})
-***
-
-4. You will be redirected to a page where you can see all of the resources that are a part of the selected **Managed Resource Group**. Search for a Virtual Machine called `hyex-jump` in this list and open it.
+**Step 4:** You will be redirected to a page where you can see all of the resources that are a part of the selected **Managed Resource Group**. Search for a Virtual Machine called `hyex-jump` in this list and open it.
.default})
-***
-
-5. You can now see the VM details and can use the shown public IP to connect to the virtual machine using the shared credentials over mail.
+**Step 5:** You can now see the VM details and can use the shown public IP to connect to the virtual machine using the shared credentials over mail.
.default})
-***
-
To ensure that you have complete control over your HyperExecute application and your browsers, the virtual machine is completely customizable. You can make the modifications that you require and test all of your applications. Happy testing!
> If you have more questions regarding HyperExecute Private Cloud, reach out to us at [hyperexecute-privatecloudsupport@lambdatest.com](mailto:hyperexecute-privatecloudsupport@lambdatest.com).
diff --git a/docs/hyperexecute-private-cloud-setup-with-aws.md b/docs/hyperexecute-private-cloud-setup-with-aws.md
index 6a11a26cb..f528c6608 100644
--- a/docs/hyperexecute-private-cloud-setup-with-aws.md
+++ b/docs/hyperexecute-private-cloud-setup-with-aws.md
@@ -1,7 +1,7 @@
---
-id: he-aws
-title: How to Setup HyperExecute Private Cloud with AWS
-hide_title: true
+id: hyperexecute-private-cloud-setup-with-aws
+title: How to setup HyperExecute Private Cloud with AWS
+hide_title: false
sidebar_label: Setup with AWS
description: This documentation will help you setup HyperExecute Private Cloud with AWS.
keywords:
@@ -13,99 +13,41 @@ site_name: LambdaTest
slug: hyperexecute-private-cloud-setup-with-aws/
---
-# HyperExecute Deployment on Amazon Marketplace
-
----
-
-One of the biggest challenges developers and testers face is the speed of test execution and the lack of smart test orchestration. But, so far, customers had only two options—depend on traditional cloud-based grids that haven't really innovated to fulfill present demands or build their own in-house infrastructure.
-
-Existing test execution solutions are inherently slow because of lots of network hops that happen during each test, triggered test scenarios are first sent to the automation hub, which in turn are scheduled to run on the best-suited automation node resulting in unnecessary latency. Also, multiple network hops with separated components result in increased test flakiness.
-
-On the other hand, local setups don't have the smart features that can be offered on the cloud. It has always been a trade-off for customers.
-
-## HyperExecute by LambdaTest
-
----
-
-HyperExecute by LambdaTest is a lightning-quick intelligent end-to-end test execution and orchestration platform that is framework and language-agnostic. It is up to 70% faster than any cloud-based test execution grid. HyperExecute reduces developer friction and interrupts and ultimately helps businesses release features/products quicker.
-
-- HyperExecute achieves in-house-like performance by merging all the components into a single execution environment, thereby ensuring all the components 'talk' to each other just like they do in a local network.
-
-- High-performing, highly scalable, and with intelligent features, the platform takes care of executing your tests in the least time possible so that you can focus on crafting your test cases. With smart features such as auto-grouping, auto-retry, and fail-fast mechanisms, HyperExecute takes away all the pain to run tests leaving the developers/testers to focus on other important tasks.
-
-- Through a simple YAML file, HyperExecute allows one to group and distribute tests intelligently across runner environments. This intelligent test orchestration takes into account past test run data, and automatically reorders the test runs to surface failures faster and thus cuts down developer feedback time.
-
-- HyperExecute ensures that all test execution data is available on a single platform, thereby allowing teams to truly analyze the quality of their builds through insightful automatic reports generated for each build run.
-
-HyperExecute's other noteworthy features include artifacts management, automatic tunnel management, customizable test environments, dependency caching, etc.
-
-## Data Processing and Storing by LambdaTest
-
----
-
-LambdaTest processes and stores two categories of data from its Customers while providing LambdaTest Services.
-
-1. **LambdaTest Account data:** The first category of data is any Personally Identifiable Information (PII) other than 'Test execution data' provided by the Customer during the Services. This includes PII related to employees, users, or customer personnel. We refer to this data as 'LambdaTest Account data.' It may include names, email addresses, and contact numbers.
-
-2. **Test execution data:** The second category of data is any information, including PII, that is stored, processed, or transmitted via the LambdaTest platform by, or on behalf of, our Customers. We refer to this data as 'Test execution data.'
-
-The Test execution data consists of the data that our Customers upload to our Platform or that our Platform accesses during the testing of applications. It may include reports, tests, networks, browser process logs, other artifacts, authentication information, licensing information, and test execution metadata (e.g., test status, duration, name, browsing sessions, search history), as well as other information that Customers may provide during testing.
-
-In general, 'Test execution data' refers to data that is stored or processed for the delivery of the Services we provide as a data processor. This data may also include backup storage. It is important to note that 'Test execution data' does not necessarily contain any identifiable PII or sensitive data regarding customer personnel, customers, end-users, or other third parties.
-
-Please note that LambdaTest does not collect, nor does it require, any identifiable PII or sensitive data by default for its functioning.
-
-From a privacy perspective, the customer is considered the controller of Test execution data, while LambdaTest acts as a processor. This means that throughout the time a customer subscribes to services with LambdaTest, the Customer retains ownership of and control over the Test execution data in their account.
-
-'Test execution data' encompasses data stored for the delivery of services we provide as a data processor, including data stored for backup purposes.
-
-### Data to be Processed by LambdaTest while using the HyperExecute Platform
-
-The following data will be processed by LambdaTest when using the HyperExecute Platform:
-
-- **Selenium test data:** This includes selenium logs, Selenium video logs, Selenium test network logs captured from browsers, and selenium process logs. These will be stored on LambdaTest.
-
-- **LambdaTest authentication and Licensing information:** Authentication and licensing information related to LambdaTest will be stored on LambdaTest's platform to control the test concurrency.
-
-- **Web browsers and selenium drivers:** LambdaTest curates and stores publicly available web browsers and selenium drivers in their public storage. The HyperExecute environment for customers will regularly download these web browsers and selenium drivers from LambdaTest's public storage.
-
-- **Test execution metadata:** Metadata related to test execution, such as test status, duration, and name, will be stored on LambdaTest's servers. This data is used to power dashboards for customers, providing insights into test execution.
-
-- **Alerts from HyperExecute services:** HyperExecute services running inside the customer's environment may send alerts to LambdaTest in case of failures. These alerts will not contain any critical or sensitive details. The data sent will include information such as error type, service, and time. This data is used to provide prompt technical support to the customer.
-
-- **Software updates:** LambdaTest will roll out frequent software updates for the HyperExecute Platform. Customers can apply these updates at their convenience.
-
-- **Customer's critical data:** All critical data, including test scripts, terminal logs, and test dependencies, will remain within the customer's environment and will not leave their perimeter. LambdaTest does not process or store this data.
-
-Please note that LambdaTest prioritizes data privacy and security and ensures that sensitive customer data remains protected and within the customer's control.
-
-### Data Deletion Process
-
-LambdaTest follows the following data deletion process:
-
-1. All test execution data from the executed virtual machines (VMs) is deleted as soon as the test is completed. This means that each time a test is run, a new clean and sanitized machine is used, and the VM where the test was executed is deleted immediately after the test ends.
-
-2. LambdaTest stores encrypted test execution result data, including logs, videos, and screenshots, that are generated during test runs on LambdaTest's platform. By default, this data is retained for 60 days.
-
-3. Customers have the ability to request the deletion of all data corresponding to a person. This can be done by contacting LambdaTest via email and explicitly requesting the deletion. LambdaTest aims to process such requests within a turnaround time of 48 hours.
-
-LambdaTest prioritizes data privacy and provides mechanisms for data deletion to ensure compliance with data protection regulations and to meet customer requirements.
-
-## Deployment with the AWS Marketplace Offer
-
----
-
-### Prerequisites
+
+
+## Prerequisites
Before deploying the CloudFormation template for HyperExecute through the AWS Marketplace, ensure that the following prerequisites are met:
-1. **Region with min 3 availability zones**: Make sure you are running the CloudFormation in a region that supports a minimum of 3 availability zones. The currently supported regions are us-east-1, us-east-2, us-west-2, eu-central-1, ap-south-1, and ap-southeast-2.
+1. **Region with min 3 availability zones**: Make sure you are running the CloudFormation in a region that supports a minimum of 3 availability zones. The currently supported regions are `us-east-1`, `us-east-2`, `us-west-2`, `eu-central-1`, `ap-south-1`, and `ap-southeast-2`.
2. **Elastic IPs (EIPs)**: HyperExecute requires 3 Elastic IPs for each availability zone (AZ). Ensure that you have sufficient quota for EIPs in your AWS account. You can refer to the [EIP Limits](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-limit) to check your quota.
3. **EC2 quota limits**: The CloudFormation template will create EC2 instances as part of a Managed NodeGroup, with a minimum requirement of 5 nodes, and an Auto Scaling Group with a maximum size based on your concurrency license. Make sure to increase your [EC2 quota](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html) limits accordingly.
-### Steps to Deploy
+## Steps to Deploy
To deploy the CloudFormation template on AWS, follow these steps:
@@ -131,7 +73,7 @@ By following these steps, you can deploy the HyperExecute CloudFormation templat
.default})
-### Configuration Parameters
+## Configuration Parameters
Please provide the following configuration details based on the type of installation you want to perform:
@@ -185,8 +127,6 @@ In the Other Configuration, provide the following details as required:
## Accessing HyperExecute after deployment
----
-
Once the CloudFormation template is successfully deployed, you can access HyperExecute and perform the following steps:
**Step 1:** Login into the EC2 instance named "**HyperExecute-Admin-Bastion**" using either SSM (Session Manager) or the SSH key provided in the Configuration Parameters. Note that SSH access is allowed by default within the VPC.
@@ -225,24 +165,22 @@ Once the CloudFormation template is successfully deployed, you can access HyperE
**Step 7:** Login using your email and password and run jobs using the HyperExecute CLI. For further details about HyperExecute, refer to the [documentation](https://www.lambdatest.com/support/docs/getting-started-with-hyperexecute/).
-## Cleanup the environment
-
----
+## Cleanup the Environment
If you wish to clean up the resources created during the deployment, follow these steps:
-1. Ensure that the objects inside the S3 bucket created by the CloudFormation template with the name `${AWS::StackName}-${AWS::AccountId}-hyperexecute-bucket` are deleted before the bucket can be deleted.
+**Step 1 :** Ensure that the objects inside the S3 bucket created by the CloudFormation template with the name `${AWS::StackName}-${AWS::AccountId}-hyperexecute-bucket` are deleted before the bucket can be deleted.
-2. Delete the images in the ECR (Elastic Container Registry) repository with the name `${ManagedAppName}-hyperexecute-private-cloud` before deleting the repository.
+**Step 2 :** Delete the images in the ECR (Elastic Container Registry) repository with the name `${ManagedAppName}-hyperexecute-private-cloud` before deleting the repository.
-3. Delete the root stack from CloudFormation. This will delete all the nested stacks and their resources.
+**Step 3 :** Delete the root stack from CloudFormation. This will delete all the nested stacks and their resources.
-4. CloudWatch log groups are not deleted by default. Manually navigate to CloudWatch and delete the log groups starting with the following regex patterns:
+**Step 4 :** CloudWatch log groups are not deleted by default. Manually navigate to CloudWatch and delete the log groups starting with the following regex patterns:
- `/aws/lambda/*-ClusterCreatorFunction-*`
- `/aws/lambda/*-ClusterOIDCURLFunction-*`
- `/aws/lambda/*-HyePrivateCloudFunction-*`
- `/aws/containerinsights/${ManagedAppName}-hyperexecute-eks-cluster/*`
-5. If you have used the secrets feature in HyperExecute, the secrets with the regex pattern `hyperexecute-secrets-*` will not be deleted. Manually navigate to AWS Secret Manager and delete the secrets.
+**Step 5 :** If you have used the secrets feature in HyperExecute, the secrets with the regex pattern `hyperexecute-secrets-*` will not be deleted. Manually navigate to AWS Secret Manager and delete the secrets.
Make sure to follow these cleanup steps to remove the resources associated with the HyperExecute deployment.
diff --git a/docs/hyperexecute-private-cloud-setup-with-azure.md b/docs/hyperexecute-private-cloud-setup-with-azure.md
index 5eee1f49a..c09c9d5d2 100644
--- a/docs/hyperexecute-private-cloud-setup-with-azure.md
+++ b/docs/hyperexecute-private-cloud-setup-with-azure.md
@@ -1,7 +1,7 @@
---
id: hyperexecute-private-cloud-setup-with-azure
title: HyperExecute Private Cloud Setup with Azure
-hide_title: true
+hide_title: false
sidebar_label: HyperExecute Private Cloud Setup with Azure
description: Discover HyperExecute Private Cloud Setup with Azure and understand how to inherit configurations for optimal performance. Explore the integration of hyperexecute inherit config.
keywords:
@@ -36,42 +36,20 @@ slug: hyperexecute-private-cloud-setup-with-azure/
})
}}
>
-
-# HyperExecute Private Cloud Setup with Azure
-
-HyperExecute Private Cloud is now available on the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/lambdatestinc1584019832435.hyperexeonprem?tab=Overview).
-
-Follow the steps below to understand how to setup **HyperExecute Private Cloud** via the Azure Marketplace.
+Follow the steps below to understand how to setup **HyperExecute Private Cloud** via the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/lambdatestinc1584019832435.hyperexeonprem?tab=Overview).
## Prerequisites
-1. **Resource Provider**
- The following resource providers must be registered to install HyperExecute successfully. If you do not have them registered, follow the steps on this [page](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types).
-
- - Microsoft.Compute
-
- - Microsoft.OperationsManagement
-
-
-2. **'EnablePodIdentityPreview` Preview feature**
-
- - We use AAD Pod Identity feature to enable Kubernetes applications to access cloud resources securely with Azure Active Directory.
+1. **Resource Provider :** The following resource providers must be registered to install HyperExecute successfully. If you do not have them registered, follow the steps on this [page](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types); `Microsoft.Compute`, `Microsoft.OperationsManagement`
- - To use this feature(preview), we need to register the `EnablePodIdentityPreview` feature. If you haven’t registered this feature, follow the steps on this [page](https://learn.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity).
-
-
-3. **CPU Quotas**
- In order to successfully deploy HyperExecute, we need to increase VM-family vCPU quotas. If you want to increase the quotas of your VM-family vCPU, follow the steps on this [page](https://learn.microsoft.com/en-us/azure/quotas/per-vm-quota-requests).
-
+2. **CPU Quotas :** In order to successfully deploy HyperExecute, we need to increase VM-family vCPU quotas. If you want to increase the quotas of your VM-family vCPU, follow the steps on this [page](https://learn.microsoft.com/en-us/azure/quotas/per-vm-quota-requests).
+
- Standard DSv3 Family vCPUs. vCPU core count - 80
-
- Standard FSv2 Family vCPUs. vCPU core count - 8 * number of parallel licenses.
-4. **Dedicated Resource Group.**
+3. **Dedicated Resource Group.**
-5. A user with Admin Access who would be running the ARM script as certain resources like resource group, UAMI and related operations would require elevated access for creation.
-
-6. Enablements on Preview features of **Pod Identity**
+4. A user with Admin Access who would be running the ARM script as certain resources like resource group, UAMI and related operations would require elevated access for creation.
## IP Ranges
By default the setup creates its own network with IP range `10.26.0.0/16`. if in case the customer needs customised environment than minimum 2 subnets are required to accommodate the resources.
@@ -85,63 +63,35 @@ By default the setup creates its own network with IP range `10.26.0.0/16`. if in
**Step 1:** Sign in to your Azure Marketplace account. Alternatively, you can create a new account if you don’t already have one.
-**Step 2:** You can access the HyperExecute Private Cloud in two ways, by searching for it on Azure Marketplace, or by directly accessing the [HyperExecute’s Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/lambdatestinc1584019832435.hyperexeonprem?exp=ubp8&tab=Overview) listing.
-
-- Go on [HyperExecute’s Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/lambdatestinc1584019832435.hyperexeonprem?exp=ubp8&tab=Overview) listing, and click on **Get It Now**.
+**Step 2:** You can access the HyperExecute Private Cloud in two ways, by searching for it on Azure Marketplace, or by directly accessing the [HyperExecute’s Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/lambdatestinc1584019832435.hyperexeonprem?tab=Overview) listing and click on **Get It Now** button.
-.default})
+
- Fill your details in the pop-up, and select a plan between **HyperExecute Private Cloud - Monthly** or **HyperExecute Private Cloud - Annual**. Click on **Continue** to proceed.
-.default})
-
-- Alternatively, you can also search for HyperExecute from the search bar on Azure Marketplace’s homepage.
-
-.default})
-
-- Click on the **Get It Now** button on the **HyperExecute Private Cloud** listing.
-
-.default})
-
-- Select a plan between **HyperExecute Private Cloud - Monthly** or **HyperExecute Private Cloud - Annual**. Click on **Continue** to proceed.
-
-.default})
+
**Step 3:** You will be redirected to HyperExecute Private Cloud listing page. Click on **Create** to proceed.
-.default})
-
-**Step 4:** You will be redirected to the **Basics** page where you have to configure your plan for **HyperExecute Private Cloud.**
-
-.default})
-
-**Step 5:** Configure the fields as per your requirements, and click on **Review + create** to proceed further.
+
-.default})
+**Step 4:** You will be redirected to the **Basics** page where you have to configure your plan for **HyperExecute Private Cloud.** Configure the fields as per your requirements, and click on **Review + create** to proceed further.
- **Subscription**: The Azure subscription where the resource will be billed.
-
- **Resource Group**: Choose a unique name for this new [Resource group](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group), or allot it to an older resource group of your choice.
-
- **Select Location**: Select the location where you want to deploy HyperExecute Private Cloud.
-
- **App Insight Retention Period**: Select the retention period for [application insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview?tabs=net) (in this case HyperExecute Private Cloud) in days.
-
- **Email ID**: The Email ID associated with your Azure account.
-
- **Select Parallel Tests**: The number of parallel test executions that you need. You can also check HyperExecute’s pricing plans by clicking on the link below the field.
-
- **Managed Application Name**: Choose a unique name for your application.
-
- **Ingress Type**: Choose between **Private** or **Public** to determine if you want a private endpoint or a public endpoint.
-
- **Managed Resource Group**: This field will be automatically filled, and you do not need to change it.
-**Step 6:** You can review all of your entries and then select the checkbox under **Co-Admin Access Permission**, indicating that you agree to the **Terms and Conditions** listed above.
+
-.default})
+**Step 5:** You can review all of your entries and then select the checkbox under **Co-Admin Access Permission**, indicating that you agree to the **Terms and Conditions** listed above. Click on **Create** and you will have successfully set up the HyperExecute Private Cloud.
-**Step 7:** Click on **Create** and you will have successfully set up the HyperExecute Private Cloud.
+
## Running HyperExecute Private Cloud
diff --git a/docs/playwright-bundled-browser-support.md b/docs/playwright-bundled-browser-support.md
index c6e82bf69..5ee15760e 100644
--- a/docs/playwright-bundled-browser-support.md
+++ b/docs/playwright-bundled-browser-support.md
@@ -52,9 +52,9 @@ const capabilities = { "LT:Options": {"useSpecificBundleVersion": true,}}
| Playwright Versions | Chromium | Firefox | Webkit |
|---------------------|----------|---------|--------|
-|1.50| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0-18.2 |
-|1.49| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0-18.2 |
-|1.48| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0-18.2 |
+|1.50| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0, 18.2 |
+|1.49| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0, 18.2 |
+|1.48| 130-133 except - 132, 126, 122 | 130-134, except - 131,133,126,122,120 | 18.0, 18.2 |
|1.47| 129 except - 132, 126, 122 | 130, except - 131,133,126,122,120 | 18.0 |
|1.46| 119-133, except - 132, 126, 122 | 118-134, except - 131,133, 126,122,120 | 17.4, 18.2 |
|1.45| 119-127, except - 126,122 | 119-127, except - 126,122,120 | 17.4 |
diff --git a/sidebars.js b/sidebars.js
index 33a1b7e9c..78733db20 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -663,7 +663,7 @@ module.exports = {
{
type: "doc",
label: "Setup with AWS",
- id: "he-aws",
+ id: "hyperexecute-private-cloud-setup-with-aws",
},
],
},