AmberKey is in invite-only beta. Join the newsletter to request an invite and hear the moment it opens to everyone. Sign up ↓
AmberKey

Playbook

Amazon & AWS: A Library That Dies, and a Bill That Does Not

Platform claims verified July 26, 2026

What this mechanism is

Two very different accounts wear the same login, and they fail in opposite ways.

The consumer Amazon account has no transfer mechanism and no beneficiary feature. Kindle books, Prime Video purchases, Amazon Music purchases, Audible audiobooks, apps, and games are non-transferable under Amazon’s Conditions of Use. There is no process for moving them to another account, because you never owned them: you bought a licence that ends with you. A thousand-book Kindle library is not an asset your family inherits. The estate task is management and closure, not inheritance.

AWS, if the person ran anything on it, is the opposite problem. It bills until someone closes it, and only the account root user can close a standalone account (an account inside AWS Organizations can be closed by an organization admin). Amazon’s bereavement support does not close AWS accounts. Infrastructure keeps running, and keeps charging, until someone with root credentials acts.

So: for the shopping account, salvage what can be salvaged and close it. For AWS, treat root access as a Layer 2 secret, because without it the estate can watch a bill accrue with no way to stop it.

Set it up now

  1. On the account card (Layer 1), record: the Amazon account email, whether there is Prime, whether a Kindle or Audible library exists, and whether an AWS account hangs off this identity. That last flag is the one that changes what your executor must do first.
  2. Download what is downloadable while you are alive. Kindle books can be downloaded to a device and, for many titles, exported; Amazon Photos can be bulk-downloaded; order history can be exported for tax and warranty records. Whatever leaves the platform as a file survives; whatever stays is a licence.
  3. Note any gift card balance. It can be transferred before closure, and it is the one part of the consumer account that is genuinely salvageable.
  4. If Amazon Photos holds family photographs, treat it as a photo library and see that playbook. This is the highest emotional-value content in the account, and it is not covered by any legacy mechanism.
  5. For AWS: escrow the root email, the root password, and the root MFA recovery path in Layer 2. If the root MFA is a hardware key or an authenticator on a phone, record where it physically is. Consider setting up AWS Organizations, because an organization admin can close a member account without root, which gives the estate a second door.
  6. List what AWS is actually running, in plain language, on the card. “The family website and its backups” tells an executor whether closing it destroys something.

What AmberKey stores

  • Layer 1 (metadata): Amazon account email, Prime status, whether a media library exists, whether AWS exists and roughly what it runs, and where any root MFA device physically lives.
  • Layer 2 (bearer secrets): AWS root credentials and MFA recovery, plus the consumer account password if you escrow it. AWS root is the important one: without it the estate cannot stop the billing.
  • Do not store a promise that the Kindle library is inheritable. It is not, and setting that expectation is unkind. Say so on the card.

What your survivors do

  1. Deal with AWS first if it exists. It is the only part that costs money every day. Sign in as root, or have an Organizations admin close the member account. Take a backup of anything wanted before closing, because closure deletes resources after a grace period.
  2. If there is no root access, open an AWS Support case explaining the circumstances. Expect this to be slow and uncertain; it is precisely the situation the Layer 2 escrow exists to avoid.
  3. Move the gift card balance off before closing the consumer account. It is forfeited otherwise.
  4. Download Amazon Photos and any order history the estate may need. Order history matters more than people expect for warranties, insurance claims, and proving what was bought.
  5. Cancel Prime and any Subscribe & Save or channel subscriptions. These renew quietly and are a common source of small charges months after a death.
  6. Notify Amazon by emailing bereavement-support-cs@amazon.com with the death certificate, your photo ID, and an account identifier (the email address, mobile number, or an order number).
  7. Accept that the media library ends. Do not spend estate money on lawyers trying to transfer Kindle titles; the terms are unambiguous.

Required documents

Consumer account: death certificate, requestor photo ID, and an account identifier, sent to bereavement support. Amazon reviews these manually with no published checklist beyond that.

AWS: no documents if you hold root credentials, because you simply close the account. Without them, an AWS Support case and whatever proof of authority they ask for, at their discretion.

Expected timeline

AWS closure with root access: minutes, then a grace period before resources are deleted. Amazon bereavement support: weeks, manual review. AWS without root: open-ended, and billing continues meanwhile.

Gotchas

  • The library is the shock. Families reliably assume a large Kindle or Audible collection passes to someone. It does not, under any circumstance, and it is better for them to learn that from your notes than from a support agent.
  • AWS bills while probate runs. This is the only account in this packet that actively drains the estate while everyone waits for paperwork. Root access in Layer 2 is the fix.
  • Root MFA is a hard stop. An AWS root account protected by an authenticator app on a locked, wiped phone is effectively closed to the estate. Record where the device is and escrow the recovery path; see the authenticator playbook.
  • Household sharing is not inheritance. Amazon Household lets others use some content while you are alive; it confers nothing after death.
  • Closing the consumer account can affect AWS if they share an identity. Close AWS deliberately and first, rather than discovering the coupling.
  • Alexa devices keep working against a closed or orphaned account in confusing ways. Factory reset them before rehoming or selling.
  • A bulk Amazon Photos download is easily large enough to outgrow the browser. Locking it works; reopening it in the recovery tool may not, past roughly a gigabyte. It is ordinary age, so `age -d -i key.txt photos.zip.age

    photos.zip` handles any size. Consider splitting the download by year.