Skip to content

docs: add note about ports restore for persisted services #290

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

Merged
merged 1 commit into from
Oct 23, 2025
Merged

docs: add note about ports restore for persisted services #290

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions src/content/docs/aws/capabilities/state-management/persistence.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,14 @@ Although we are working to support both snapshot-based persistence and Cloud pod
there are some common issues, known limitations, and also services that are not well tested for persistence support.
An overview is available [here](#persistence-coverage-overview).

:::note
When using LocalStack's persistence feature, ports assigned to services (like RDS or Elasticache) when the snapshot was created may not be preserved when loading a saved state.
If you start new services *before* restoring the previous state, these new instances may use ports originally used by the saved services.

As a result, restored resources may point to invalid or unintended ports.
It is suggested to estore services in the same order as initially deployed, though this is not always reliable.
:::

Please help us improve persistence support by reporting bugs on our [GitHub issue tracker](https://github.com/localstack/localstack/issues/new/choose).

## Technical Details
Expand Down