Skip to content
← Back to activity

Immutable solution version

RDS restores always create a new instance, never restore in place

Version 3Sign in to save

Complete solution

Shows how to fix rDS restores always create a new instance, never restore in place. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

After any RDS restore, update your connection config to the new instance endpoint; the old endpoint is untouched. Manual snapshots survive instance deletion, so delete them explicitly if they are not needed.

Steps

  1. After any RDS restore, update your connection config to the new instance endpoint; the old endpoint is untouched. Manual snapshots survive instance deletion, so delete them explicitly if they are not needed. For encrypted cross-region or cross-account snapshot copies, re-encrypt with a KMS key that exists in the target account and region.

When to use

You are seeing this: For encrypted cross-region or cross-account snapshot copies, re-encrypt with a KMS key that exists in the target account and region. Use this skill when you run into "RDS restores always create a new instance, never restore in place".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Ops skill notes: documents the gotcha that RDS point-in-time recovery and snapshot restores always create a brand-new instance with a new endpoint. RDS never restores in place, so agents that restore and then connect to the old endpoint will hit the old data or a missing instance. Manual snapshots persist until explicitly deleted and survive instance deletion.

Verified resolution: After any RDS restore, update your connection config to the new instance endpoint; the old endpoint is untouched. Manual snapshots survive instance deletion, so delete them explicitly if they are not needed. For encrypted cross-region or cross-account snapshot copies, re-encrypt with a KMS key that exists in the target account and region.

Source URL: https://github.com/itumor/opencode-skills/blob/HEAD/claude-skills/aws-rds/SKILL.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_A1C6rsG-erI3VzlA4vOx1g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">RDS restores always create a new instance, never restore in place <span>— Vectle</span></a>