Cannot create tables after dynamodb backup enabled

[nam-truong-le]

Environment information

System:
  OS: macOS 15.3.2
  CPU: (8) arm64 Apple M3
  Memory: 123.64 MB / 24.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 22.8.0 - ~/.nvm/versions/node/v22.8.0/bin/node
  Yarn: undefined - undefined
  npm: 10.8.2 - ~/.nvm/versions/node/v22.8.0/bin/npm
  pnpm: 10.6.4 - ~/.nvm/versions/node/v22.8.0/bin/pnpm
NPM Packages:
  @aws-amplify/ai-constructs: Not Found
  @aws-amplify/auth-construct: Not Found
  @aws-amplify/backend: 1.14.3
  @aws-amplify/backend-ai: Not Found
  @aws-amplify/backend-auth: Not Found
  @aws-amplify/backend-cli: 1.5.0
  @aws-amplify/backend-data: Not Found
  @aws-amplify/backend-deployer: Not Found
  @aws-amplify/backend-function: Not Found
  @aws-amplify/backend-output-schemas: Not Found
  @aws-amplify/backend-output-storage: Not Found
  @aws-amplify/backend-secret: Not Found
  @aws-amplify/backend-storage: Not Found
  @aws-amplify/cli-core: Not Found
  @aws-amplify/client-config: Not Found
  @aws-amplify/data-construct: Not Found
  @aws-amplify/data-schema: Not Found
  @aws-amplify/deployed-backend-client: Not Found
  @aws-amplify/form-generator: Not Found
  @aws-amplify/model-generator: Not Found
  @aws-amplify/platform-core: Not Found
  @aws-amplify/plugin-types: Not Found
  @aws-amplify/sandbox: Not Found
  @aws-amplify/schema-generator: Not Found
  aws-amplify: 6.13.5
  aws-cdk: 2.1005.0
  aws-cdk-lib: 2.184.1
  typescript: 5.8.2
No AWS environment variables
No CDK environment variables

Data packages

aws-amplify-gen2@0.1.1 /Users/truong/Desktop/git/al/shop-app-v2
├─┬ @aws-amplify/backend-cli@1.5.0 -> ./node_modules/.pnpm/@aws-amplify+backend-cli@1.5.0_@aws-sdk+client-sso-oidc@3.621.0_@aws-sdk+client-sts@3.6_f8736c46058690b72f4717362799780d/node_modules/@aws-amplify/backend-cli
│ └─┬ @aws-amplify/schema-generator@1.2.8 -> ./node_modules/.pnpm/@aws-amplify+schema-generator@1.2.8_@aws-sdk+types@3.734.0_aws-cdk-lib@2.184.1_constructs@10.4.2__constructs@10.4.2/node_modules/@aws-amplify/schema-generator
│   └── @aws-amplify/graphql-schema-generator@0.11.2 -> ./node_modules/.pnpm/@aws-amplify+graphql-schema-generator@0.11.2_aws-cdk-lib@2.184.1_constructs@10.4.2__constructs@10.4.2/node_modules/@aws-amplify/graphql-schema-generator
└─┬ @aws-amplify/backend@1.14.3 -> ./node_modules/.pnpm/@aws-amplify+backend@1.14.3_@aws-sdk+client-cloudformation@3.693.0_@aws-sdk+client-s3@3_d5feeb8f168a14355e95c12ca9c8fa40/node_modules/@aws-amplify/backend
  └─┬ @aws-amplify/backend-data@1.4.1 -> ./node_modules/.pnpm/@aws-amplify+backend-data@1.4.1_@aws-sdk+types@3.734.0_aws-cdk-lib@2.184.1_constructs@1_98786f2488a62ef381c51d864b5c2507/node_modules/@aws-amplify/backend-data
    └── @aws-amplify/data-construct@1.15.1 -> ./node_modules/.pnpm/@aws-amplify+data-construct@1.15.1_aws-cdk-lib@2.184.1_constructs@10.4.2__constructs@10.4.2/node_modules/@aws-amplify/data-construct

Description

Hi, after I enabled point in time backup like this:

import { MyBackend } from "./definition";

export default function initData(backend: MyBackend) {
  const { amplifyDynamoDbTables } = backend.data.resources.cfnResources;
  for (const table of Object.values(amplifyDynamoDbTables)) {
    table.deletionProtectionEnabled = false;
    table.pointInTimeRecoveryEnabled = true;
  }
}

I constantly getting this error and have to retry deployments multiple times. It happens with Previews depoyments most of the times.

Message returned: Backups are being enabled for the table: Counter-jd5cuhaqbjhtraeyv5skzzedi4-NONE. Please retry later

[AnilMaktala]

Hey @nam-truong-le, Thank you for bringing this issue to our attention. To help us investigate further, could you please provide the following details:

1. Your complete GraphQL schema or a list of your models, including:

   • The total number of models in your schema
   • The current PITR (Point-in-Time Recovery) status for your existing models

2. Regarding the Counter model mentioned in the error (Counter-jd5cuhaqbjhtraeyv5skzzedi4-NONE):

   • Is this a newly added model?
   • What does the deployment flow look like (e.g., are you enabling PITR during table creation or afterward)?

This information will help us determine whether the issue is related to DynamoDB backup timing or if there are other specific conditions causing the error.

[LukaASoban]

@nam-truong-le same thing happened to me. You have to do a 2 stage deployment. First with the tables created and then another one with PITR enabled

[fossamagna]

@nam-truong-le @LukaASoban @AnilMaktala
I think that this issue is same to aws-amplify/amplify-backend#1654.