add walkthrough for pv snapshot and restore using aws providers

hack/redirect-history.json

@@ -18,10 +18,16 @@
       "to": "third-party-integrations/git-operations/flux",
       "version": "0.29.0",
       "timestamp": "2025-10-23T08:30:49.815242Z"
+    },
+    {
+      "from": "manage/backup-restore/volume-snapshots",
+      "to": "manage/backup-restore/volume-snapshots/README",
+      "version": "latest",
+      "timestamp": "2025-10-31T07:58:21.031625Z"
     }
   ],
   "metadata": {
     "created": "2025-08-29T18:53:37.644882313Z",
-    "last_updated": "2025-10-23T08:30:49.815249Z"
+    "last_updated": "2025-10-31T07:58:21.031628Z"
   }
 }

hack/test-redirects.hurl

@@ -1,5 +1,5 @@
 # Auto-generated redirect tests
-# Generated: 2025-10-23 08:30:49 UTC
+# Generated: 2025-10-31 07:58:21 UTC
 # Usage: hurl --test --variable BASE_URL=https://www.vcluster.com test-redirects.hurl
 
 # Test: deploy/control-plane/container/flux -> third-party-integrations/git-operations/flux
@@ -17,3 +17,18 @@ header "Location" contains "/docs/vcluster/next/third-party-integrations/git-ope
 GET {{BASE_URL}}/docs/vcluster/third-party-integrations/git-operations/flux/
 HTTP 200
 
+# Test: manage/backup-restore/volume-snapshots -> manage/backup-restore/volume-snapshots/README
+GET {{BASE_URL}}/docs/vcluster/manage/backup-restore/volume-snapshots/
+HTTP 301
+[Asserts]
+header "Location" contains "/docs/vcluster/manage/backup-restore/volume-snapshots/README"
+
+GET {{BASE_URL}}/docs/vcluster/next/manage/backup-restore/volume-snapshots/
+HTTP 301
+[Asserts]
+header "Location" contains "/docs/vcluster/next/manage/backup-restore/volume-snapshots/README"
+
+# Verify destination exists
+GET {{BASE_URL}}/docs/vcluster/manage/backup-restore/volume-snapshots/README/
+HTTP 200
+

netlify.toml

@@ -708,9 +708,11 @@ to = "/docs/vcluster/:version/manage/backup-restore#migrate-and-override-vcluste
 
 
 
+
+
 # AUTO-GENERATED REDIRECTS START
 # Do not edit manually - generated by redirect-resolver
-# Generated: 2025-10-23 08:30:49 UTC
+# Generated: 2025-10-31 07:58:21 UTC
 # All redirects are transitively resolved to prevent redirect chains
 
 [[redirects]]
@@ -728,4 +730,19 @@ to = "/docs/vcluster/:version/manage/backup-restore#migrate-and-override-vcluste
   to = "/docs/vcluster/:splat/third-party-integrations/git-operations/flux"
   status = 301
 
+[[redirects]]
+  from = "/docs/vcluster/manage/backup-restore/volume-snapshots"
+  to = "/docs/vcluster/manage/backup-restore/volume-snapshots/README"
+  status = 301
+
+[[redirects]]
+  from = "/docs/vcluster/next/manage/backup-restore/volume-snapshots"
+  to = "/docs/vcluster/next/manage/backup-restore/volume-snapshots/README"
+  status = 301
+
+[[redirects]]
+  from = "/docs/vcluster/*/manage/backup-restore/volume-snapshots"
+  to = "/docs/vcluster/:splat/manage/backup-restore/volume-snapshots/README"
+  status = 301
+
 # AUTO-GENERATED REDIRECTS END

vcluster/deploy/control-plane/container/environment/eks.mdx

@@ -26,7 +26,7 @@ on [Amazon EKS](https://aws.amazon.com/.).
 
 ## Prerequisites
 
-Before staring, ensure you have the following tools installed:
+Before starting, ensure you have the following tools installed:
 
 - `kubectl` installed: Kubernetes command-line tool for interacting with the cluster. See [Install and Set Up kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) for installation instructions.
 - `vCluster CLI` <InstallCli />

vcluster/manage/backup-restore/volume-snapshots.mdx → vcluster/manage/backup-restore/volume-snapshots/README.mdx

@@ -7,18 +7,20 @@ sidebar_class_name: host-nodes private-nodes
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
-import TenancySupport from '../../_fragments/tenancy-support.mdx';
+import TenancySupport from '../../../_fragments/tenancy-support.mdx';
 
 <TenancySupport hostNodes="true" privateNodes="true" />
 
 :::warning
 This feature is currently in Beta.
-See vCluster [Lifecycle Policy](../../deploy/upgrade/supported_versions#feature-versioning) for more information.
+See vCluster [Lifecycle Policy](../../../deploy/upgrade/supported_versions#feature-versioning) for more information.
 :::
 
 vCluster snapshots enable you to create volume snapshots for PersistentVolumeClaims that are provisioned by CSI drivers. This allows you to protect not only your virtual cluster resources and config, but also your application data.
 
-See [how volume snapshots are created](../../understand/volume-snapshots) if you would like to learn more about volume snapshots and how vCluster creates them.
+See [how volume snapshots are created](../../../understand/volume-snapshots) if you would like to learn more about volume snapshots and how vCluster creates them.
+
+For an example guide demonstrating volume snapshots in action, see this [walkthrough using AWS EBS volumes](./aws-ebs-guide).
 
 :::important
 Volume snapshots can be created only for PVCs that are provisioned by CSI drivers with [Volume Snapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) support.
@@ -31,7 +33,7 @@ In order to create volume snapshots, several installation and configuration step
 ### Host nodes
 
 The following setup has to be done in the host cluster:
-1. Install the [Kubernetes CSI snapshotter](https://github.com/kubernetes-csi/external-snapshotter) and VolumeSnapshot, VolumeSnapshotContent and VolumeSnapshotClass CRDs. You can find further instructions in the upstream repo.
+1. Install the [Kubernetes CSI snapshotter](https://github.com/kubernetes-csi/external-snapshotter) and VolumeSnapshot, VolumeSnapshotContent, and VolumeSnapshotClass CRDs. You can find further instructions in the upstream repo.
 2. Install a CSI driver that supports volume snapshots, and storage classes for that CSI driver.
 3. Configure the default VolumeSnapshotClass for each CSI driver in the host cluster. See [Kubernetes Volume Snapshot Classes docs](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/) for more details.
 
@@ -94,12 +96,12 @@ When taking volume snapshots, there are limitations:
 - Volume snapshots cannot be created for PVCs that are not provisioned by CSI drivers with [Volume Snapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) support.
 - Volume snapshots cannot be created for PVCs that are provisioned by CSI drivers that don't support [Volume Snapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/).
 - When using host nodes:
-  - Currently volume snapshots are created only for PersistentVolumeClaims that are synced to the vCluster host namespace. This means that, when the [Namespace sync](../../configure/vcluster-yaml/sync/to-host/advanced/namespaces) is enabled, volume snapshots are not created for the PersistentVolumeClaims that are synced to namespaces different than the vCluster host namespace.
+  - Currently volume snapshots are created only for PersistentVolumeClaims that are synced to the vCluster host namespace. This means that, when the [Namespace sync](../../../configure/vcluster-yaml/sync/to-host/advanced/namespaces) is enabled, volume snapshots are not created for the PersistentVolumeClaims that are synced to namespaces different than the vCluster host namespace.
 - When using private nodes:
   - vCluster has to be deployed with `deploy.volumeSnapshotController.enabled` config set to `true`.
   - CSI driver that supports volume snapshots has to be installed in the virtual cluster.
   - The default VolumeSnapshotClass has to be configured for each CSI driver in the virtual cluster. See [Kubernetes Volume Snapshot Classes docs](https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/) for more details.
-- Volume snapshots are currently not supported for [vCluster standalone](../../deploy/control-plane/binary/).
+- Volume snapshots are currently not supported for [vCluster standalone](../../../deploy/control-plane/binary/).
 
 
 ## Troubleshoot issues