Zero-downtime DynamoDB construct migration: from Table to TableV2 with cdk orphan
Database Blog
This article explains how to migrate a DynamoDB table from the CDK Table construct to TableV2 with zero downtime using the new cdk orphan command.
- TableV2 maps directly to AWS::DynamoDB::GlobalTable for native CloudFormation replica management
- Table construct uses Lambda-backed custom resources; TableV2 supports per-replica configuration
- cdk orphan detaches resources from CloudFormation stacks without deletion
- Migration workflow: orphan existing table, update CDK code, import table under TableV2
- Data, streams, and application traffic remain uninterrupted throughout migration
- After import, add replicas in subsequent deployment with per-replica settings
- Requires AWS CDK v2.x with bootstrap stack version 32 or later
The cdk orphan command eliminates manual CloudFormation console operations, enabling safe DynamoDB construct migration while maintaining full application availability.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jan 31
2024
2024
A new and improved AWS CDK construct for Amazon DynamoDB tables
May 20
2026
2026
Best practices for Amazon DynamoDB Global Tables – Part 2: Failover strategies
Jul 3
2025
2025
SQL to NoSQL: Planning your application migration to Amazon DynamoDB
Dec 29
2023
2023
Migrate from SQL Server to Amazon DynamoDB with data transformation using a staging table
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.