Fix snapshot support details

- **AWS page**: `snapshot` content inlined natively (it's no longer shared with anything, so the component was folded back in and deleted) — kept full Cloud Pods/S3/local support, dropped the inaccurate "also works experimentally on Snowflake/Azure" note.
- **Azure page**: removed `snapshot`/`reset` entirely, added a short note pointing to `--persist` as the only state-retention option, and fixed the Introduction paragraph, which previously claimed Cloud Pod support.
- **Snowflake page**: replaced the shared component with a native `snapshot` section scoped to local files only — no `pod:` refs, no S3 remotes, no `list`/`remove`/`show` (all Cloud-Pod-only) — kept the "experimental" warning since that's specifically about local save/load, and fixed its Introduction paragraph too.
- Annotated the global `--snapshot`/`--no-snapshot` flags as AWS-only in `GlobalOptionsAndOutput.mdx` for consistency.

Author: remotesynth

src/components/lstk/GlobalOptionsAndOutput.mdx

@@ -8,8 +8,8 @@ These options are available for all commands:
 | `--non-interactive` | Disable the interactive TUI, use plain output                              |
 | `--json`            | Emit a single machine-readable JSON envelope on stdout instead of human-oriented output. Supported by `stop`, `reset`, and `update`; any other command rejects it. See [Structured output](#structured-output). |
 | `--persist`         | Persist emulator state across restarts (on `start`/bare `lstk` and `restart`) |
-| `--snapshot <REF>`  | Snapshot REF to auto-load after start (on `start`/bare `lstk`; overrides config for one run) |
-| `--no-snapshot`     | Skip auto-loading the configured snapshot (on `start`/bare `lstk`)          |
+| `--snapshot <REF>`  | Snapshot REF to auto-load after start (on `start`/bare `lstk`; overrides config for one run). AWS emulator only. |
+| `--no-snapshot`     | Skip auto-loading the configured snapshot (on `start`/bare `lstk`). AWS emulator only. |
 | `-v`, `--version`   | Print the version and exit                                                 |
 | `-h`, `--help`      | Print help and exit                                                        |
 

src/components/lstk/SnapshotCommands.mdx

@@ -12,7 +12,6 @@ import QuickStart from '@/components/lstk/QuickStart.mdx';
 import Authentication from '@/components/lstk/Authentication.mdx';
 import Configuration from '@/components/lstk/Configuration.mdx';
 import LifecycleCommands from '@/components/lstk/LifecycleCommands.mdx';
-import SnapshotCommands from '@/components/lstk/SnapshotCommands.mdx';
 import CommonCommands from '@/components/lstk/CommonCommands.mdx';
 import GlobalOptionsAndOutput from '@/components/lstk/GlobalOptionsAndOutput.mdx';
 import EnvironmentAndLogging from '@/components/lstk/EnvironmentAndLogging.mdx';
@@ -151,7 +150,163 @@ Like `lstk aws`, the `terraform`, `cdk`, and `sam` proxies do not start the emul
 Each requires the corresponding third-party CLI to be installed and on your `PATH`.
 :::
 
-<SnapshotCommands />
+### `snapshot`
+
+Manage emulator snapshots.
+A snapshot captures the running AWS emulator's state, either as a local file on disk, as a Cloud Pod on the LocalStack platform, or in your own S3 bucket.
+The `snapshot` command groups five subcommands — `save`, `load`, `list`, `remove`, and `show`. The first two are also exposed as the top-level aliases `lstk save` and `lstk load`.
+
+:::note
+Cloud Pods and S3 remotes are **AWS-only**. Snapshots are not currently supported for the Snowflake or Azure emulators through `lstk`.
+`reset` is also **AWS-only** and errors out with `reset is only supported for the AWS emulator` otherwise.
+:::
+
+#### `snapshot save`
+
+Save a snapshot of the running emulator's state.
+The emulator must already be running; this command does **not** auto-start it.
+
+```bash
+# Auto-named snapshot file in the current directory
+lstk snapshot save
+
+# Save to a specific local path
+lstk snapshot save ./my-snapshot
+
+# Save to a Cloud Pod on the LocalStack platform (requires auth)
+lstk snapshot save pod:my-baseline
+
+# Save to your own S3 bucket (pod name is auto-generated if omitted)
+lstk snapshot save my-pod s3://my-bucket/prefix
+```
+
+The optional `[destination]` argument takes one of these forms:
+
+| Destination                     | Description                                                                                     |
+|:--------------------------------|:------------------------------------------------------------------------------------------------|
+| (omitted)                       | Auto-generates a timestamped snapshot file in the current directory (`./snapshot-<timestamp>-<hex>.snapshot`). |
+| local path                      | Writes a snapshot archive to that path. The `.snapshot` extension is forced.                     |
+| `pod:<name>`                    | Saves a Cloud Pod to the LocalStack platform. Requires authentication.                           |
+| `<pod-name> s3://bucket/prefix` | Saves to your own S3 bucket. The pod name is a separate positional (auto-generated when omitted). See [S3 remotes](#s3-remotes). |
+
+Pod operations require an auth token (`LOCALSTACK_AUTH_TOKEN` or a prior `lstk login`); local-file snapshots do not.
+
+| Option              | Description                                                                                   |
+|:--------------------|:----------------------------------------------------------------------------------------------|
+| `--profile <name>`  | AWS profile to read S3 credentials from (used only for `s3://` destinations). Defaults to `AWS_*` env vars, then `AWS_PROFILE`. |
+
+#### `snapshot load`
+
+Load a snapshot into the emulator, **auto-starting it first** if it is not already running.
+
+```bash
+# Load a local snapshot by path or name
+lstk snapshot load my-baseline
+lstk snapshot load ./checkpoint
+
+# Load from a Cloud Pod (requires auth)
+lstk snapshot load pod:my-baseline
+
+# Load from your own S3 bucket (pod name is required)
+lstk snapshot load my-pod s3://my-bucket/prefix
+
+# Control how the snapshot merges with running state
+lstk snapshot load pod:my-baseline --merge=overwrite
+```
+
+The `REF` argument is required and identifies a local path/name or a `pod:<name>` Cloud Pod.
+To load from S3, pass the pod name followed by an `s3://bucket/prefix` location (see [S3 remotes](#s3-remotes)).
+
+| Option               | Description                                                                                              |
+|:---------------------|:--------------------------------------------------------------------------------------------------------|
+| `--merge <strategy>` | How the loaded state combines with running state. One of `account-region-merge` (default), `overwrite`, `service-merge`. |
+| `--profile <name>`   | AWS profile to read S3 credentials from (used only for `s3://` sources). Defaults to `AWS_*` env vars, then `AWS_PROFILE`. |
+
+- `account-region-merge` (default): the snapshot wins on any `(service, account, region)` overlap.
+- `overwrite`: running state is reset first, then the snapshot is imported onto a clean state.
+- `service-merge`: the snapshot wins per resource; non-overlapping resources are combined.
+
+The aliases behave identically:
+
+```bash
+lstk save pod:my-baseline
+lstk load ./checkpoint
+```
+
+#### `snapshot list`
+
+List the Cloud Pod snapshots available on the LocalStack platform.
+By default, only snapshots you created are listed; pass `--all` to include every snapshot in your organization.
+This subcommand operates on Cloud Pods, so it requires authentication.
+
+```bash
+# Snapshots you created
+lstk snapshot list
+
+# Every snapshot in your organization
+lstk snapshot list --all
+
+# List snapshots in your own S3 bucket (requires a running emulator)
+lstk snapshot list s3://my-bucket/prefix
+```
+
+Passing an `s3://bucket/prefix` location lists snapshots stored in your own S3 bucket instead of the platform (see [S3 remotes](#s3-remotes)). Unlike the platform listing, this queries the emulator, so it requires a running emulator.
+
+| Option             | Description                                                  |
+|:-------------------|:-------------------------------------------------------------|
+| `--all`            | List all snapshots in your organization, not just your own.  |
+| `--profile <name>` | AWS profile to read S3 credentials from (used only with an `s3://` location). Defaults to `AWS_*` env vars, then `AWS_PROFILE`. |
+
+#### `snapshot remove`
+
+Delete a Cloud Pod snapshot from the LocalStack platform.
+Only cloud snapshots (the `pod:` prefix) can be removed; local snapshots are plain files you delete yourself.
+This operation cannot be undone.
+
+```bash
+lstk snapshot remove pod:my-baseline
+
+# Skip the confirmation prompt (required in non-interactive mode)
+lstk snapshot remove pod:my-baseline --force
+```
+
+The required `REF` argument must be a `pod:<name>` Cloud Pod reference.
+
+| Option    | Description                                                            |
+|:----------|:------------------------------------------------------------------------|
+| `--force` | Skip the confirmation prompt. Required when running non-interactively. |
+
+#### `snapshot show`
+
+Show metadata for a single Cloud Pod snapshot on the LocalStack platform: its name, created date, size, LocalStack version, message, the services it contains, and per-service resource counts (resource counts render only when the platform has them for that snapshot).
+This subcommand is cloud-only and requires authentication.
+
+```bash
+lstk snapshot show pod:my-baseline
+```
+
+The required `REF` argument must be a `pod:<name>` Cloud Pod reference.
+
+#### S3 remotes
+
+`snapshot save`, `load`, and `list` can target a snapshot stored in your **own S3 bucket** by passing an `s3://bucket/prefix` location.
+The pod name (the snapshot's identity within the bucket) is a positional separate from the `s3://` location — required for `load`, auto-generated for `save` when omitted, and unused for `list`.
+
+```bash
+lstk snapshot save my-pod s3://my-bucket/prefix
+lstk snapshot load my-pod s3://my-bucket/prefix
+lstk snapshot list s3://my-bucket/prefix
+```
+
+Credentials follow AWS CLI precedence: `--profile <name>` wins, otherwise the static `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` (plus optional `AWS_SESSION_TOKEN`) environment variables, otherwise the profile named by `AWS_PROFILE`.
+Only static credentials are supported (no SSO, assume-role, or `credential_process`), and credentials must never be embedded in the URL.
+
+`lstk` runs a pre-flight check that the target bucket exists and errors out rather than letting the emulator auto-create a bucket on a typo.
+Because the transfer is performed by the emulator (not the CLI), S3 remotes require a **running emulator**, and `list s3://…` in particular queries the emulator rather than the platform API.
+
+:::note
+`remove` and `show` do not support S3; they operate on Cloud Pods only.
+:::
 
 ### `reset`
 

src/content/docs/aws/developer-tools/running-localstack/lstk.mdx

@@ -11,7 +11,6 @@ import QuickStart from '@/components/lstk/QuickStart.mdx';
 import Authentication from '@/components/lstk/Authentication.mdx';
 import Configuration from '@/components/lstk/Configuration.mdx';
 import LifecycleCommands from '@/components/lstk/LifecycleCommands.mdx';
-import SnapshotCommands from '@/components/lstk/SnapshotCommands.mdx';
 import CommonCommands from '@/components/lstk/CommonCommands.mdx';
 import GlobalOptionsAndOutput from '@/components/lstk/GlobalOptionsAndOutput.mdx';
 import EnvironmentAndLogging from '@/components/lstk/EnvironmentAndLogging.mdx';
@@ -25,7 +24,7 @@ import TroubleshootingCommon from '@/components/lstk/TroubleshootingCommon.mdx';
 It provides a built-in terminal UI (TUI) for interactive use and plain text output for CI/CD pipelines and scripting.
 
 `lstk` handles the full emulator lifecycle: authentication, pulling the Docker image, starting, stopping, and restarting the container, streaming logs, and checking status.
-It can also save and load emulator state (as local snapshots or Cloud Pods) and manage the on-disk volume.
+It can also persist emulator state across restarts and manage the on-disk volume.
 Running `lstk` with no arguments takes you through the entire startup flow automatically.
 
 `lstk` also proxies the Azure CLI (`lstk az`) so it runs directly against the Azure emulator.
@@ -87,7 +86,9 @@ Like the other CLI proxies, `lstk az` does not start the emulator — start it f
 It requires the `az` CLI to be installed and on your `PATH`.
 :::
 
-<SnapshotCommands />
+:::note
+`lstk` does not currently support `snapshot` or `reset` for the Azure emulator — those commands are AWS-only. `lstk start --persist` is the only state-retention option available.
+:::
 
 <CommonCommands />