Revamp Snapshots section: major restructuring (largely by hand), and support for lstk - #800
Conversation
Deploying localstack-docs with
|
| Latest commit: |
78ca32f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1b88df15.localstack-docs.pages.dev |
| Branch Preview URL: | https://pro-275-rewrite-snapshots-se.localstack-docs.pages.dev |
3d31485 to
b0fb87d
Compare
e508757 to
9caeb99
Compare
lstk
…o other pages yet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…itch documented commands to the lstk CLI Move the Remotes section from cloud-pods.mdx into other-snapshot-storage-options.md, and the (now Snapshot Merging) section into save-snapshots-locally.md. Update save-snapshots-locally.md to document the lstk snapshot save/load commands instead of the legacy localstack CLI, and fix inbound links to the relocated sections across the docs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Work in progress towards rewriting cloud-pods.mdx around the lstk CLI's snapshot commands instead of the legacy localstack pod CLI, plus a new workflow diagram and a remotes miscellaneous note. Not yet complete (contains a TBD placeholder). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Renames several cloud-pods.mdx headings to better distinguish the Cloud Pod (the repository) from the snapshot (the saved emulator state), fixes the one cross-doc link that referenced the old heading anchor, and cleans up assorted grammar/typo/consistency issues found in a pass over the page (subject-verb agreement, singular/plural Cloud Pod references, a broken image markdown tag, a directory-name typo, and stale export/import wording left over after the heading renames).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Delete launchpad.md and its images, drop the dead card link from the Snapshots overview, and repoint legacy launchpad redirects to the Snapshots overview page instead of the now-removed page. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
48c85bf to
39fb0fa
Compare
Rebuild the "Using the lstk CLI" section around a single worked example that builds a Cloud Pod over three versions, adding one service at a time (S3, then SQS, then SNS). Document the `snapshot versions` command and loading a specific version with the `:<version>` suffix. All command output in the section is captured from a real run against a fresh emulator, with the LocalStack version normalised to 2026.8.0. Also remove the End-to-End Encryption section, which is no longer part of this page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
| ``` | ||
|
|
||
| More information about state import and export [here](/aws/developer-tools/snapshots/export-import-state). | ||
| More information about state import and export [here](/aws/developer-tools/snapshots/saving-snapshots-locally). |
There was a problem hiding this comment.
| More information about state import and export [here](/aws/developer-tools/snapshots/saving-snapshots-locally). | |
| More information about state import and export [here](/aws/developer-tools/snapshots/cloud-pods/). |
Given the example above this is using the Cloud Pod backend, should we link to the cloud pods page instead?
| - **License activation**: The standard image performs online activation using your `LOCALSTACK_AUTH_TOKEN`. See [Auth Token](/aws/getting-started/auth-token) for activation behavior and fallbacks. | ||
| - **Event reporting (telemetry)**: Used for Stack Insights and related usage analytics. You can disable this via `DISABLE_EVENTS=1`. | ||
| - **Cloud Pods (platform remote)**: Saving/loading pods against the default platform remote uses LocalStack-managed infrastructure. For stricter data residency, configure your own Cloud Pods [remote storage](/aws/developer-tools/snapshots/cloud-pods#remotes). | ||
| - **Cloud Pods (platform remote)**: Saving/loading pods against the default platform remote uses LocalStack-managed infrastructure. For stricter data residency, consider other [remote storage options](/aws/developer-tools/snapshots/saving-snapshots-to-s3). |
There was a problem hiding this comment.
LocalStack-managed infrastructure
This probably goes beyond the the scope of this PR, but I wonder if it's worth mentioning somewhere in our docs the region in which the LocalStack platform (Console + hosted resources like CloudPods and Ephem Instances) is hosted (e.g. eu-central-1?). From my experience, enterprises like to know this and it can help them think about which Snapshot backend is right for them. Perhaps we could add a note on this page: https://docs.localstack.cloud/aws/connecting/console/ and then link to it from here, Cloud Pods page, and Ephemeral Instances page.
| /user-guide/aws/cloudfront/ /aws/services/cloudfront/ 301 | ||
| /applications/note-taking-application-using-aws-sdk-for-javascript/ https://github.com/localstack-samples/sample-notes-app-dynamodb-lambda-apigateway 301 | ||
| /user-guide/state-management/export-import-state/ /aws/developer-tools/snapshots/export-import-state/ 301 | ||
| /user-guide/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /user-guide/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /user-guide/state-management/export-import-state/ /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /user-guide/aws/cloudfront /aws/services/cloudfront/ 301 | ||
| /applications/note-taking-application-using-aws-sdk-for-javascript https://github.com/localstack-samples/sample-notes-app-dynamodb-lambda-apigateway 301 | ||
| /user-guide/state-management/export-import-state /aws/developer-tools/snapshots/export-import-state/ 301 | ||
| /user-guide/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /user-guide/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /user-guide/state-management/export-import-state /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/capabilities/state-management/export-import-state/ /aws/developer-tools/snapshots/export-import-state/ 301 | ||
| /aws/capabilities/state-management/cli-commands /aws/developer-tools/running-localstack/lstk/#snapshot 301 | ||
| /aws/capabilities/state-management/cli-commands/ /aws/developer-tools/running-localstack/lstk/#snapshot 301 | ||
| /aws/capabilities/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/capabilities/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/capabilities/state-management/export-import-state /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/capabilities/state-management/cli-commands /aws/developer-tools/running-localstack/lstk/#snapshot 301 | ||
| /aws/capabilities/state-management/cli-commands/ /aws/developer-tools/running-localstack/lstk/#snapshot 301 | ||
| /aws/capabilities/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | ||
| /aws/capabilities/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/capabilities/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/capabilities/state-management/export-import-state/ /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/capabilities/state-management/ /aws/developer-tools/snapshots/ 301 | ||
| /aws/capabilities/state-management/launchpad /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/capabilities/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/developer-tools/snapshots/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/developer-tools/snapshots/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/developer-tools/snapshots/export-import-state /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/capabilities/state-management/launchpad /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/capabilities/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/developer-tools/snapshots/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | ||
| /aws/developer-tools/snapshots/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/developer-tools/snapshots/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/developer-tools/snapshots/export-import-state/ /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/configuration/state-management/export-import-state/ /aws/developer-tools/snapshots/export-import-state/ 301 | ||
| /aws/configuration/state-management/launchpad /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/configuration/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/configuration/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/configuration/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/configuration/state-management/export-import-state /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
| /aws/configuration/state-management/launchpad /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/configuration/state-management/launchpad/ /aws/developer-tools/snapshots/launchpad/ 301 | ||
| /aws/configuration/state-management/export-import-state /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | ||
| /aws/configuration/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 |
There was a problem hiding this comment.
| /aws/configuration/state-management/export-import-state/ /aws/developer-tools/snapshots/save-snapshots-locally/ 301 | |
| /aws/configuration/state-management/export-import-state/ /aws/developer-tools/snapshots/saving-snapshots-locally/ 301 |
|
|
||
| <PersistenceCoverage client:load /> | ||
|
|
||
| ### Terminology |
There was a problem hiding this comment.
should this section carry over to the Service Coverage page, given we moved the PersistenceCoverage table there?
|
|
||
| Please help us improve persistence support by reporting bugs on our [GitHub Discussion](https://github.com/orgs/localstack/discussions/new/choose). | ||
|
|
||
| ## Technical Details |
There was a problem hiding this comment.
Looks like this section didn't get carried over to Service Coverage page. Was that on purpose?
Migrate the entire "Snapshots" section to use
lstk, and perform major restructuring on the existing content.The Snapshots section had grown organically around Cloud Pods and the legacy
localstackCLI. Content had been added over time, in a way that didn't make sense to many readers I talked with. In addition to migrating tolstk, we needed to rethink how the content was structured, making it far easier for novice readers to understand the important concepts.This change restructures the section around the user's actual goal — where do I want to put my snapshot? — and moves every example to
lstk.Note that most of this work was done by Peter, using AI as an assistant. I reviewed all the content, made conscious decisions about how it should be restructured, and wrote many of the paragraphs myself. In many cases it was easier to write it myself, than to instruct Claude on what should have been written. In the end, Claude was great for testing examples and sanity-testing my grammar.
What changed
Page structure — one page per destination, ordered as a reading path:
Removed
cli-commands.md(now covered by thelstkCLI guide),launchpad.md(no longer works), andexport-import-state.md(replaced by "saving locally").