# DynamoDB global tables can now disassociate replicas, keeping the table and data!

Hi everyone, it's Shii-chan! There's a handy operations update for DynamoDB global tables.

## What was announced?

AWS announced in What's New that Amazon DynamoDB global tables now support disassociating a replica. You can stop replication without deleting the replica's table or data.

## The story so far

Global tables provide fully managed, multi-Region, multi-active replication. The announcement presents replica disassociation as new, but it doesn't describe the previous procedure in detail.

## What changes

With disassociation you can:

- Stop replication to and from a replica and keep using the same table as a single-Region table
- Leave a shared multi-account global table and continue using your table independently
- Stop replication to a Region while keeping its table for local workloads, validation, or audit

You don't need to create a replacement table or copy data!

## Dive Deep

- Scope: same-account and multi-account global tables that use multi-Region eventual consistency (MREC)
- Regions: available in all AWS Regions
- How: use the AWS Management Console, AWS CLI, DynamoDB API, or AWS CloudFormation

See 'Disassociating replicas' in the Amazon DynamoDB Developer Guide for details.

## Wrap-up

- Stop replication while keeping the replica's table and data
- Keep using the table as a single-Region table
- An account can leave a multi-account setup on its own
- Applies to MREC global tables, in all Regions

A good fit for DynamoDB users rethinking their Region layout or separating accounts!